Re: [reSIProcate-users] problem of p2p call with TCP transport

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Title: Mail

I am not aware of any TCP bugs in resip. 

 

One thing to be aware of though, when using TCP some UA’s expect all SIP traffic down the same TCP connection that they used for the registration ? this behavior is not specified in the base SIP spec.  A standard for doing this is being spec’d out by in draft-ietf-sip-outbound.

 

Resiprocate may try to form a TCP connection back to the client, so clients that don’t listen for incoming TCP traffic will have trouble receiving certain requests and responses.

 

Scott

 

From: 秦杨 [mailto:qinyang_1980@xxxxxxx]
Sent: May 21, 2008 4:40 AM
To: resiprocate-users
Cc: Scott Godin
Subject: problem of p2p call with TCP transport

 

Hi Scott:

 

I prepared 3 computers to test my demo p2p sip call.
PC_A is registered as user1.
PC_B is registered as user2.
PC_C is sip proxy server.

My expectation testing flow:
-----------------------------
1.I registered the user1 and user2 on the PC_C.
2.PC_A calls PC_B.
3.PC_A will send a sip invite msg to PC_C.
4.PC_C will send back the 100 to PC_A.
5.PC_C will transfer the sip invite msg to PC_B.
6.PC_B received the sip invite msg and send back the 180 and 200 msg.
7.PC_A received the 180 and 200 msg and then created the connection with PC_B.

 

Now, I tried the testing flow use the UDP protocol. It's OK.

But when I tried with TCP protocol, the flow is failed.

The PC_C can not transfer the sip invite message sent from PC_A to PC_B.
I don't know what the problem is ?? Is any bugs with TCP ??

 

 

Ryan Qin