On Wed, Feb 18, 2009 at 12:31 PM, Gabor Paller <[email protected]> wrote: > Hi, > > I have the following interesting situation with SipX 3.10.2. There is a > JAIN-SIP application subscribed to MWI notifications. Before the > scenario presented below, there was a successful subscription and it is > expiring, therefore the application sends a new subscribe. The > subscription progresses nicely, the first SUBSCRIBE is challenged and > now the application sends the SUBSCRIBE with the credentials. > > 17:55:29,661: > SUBSCRIBE sip:[email protected] SIP/2.0 > Call-ID: [email protected] > CSeq: 2 SUBSCRIBE > From: <sip:[email protected]>;tag=tag3218735 > To: <sip:[email protected]> > Max-Forwards: 70 > Contact: <sip:[email protected]:5560> > Expires: 1800 > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, > SUBSCRIBE, INFO, UPDATE > Event: message-summary > Authorization: Digest > username="8186",realm="onrelay.local",nonce="b77e1431144dee71a8a0bc87bf4 > 97da94999a891",uri="sip:[email protected]",algorithm=MD5,respon > se="0d188e8e591cfd58a36e71196a3210d3" > Via: SIP/2.0/UDP > 10.1.3.11:5560;branch=z9hG4bKd8de6d7cf6cb5e86dcb366a003d69f38 > Content-Length: 0 > > After this message, however, 202 Accepted does not arrive but SipX > immediately returns a NOTIFY. > > 17:55:29,694: > NOTIFY sip:[email protected]:5560 SIP/2.0 > Content-Type: application/simple-message-summary > Event: message-summary > Subscription-State: active;expires=867 > From: <sip:[email protected]>;tag=b447fa6a > To: <sip:[email protected]>;tag=tag3218735 > Call-ID: [email protected] > CSeq: 2 NOTIFY > Contact: <sip:[email protected]> > User-Agent: sipXecs/3.10.2 sipXecs/publisher (Linux) > Date: Mon, 16 Feb 2009 17:55:29 GMT > Max-Forwards: 19 > Accept-Language: en > Supported: sip-cc-01,timer > Via: SIP/2.0/UDP > 10.1.3.11:5060;branch=z9hG4bK-sipXecs-00f6464514d97a97596ee08359c3a2a423 > 02,SIP/2.0/UDP > 10.1.3.11:5110;branch=z9hG4bK-sipXecs-b31f347bf4a3f0867d610a0925cb3884fc > 75 > Content-Length: 51 > > This confuses the JAIN-SIP stack, as there is no SUBSCRIBE dialog > established, the NOTIFY goes into the void and cannot be responded to. > > Eventually the 202 arrives. > > 17:55:29,701: > SIP/2.0 202 Accepted > From: <sip:[email protected]>;tag=tag3218735 > To: <sip:[email protected]>;tag=b447fa6a > Call-ID: [email protected] > CSeq: 2 SUBSCRIBE > Via: SIP/2.0/UDP > 10.1.3.11:5560;branch=z9hG4bKd8de6d7cf6cb5e86dcb366a003d69f38 > Expires: 867 > Contact: <sip:[email protected]> > User-Agent: sipXecs/3.10.2 sipXecs/publisher (Linux) > Date: Mon, 16 Feb 2009 17:55:29 GMT > Allow: INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE > Accept-Language: en > Supported: sip-cc-01,timer > Content-Length: 0 > > Shouldn't 202 Accepted arrive first? The application and the server are > located on the same machine, I can't imagine that this is caused by > network delay.
Gabor, There is a NIST specific property to allow you to process unsolicited NOTIFY. Please see the javadoc for the package gov.nist.javax.sip The property name is gov.nist.javax.sip.DELIVER_UNSOLICITED_NOTIFY. You must specify this to "true" if you want the behavior you seek. Regards Ranga > > Regards, > Gabor > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > -- M. Ranganathan _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
