<br>
Hi Jon,<br>
<br>
Which Cisco gw are you using? We have a Cisco AS5350 running
12.3(8)T3. I attempted to reproduce what you saw but did not see
the same symptom. Which softphone?<br>
<br>
Dan<br>
<br><br><div><span class="gmail_quote">On 7/20/05, <b class="gmail_sendername">Jon Mansey</b> <<a href="mailto:jon@tigrisnet.net">jon@tigrisnet.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In the following scenario, it seems that ser may not be sending the BYE to<br>the right port on the cisco, is that possible? The cisco is not registered<br>with ser, it is a trusted IP. The DID is an alias for my softphone UID. This
<br>only happens for pstn-voip calls, when calling voip-pstn, ser always talks<br>to the cisco on port 5060 and the BYE is obeyed, whichever end sends 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 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 different<br>ports for each message, but how is ser supposed to communicate back to it if
<br>not on the port used by the original INVITE? Perhaps it should only 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 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><a href="mailto:serusers@lists.iptel.org">Serusers@iptel.org
</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://mail.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>