<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>My experience is that you can answer to both 5060 and the source port with
the same result as long as the message is part of a previous dialog. Cisco
normally announces 5060 in Contact. I have never seen the refused BYE
either. BYE is the start of a new dialog and I'm not sure how you make ser
send to the high source port in your ser.cfg. I would try using
rewritehostport("cisco_ip:5060") for all messages to the gw.</DIV>
<DIV>g-)</DIV>
<DIV> </DIV>
<DIV>---- Original Message ----<BR>From: Jon Mansey<BR>To: 'Daniel
Poulsen'<BR>Cc: serusers@lists.iptel.org<BR>Sent: Thursday, July 21, 2005 12:58
AM<BR>Subject: RE: [Serusers] Cisco pstn gw ignoring BYE from ser<BR><BR>>
Gateway is a 3600 running 12.something, softphone is X-ten, but the<BR>>
softphone is irrelevant, it happens on all UAs. <BR>> <BR>> User-Agent:
Cisco-SIPGateway/IOS-12.x<BR>> <BR>> what port do the original invite and
subsequent messages come from if<BR>> you originate a pstn call to ser from
your cisco, if you dont me me<BR>> asking? <BR>> <BR>> <BR>>
<BR>> <BR>> -----Original Message-----<BR>> From: Daniel Poulsen
[mailto:dpoulsen@gmail.com]<BR>> Sent: Wednesday, July 20, 2005 3:01
PM<BR>> To: Jon Mansey<BR>> Cc: serusers@lists.iptel.org<BR>> Subject: Re:
[Serusers] Cisco pstn gw ignoring BYE from ser<BR>> <BR>> <BR>>
<BR>> Hi Jon,<BR>> <BR>> Which Cisco gw are you using? We have a
Cisco AS5350 running<BR>> 12.3(8)T3. I attempted to reproduce what you
saw but did not see the<BR>> same symptom. Which softphone?
<BR>> <BR>> Dan<BR>> <BR>> <BR>> <BR>> On 7/20/05, Jon Mansey
<jon@tigrisnet.net> wrote:<BR>> In the following scenario, it seems
that ser may not be sending the<BR>> BYE to <BR>> the right port on the
cisco, is that possible? The cisco is not<BR>> registered <BR>> with ser,
it is a trusted IP. The DID is an alias for my softphone<BR>> UID. This
<BR>> only happens for pstn-voip calls, when calling voip-pstn, ser
always<BR>> talks <BR>> to the cisco on port 5060 and the BYE is obeyed,
whichever end sends<BR>> it <BR>> first.<BR>> <BR>> <BR>> call
scenario<BR>> <BR>> dial DID from pstn phone<BR>> <BR>> cisco:51339
-> ser:5060 INVITE<BR>>
ser:5060 -> cisco:51339 100
trying<BR>> ser:5060 ->
cisco:51339 180 ringing softphone ringing<BR>>
ser:5060 -> cisco:51339 200
OK softphone answered<BR>> cisco:53924 ->
ser:5060 ACK<BR>> <BR>> call in progress, 2 way
audio<BR>> <BR>> I hang up the softphone<BR>> <BR>>
ser:5060 -> cisco:51339
BYE softphone says "hanging up"<BR>>
ser:5060 -> cisco:51339
BYE<BR>> ser:5060 ->
cisco:51339 BYE<BR>> ser:5060
-> cisco:51339 BYE<BR>>
ser:5060 -> cisco:51339
BYE<BR>> ser:5060 ->
cisco:51339 BYE<BR>> ser:5060
-> cisco:51339 BYE<BR>> <BR>> <BR>>
ser:5060 -> softphone:5060
TIMEOUT softphone says "hung up"<BR>> <BR>> pstn phone still off
hook, call up still<BR>> <BR>> i hang up the pstn phone<BR>> <BR>>
cisco:50580 -> ser:5060
BYE<BR>> ser:5060 ->
cisco:5060 OK<BR>>
ser:5060 -> cisco:51339
BYE<BR>> <BR>> So the cisco has used 3 different ports during this call,
one for the<BR>> INVITE, which ser then uses to send replies back to, but the
ACK<BR>> comes from <BR>> a new port, and then the eventual BYE comes from
a 3rd port.<BR>> <BR>> I can understand how the cisco tries not to be
stateful and uses<BR>> different <BR>> ports for each message, but how is
ser supposed to communicate back<BR>> to it if <BR>> not on the port used
by the original INVITE? Perhaps it should only<BR>> talk to <BR>> the
cisco on port 5060? If so how do I make it do that? Is the cisco<BR>>
misbehaving by using many different ports when it originates the sip<BR>>
call? <BR>> Is that a known IOS bug perhaps?<BR>> <BR>> Help and wisdom
appreciated,<BR>> <BR>> Jon<BR>> <BR>> <BR>>
_______________________________________________<BR>> Serusers mailing
list<BR>> serusers@lists.iptel.org<BR>>
http://lists.iptel.org/mailman/listinfo/serusers<BR>> <BR>> <BR>>
<BR>> <BR>> <BR>> <BR>>
_______________________________________________<BR>> Serusers mailing
list<BR>> serusers@lists.iptel.org<BR>>
http://lists.iptel.org/mailman/listinfo/serusers</DIV></BODY></HTML>