Is the Construction of BYE request is correct in behind NAT?..


#1

Hi All,

    We have tested sip communicator behaind the NAT (in between Proxy). SIP Communicator constructs the BYE request with the incorrect Route Header.

here, BYE message.

BYE sip:200.201.202.158:5070 SIP/2.0
CSeq: 1 BYE
Call-ID: fe12113298f191159657bd3d07fef6b2@0:0:0:0:0:0:0:0

From: <sip:siva@200.201.202.158>;tag=841ef73b

User-Agent: SIP Communicator1.0-alpha3-nightly.build.1844Linux
Max-Forwards: 70
Route: <sip:ram@200.201.202.158:40834;transport=udp;registering_acc=200_201_202_158>
Via: SIP/2.0/UDP 200.201.202.157:5060;branch=z9hG4bKdf7782f798572385d1b290acf8e718ff
Content-Length: 0

Please help me.. Is the construction of BYE request is correct?

···

To: <sip:ram@200.201.202.158>;tag=3774d860

--
Regards,
Keerthi.


#2

Hi,

to see if it is a problem of SC or a proxy problem it would
be helpful to see all messages (INVITE, OK, ACK, BYE ...)
that SC receives. The contents of the Route header are constructed
from the Record-route header that a proxy inserts into a
SIP packet.

Regards,
Werner

Keerthi schrieb:

···

Hi All,

   We have tested sip communicator behaind the NAT (in between Proxy).
SIP Communicator constructs the BYE request with the incorrect Route
Header.

here, BYE message.

BYE sip:200.201.202.158:5070 SIP/2.0
CSeq: 1 BYE
Call-ID: fe12113298f191159657bd3d07fef6b2@0:0:0:0:0:0:0:0
From: <sip:siva@200.201.202.158>;tag=841ef73b
To: <sip:ram@200.201.202.158>;tag=3774d860
User-Agent: SIP Communicator1.0-alpha3-nightly.build.1844Linux
Max-Forwards: 70
Route:
<sip:ram@200.201.202.158:40834;transport=udp;registering_acc=200_201_202_158>

Via: SIP/2.0/UDP
200.201.202.157:5060;branch=z9hG4bKdf7782f798572385d1b290acf8e718ff
Content-Length: 0

Please help me.. Is the construction of BYE request is correct?


#3

HI ..
Here i have attached the logs.

Werner Dittmann wrote:

Hi,

to see if it is a problem of SC or a proxy problem it would
be helpful to see all messages (INVITE, OK, ACK, BYE ...)
that SC receives.

From the log you can see all the sip messages (INVITE,OK,ACK and BYE)
in the log, ram is the caller and user is callee.
caller call the callee and callee accepts and caller terminated the call.

sip:ram@200.201.202.158.log.zip (16.7 KB)

sip:user@200.201.202.158.log.zip (48.7 KB)

···

The contents of the Route header are constructed
from the Record-route header that a proxy inserts into a
SIP packet.

Regards,
Werner

Keerthi schrieb:
  

Hi All,

   We have tested sip communicator behaind the NAT (in between Proxy).
SIP Communicator constructs the BYE request with the incorrect Route
Header.

here, BYE message.

BYE sip:200.201.202.158:5070 SIP/2.0
CSeq: 1 BYE
Call-ID: fe12113298f191159657bd3d07fef6b2@0:0:0:0:0:0:0:0
From: <sip:siva@200.201.202.158>;tag=841ef73b
To: <sip:ram@200.201.202.158>;tag=3774d860
User-Agent: SIP Communicator1.0-alpha3-nightly.build.1844Linux
Max-Forwards: 70
Route:
<sip:ram@200.201.202.158:40834;transport=udp;registering_acc=200_201_202_158>

Via: SIP/2.0/UDP
200.201.202.157:5060;branch=z9hG4bKdf7782f798572385d1b290acf8e718ff
Content-Length: 0

Please help me.. Is the construction of BYE request is correct?

Hi,
  
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Regards,
Keerthi.