thanks a lot sir !!!

hello,
finally !!!
thanks a lot for your help.
but I'm wondering why the stack is blocked in this case.
thanks a lot !!!

best regards,
Salim.


>From: "Jeroen van Bemmel" <[email protected]>
>To: "slim bens" <[email protected]>,<[email protected]>
>CC: <[email protected]>
>Subject: Re: [nist-sip] here is the link to the example illustrating my 
>problem!!!
>Date: Wed, 8 Nov 2006 23:14:10 +0100
>
>Slim,
>
>It is caused by your threading structure. In NodeB processRequest you block 
>the thread receiving the requestEvent, that is a thread owned by the stack. 
>Blocking that prevents your application from receiving other events
>
>Replace "sendRequestToNodeC();"
>
>with
>
>new Thread() {@Override
>public void run() {
>
>try {
>    sendRequestToNodeC();
>} catch (Exception e) {
>e.printStackTrace();
>}}}.start();
>
>and it works
>
>Regards,
>Jeroen
>
>
>
>
>
>
>slim bens wrote:
>>http://www.iro.umontreal.ca/~sidhomiy/Test.zip
>>
>>
>>
>>
>>hello to everyone,
>>here is my problem.
>>there are 3 classes : NodeC,NodeA,NodeB.
>>and the jar files are libraries.
>>launch the example following this order :NodeC,NodeB,NodeA.
>>
>>I said previously that NodeB doesn't receive the response from NodeC,
>>actually the stack Sip of NodeB receives the response, but the
>>response doesn't reach the upper layer (application layer) which is
>>the processResponse(..) of the SipListener interface.
>>Some way the response is discarded, I don't why yet !!!
>>it's been a week that I'm stuck with this bug.
>>
>>thank you for giving me a hand in debuging this problem.
>>
>>
>>
>>
>>>From: "M. Rangnathan" <[email protected]>
>>>To: slim bens <[email protected]>
>>>CC: [email protected]
>>>Subject: Re: [nist-sip] did anyone face this problem !!!
>>>Date: Mon, 06 Nov 2006 14:42:38 -0500
>>>
>>>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
>>>>
>>>
>>>
>>>--
>>>M. Ranganathan
>>>
>>>Advanced Networking Technologies Division,
>>>National Institute of Standards and Technology (NIST),
>>>100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899. tel:301 975
>>>3664 , fax:301 590 0932 http://w3.antd.nist.gov/
>>>Advanced Networking Technologies For the People!
>>>
>>>
>>
>>_________________________________________________________________
>>Ne perdez pas de temps dans les files d'attente. magasinez en ligne.
>>http://magasiner.sympatico.msn.ca
>>
>>_______________________________________________
>>nist-sip mailing list
>>[email protected]
>>http://www-x.antd.nist.gov/mailman/listinfo/nist-sip
>

_________________________________________________________________
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