Rohit Aggarwal wrote: > Hello Monika > > >From the call flow that you have shared, it is observed that Express Talk > >SIP Phone has received BYE from port 45313 and is sending the response back > >to port 45313 which is different from the port number 5060 in Via header of > >BYE - something that may happen in NAT scenario (although should have seen > >rport here) but here both the UAs are on same machine and assume that > >request is sent directly. > > 10:28:50 UDP Packet Received from > 148.147.206.192:45313<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > 10:28:50 UDP Packet Sent to > 148.147.206.192:45313>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > > >From RFC 3261 Sec 18.1.1 Sending Requests: > For unreliable unicast transports, the client transport MUST be > prepared to receive responses on the source IP address from which the > request is sent (as responses are sent back to the source address) > and the port number in the "sent-by" field. Furthermore, as with > reliable transports, in certain cases the response will be sent > elsewhere. The client MUST be prepared to receive responses on any > address and port that would be selected by a server based on the > procedures described in Section 5 of [4]. > > >From RFC 3263 Sec 5 Server Usage > RFC 3261 [1] defines procedures for sending responses from a server > back to the client. Typically, for unicast UDP requests, the > response is sent back to the source IP address where the request came > from, using the port contained in the Via header. For reliable > transport protocols, the response is sent over the connection the > request arrived on. > A server, according to RFC 3261 [1], will send a response on the > connection it arrived on (in the case of reliable transport > protocols), and for unreliable transport protocols, to the source > address of the request, and the port in the Via header field. > > I feel Express Talk should send the 200 OK for BYE on 5060 i.e. the port in > Via header for UDP. You can check if there is any option/configuration in > Express Talk that may impact this behavior (e.g. any STUN related config). > Even the 200 OK seems to have come from a different port (45312). > > Regards > Rohit Aggarwal > Aricent > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Monika > Soni > Sent: Wednesday, December 23, 2009 11:38 AM > To: [email protected] > Subject: [Sip-implementors] Query : 200 OK for BYE > > I have implemented a SIP User agent listening on 148.147.206.192:5060. And > used express talk SipPhone ( listening on 148.147.206.192:5070 ) to > initiate SIP session. The issue I am facing here is My SIP UA sends BYE > message and waits for 200 OK. But 200 OK is coming on port other than 5060. > Please refer to call flow below. > > Is it expected behaviour ? > > Is there a way to force SIP client to send 200 OK for BYE on desired port > number ? > > > > > > > UDP Packet Sent to 148.147.206.192:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > INVITE sip:[email protected] <sip%[email protected]> SIP/2.0 > > Via: SIP/2.0/UDP 148.147.206.192:5070;rport;branch=z9hG4bK151952 > > To: <sip:[email protected] <sip%[email protected]>> > > From: "Alice" <sip:[email protected] <sip%[email protected]> > >> ;tag=600 >> > > Call-ID: [email protected] > > CSeq: 891 INVITE > > Max-Forwards: 20 > > User-Agent: NCH Software Express Talk 4.02 > > Contact: <sip:[email protected]:5070> > > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, REFER, NOTIFY > > Supported: replaces > > Content-Type: application/sdp > > Content-Length: 338 > > v=0 > > o=NCHSoftware-Talk 1261542553 1261542560 IN IP4 148.147.206.192 > > s=Express Talk Call > > c=IN IP4 148.147.206.192 > > t=0 0 > > m=audio 8000 RTP/AVP 0 8 96 3 13 101 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:8 PCMA/8000 > > a=rtpmap:96 G726-32/8000 > > a=rtpmap:3 GSM/8000 > > a=rtpmap:13 CN/8000 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-16 > > a=sendrecv > > ---------------------------------------------------------------- > > 10:27:27 UDP Packet Received from > 148.147.206.192:45312<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > SIP/2.0 200 OK > > From: "Alice" <sip:[email protected] <sip%[email protected]> > >> ;tag=600 >> > > To: "VMPro" <sip:[email protected] <sip%[email protected]> > >> ;tag=-4202e26d4b31a337-6c9e8040_T148.147.206.192 >> > > Call-ID: [email protected] > > CSeq: 891 INVITE > > Via: SIP/2.0/UDP 148.147.206.192:5070 > ;branch=z9hG4bK151952;rport=148.147.206.192 > > Allow: INVITE,ACK,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,UPDATE > > User-Agent: VMPro > > Contact: <sip:[email protected] <sip%[email protected]>;transport=udp> > > Content-Type: application/sdp > > Content-Length: 204 > > v=0 > > o=sip:[email protected] <sip%[email protected]> 1 2 IN IP4 > 148.147.206.192 > > s=sip:[email protected] <sip%[email protected]> > > c=IN IP4 148.147.206.192 > > t=0 0 > > m=audio 3374 RTP/AVP 0 101 > > a=rtpmap:101 telephone-event/8000 > > a=rtpmap:0 PCMU/8000 > > ---------------------------------------------------------------- > > 10:27:27 UDP Packet Sent to > 148.147.206.192:5060>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > ACK sip:[email protected] <sip%[email protected]>;transport=udp > SIP/2.0 > > Via: SIP/2.0/UDP 148.147.206.192:5070;rport;branch=z9hG4bK161952 > > To: "VMPro" <sip:[email protected] <sip%[email protected]> > >> ;tag=-4202e26d4b31a337-6c9e8040_T148.147.206.192 >> > > From: "Alice" <sip:[email protected] <sip%[email protected]> > >> ;tag=600 >> > > Call-ID: [email protected] > > CSeq: 891 ACK > > Max-Forwards: 20 > > User-Agent: NCH Software Express Talk 4.02 > > Content-Length: 0 > > > > ---------------------------------------------------------------- > > 10:28:50 4877ms Rtp >>> 148.147.206.192:3374 0 seq=40725 ts=1211576542 ssrc= > 778769992 160 bytes > > 10:28:50 4898ms Rtp >>> 148.147.206.192:3374 0 seq=40726 ts=1211576702 ssrc= > 778769992 160 bytes > > 10:28:50 4920ms Rtp >>> 148.147.206.192:3374 0 seq=40727 ts=1211576862 ssrc= > 778769992 160 bytes > > 10:28:50 4930ms Rtp >>> 148.147.206.192:3374 0 seq=40728 ts=1211577022 ssrc= > 778769992 160 bytes > > 10:28:50 4952ms Rtp >>> 148.147.206.192:3374 0 seq=40729 ts=1211577182 ssrc= > 778769992 160 bytes > > 10:28:50 4974ms Rtp >>> 148.147.206.192:3374 0 seq=40730 ts=1211577342 ssrc= > 778769992 160 bytes > > 10:28:50 4995ms Rtp >>> 148.147.206.192:3374 0 seq=40731 ts=1211577502 ssrc= > 778769992 160 bytes > > 10:28:50 5016ms Rtp >>> 148.147.206.192:3374 0 seq=40732 ts=1211577662 ssrc= > 778769992 160 bytes > > 10:28:50 5038ms Rtp >>> 148.147.206.192:3374 0 seq=40733 ts=1211577822 ssrc= > 778769992 160 bytes > > 10:28:50 5059ms Rtp >>> 148.147.206.192:3374 0 seq=40734 ts=1211577982 ssrc= > 778769992 160 bytes > > 10:28:50 5070ms Rtp >>> 148.147.206.192:3374 0 seq=40735 ts=1211578142 ssrc= > 778769992 160 bytes > > 10:28:50 5092ms Rtp >>> 148.147.206.192:3374 0 seq=40736 ts=1211578302 ssrc= > 778769992 160 bytes > > 10:28:50 5113ms Rtp >>> 148.147.206.192:3374 0 seq=40737 ts=1211578462 ssrc= > 778769992 160 bytes > > 10:28:50 5135ms Rtp >>> 148.147.206.192:3374 0 seq=40738 ts=1211578622 ssrc= > 778769992 160 bytes > > 10:28:50 5136ms Rtp <<< 148.147.206.192:3374 0 seq=57063 ts=1211285225 > ssrc=1211095625 160 bytes > > 10:28:50 UDP Packet Received from > 148.147.206.192:45313<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > > BYE sip:[email protected]:5070 SIP/2.0 > > From: "Alice" <sip:[email protected] <sip%[email protected]> > >> ;tag=-4202e26d4b31a337-6c9e8040_T148.147.206.192 >> > > To: <sip:[email protected] <sip%[email protected]>>;tag=600 > > Call-ID: [email protected] > > CSeq: 2 BYE > > Max-Forwards: 70 > > Via: SIP/2.0/UDP 148.147.206.192:5060 > ;branch=z9hG4bK434e828_483118284d904dd7-6c9d43fa_B > > Supported: replaces > > User-Agent: VMPro > > Content-Length: 0 > > > > ---------------------------------------------------------------- > > 10:28:50 UDP Packet Sent to > 148.147.206.192:45313>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > > SIP/2.0 200 OK > > Via: SIP/2.0/UDP 148.147.206.192:5060 > ;branch=z9hG4bK434e828_483118284d904dd7-6c9d43fa_B > > To: <sip:[email protected] <sip%[email protected]>>;tag=600 > > From: "Alice" <sip:[email protected] <sip%[email protected]> > >> ;tag=-4202e26d4b31a337-6c9e8040_T148.147.206.192 >> > > Call-ID: [email protected] > > CSeq: 2 BYE > > User-Agent: NCH Software Express Talk 4.02 > > Content-Length: 0 > > > > > Thanks in advance > Monika > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > > > > ________________________________ > "DISCLAIMER: This message is proprietary to Aricent and is intended solely > for the use of the individual to whom it is addressed. It may contain > privileged or confidential information and should not be circulated or used > for any purpose other than for what it is intended. If you have received this > message in error, please notify the originator immediately. If you are not > the intended recipient, you are notified that you are strictly prohibited > from using, copying, altering, or disclosing the contents of this message. > Aricent accepts no responsibility for loss or damage arising from the use of > the information transmitted by this email including damage from virus." > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > Hi
I hope it was not related to port number. Its due to the CSeq number in BYE request. -- Regards, Keerthi. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
