Re: did anyone face this problem !!!

The rport values in this trace look suspicious to me.

Normally when A would send to B, it would connect to B first (on port 7001 
in this case). A's port would then be an ephemeral port, not equal to the 
TCP port where A is listening (7008). In the Via, the port that should be 
used is the port on which A is listening, not the port on which it is 
sending. So rport==via port is likely an error

Perhaps the stack is doing this internally, haven't played with TCP myself 
yet.

Do you have a debug trace?

Regards,
Jeroen

M. Rangnathan wrote:
> slim bens wrote:
>
>> ello everyone,
>> I am developping a P2P application using Jain-Sip for communication.
>> I'm pretty sutck with a problem , here it is :
>>
>> we have 3 nodes : A.B,C
>>
>> B has information (URL of C) to ping  the node C,
>> and node C receive the request and sends a response to B. ('til now
>> it's ok).
>>
>> But now, the node A sends a request to B ,
>> B receives the request, and before sending a response to A,
>> B needs to ping C ,
>> then C receives the request and sends a response to B,
>> but the PROBLEM !!! is that B doesn't  receive the response from C.
>>
>> notice : the thread triggered in B by receiving the reuqest from A,
>> is blocked,
>>            waiting for the response from C.
>
>
> To abstract the problem better, please post a small code snippet to
> reproduce the problem in small example that looks like
> examples/simplecallsetup.The Requests and Responses look OKto me but
> the Tag in the 200 OK is suspect because MESSAGE does not create a
> Dialog . Thats the only thing I can think of  at the moment. Have you
> created a dialog and are you sending the MESSAGE within that Dialog?
>
>>
>> if any one has face the same, I would be very thankful if he could
>> send me the solution.
>>
>> -----------------------------------here are the request
>> ----------------------------------------------------
>>
>> A sends to B :
>>
>> REGISTER sip:[email protected]:7001;transport=tcp SIP/2.0
>> Call-ID: [email protected]
>> CSeq: 1 REGISTER
>> From: <sip:[email protected]:7008;transport=tcp>;tag=6479
>> To: <sip:[email protected]:7008;transport=tcp>
>> Via: SIP/2.0/TCP
>> 127.0.0.1:7008;branch=z9hG4bK4f67136d36f023c9d805912383903d60
>> Max-Forwards: 6
>> Contact: <sip:[email protected]:7008;transport=tcp>
>> Expires: 800
>> Require: DHT
>> Supported: DHT
>> Content-Type: application/DHT+XML
>> Content-Length: 254
>>
>> <?xml version="1.0"
>> encoding="UTF-8"?><DHTInfo><DHTDescription><DHTOverlayName>Concordia
>> DHT</DHTOverlayName><DHTHashAlg>SHA-1</DHTHashAlg></DHTDescription><DHTOperation>nodeRegistration</DHTOperation><DHTNode>sip:[email protected]:7008</DHTNode></DHTInfo>
>>
>>
>>
>>
>> ******************************************************************
>>
>> B receives from A :
>>
>> REGISTER sip:[email protected]:7001;transport=tcp SIP/2.0
>> Call-ID: [email protected]
>> CSeq: 1 REGISTER
>> From: <sip:[email protected]:7008;transport=tcp>;tag=6479
>> To: <sip:[email protected]:7008;transport=tcp>
>> Via: SIP/2.0/TCP
>> 127.0.0.1:7008;branch=z9hG4bK4f67136d36f023c9d805912383903d60;rport=7008
>> Max-Forwards: 6
>> Contact: <sip:[email protected]:7008;transport=tcp>
>> Expires: 800
>> Require: DHT
>> Supported: DHT
>> Content-Type: application/DHT+XML
>> Content-Length: 254
>>
>> <?xml version="1.0"
>> encoding="UTF-8"?><DHTInfo><DHTDescription><DHTOverlayName>Concordia
>> DHT</DHTOverlayName><DHTHashAlg>SHA-1</DHTHashAlg></DHTDescription><DHTOperation>nodeRegistration</DHTOperation><DHTNode>sip:[email protected]:7008</DHTNode></DHTInfo>
>>
>>
>>
>>
>>
>> **********************************************************
>>
>> ......... then during the process of the response to A ........
>>
>> B sends to C :
>>
>> MESSAGE sip:[email protected]:7014;transport=tcp SIP/2.0
>> Call-ID: [email protected]
>> CSeq: 1 MESSAGE
>> From: <sip:[email protected]:7001;transport=tcp>;tag=8073
>> To: <sip:[email protected]:7014;transport=tcp>
>> Via: SIP/2.0/TCP
>> 127.0.0.1:7001;branch=z9hG4bKb8d8a56120b598e6f33550fdf21f3b07
>> Max-Forwards: 6
>> Contact: <sip:[email protected]:7001;transport=tcp>
>> Expires: 800
>> Content-Type: text/plain;charset=UTF-8
>> Content-Length: 4
>>
>> PING
>>
>>
>>
>> ************************************************************
>>
>> C receives from B :
>>
>> MESSAGE sip:[email protected]:7014;transport=tcp SIP/2.0
>> Call-ID: [email protected]
>> CSeq: 1 MESSAGE
>> From: <sip:[email protected]:7001;transport=tcp>;tag=8073
>> To: <sip:[email protected]:7014;transport=tcp>
>> Via: SIP/2.0/TCP
>> 127.0.0.1:7001;branch=z9hG4bKb8d8a56120b598e6f33550fdf21f3b07;rport=7001
>> Max-Forwards: 6
>> Contact: <sip:[email protected]:7001;transport=tcp>
>> Expires: 800
>> Content-Type: text/plain;charset=UTF-8
>> Content-Length: 4
>>
>> PING
>>
>> ******************************************************************
>>
>> C reply to B :
>>
>> SIP/2.0 200 OK
>> Call-ID: [email protected]
>> CSeq: 1 MESSAGE
>> From: <sip:[email protected]:7001;transport=tcp>;tag=8073
>> To: <sip:[email protected]:7014;transport=tcp>;tag=6300
>> Via: SIP/2.0/TCP
>> 127.0.0.1:7001;branch=z9hG4bKb8d8a56120b598e6f33550fdf21f3b07;rport=7001
>> Content-Type: text/plain;charset=UTF-8
>> Content-Length: 4
>>
>> PING
>>
>> ----------------------------------------------------------------------
>>
>> B doesn't receive the response from C :  <------------------- PROBLEM
>> !!!!
>>
>> _________________________________________________________________
>> Achetez ce que vous voulez, quand vous voulez sur Sympatico / MSN
>> Magasiner
>> http://magasiner.sympatico.msn.ca/content/shp/?ctId=101,ptnrid=176,ptnrdata=081805
>>
>>
>> _______________________________________________
>> nist-sip mailing list
>> [email protected]
>> http://www-x.antd.nist.gov/mailman/listinfo/nist-sip