Hi members, hope someone can help me. My setup: SipX 4.0.1 sipXtapi 3.3 (SVN Rev 11467) compiled with Visual Studio
I try to subscribe presence states of some phones by subscribing the resourcelist at our sipx. The subscription is answered with an 202 followed by a Notify message. The second Notify message from the presence server is answered by sipxtapi with 481 Transaction does not exist. Below you find the subscribe and notify messages. What does transaction does not exist mean? The second notify belongs to the dialog initiated by the subscribe message (same call-id same from and to header tags). The CSeq is increased by one and a new via branch was created. So I see no problem. Same dialog, new transaction. Thanks in advance Jan SUBSCRIBE sip:[email protected] SIP/2.0 From: <sip:[email protected]>;tag=35a7b2be8686cf178af07ddbcd51b507 To: <sip:[email protected]> Call-Id: ssc-7ab8c84ac338b5ab85e57d5678397...@28b70d10c2d661262affe918ab9e2955 Cseq: 2 SUBSCRIBE Contact: sip:[email protected]:62621 Event: dialog Accept: application/dialog-info+xml,multipart/related Expires: 3600 Date: Tue, 22 Dec 2009 09:23:09 GMT Max-Forwards: 70 User-Agent: sipX/1.3.0 (WinNT) Supported: replaces, eventlist Authorization: Digest username="7800", realm="voip.mydomain.de", nonce="a69e3ede32ff3025ce482637b2f173ed4b308fb3", uri="sip:[email protected]", response="895069c140cb7986169f703e06d72faa" Via: SIP/2.0/UDP 192.168.1.99:62621;branch=z9hG4bK-771e24c176d6 Content-Length: 0 ==================================================================================================================== NOTIFY sip:[email protected]:62621;x-sipX-nonat SIP/2.0 From: <sip:[email protected]>;tag=1939c44f To: <sip:[email protected]>;tag=35a7b2be8686cf178af07ddbcd51b507 Cseq: 1 NOTIFY Call-Id: ssc-7ab8c84ac338b5ab85e57d5678397...@28b70d10c2d661262affe918ab9e2955 Event: dialog Subscription-State: active;expires=3029 Content-Type: multipart/related;type="application/rlmi+xml";start="<[email protected]>";boundary="b88b51ab" Contact: <sip:[email protected]:5140;x-sipX-nonat> Date: Tue, 22 Dec 2009 09:21:55 GMT Max-Forwards: 19 User-Agent: sipXecs/4.0.1 sipXecs/rls (Linux) Accept-Language: en Require: eventlist Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK-sipXecs-556a4c572fd52534e95f061c79bd08e9eb14 Via: SIP/2.0/TCP 192.168.1.1:5140;branch=z9hG4bK-sipXecs-64f1e3211777a98386e7d0a930059f81e69a Content-Length: 1270 --b88b51ab CONTENT-ID: <[email protected]> CONTENT-TYPE: application/dialog-info+xml CONTENT-TRANSFER-ENCODING: binary <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="26" state="partial" entity="sip:[email protected]"> <dialog id="id8a7649db" call-id="[email protected]" local-tag="3768BB0E-B7DD9C6D" remote-tag="C6519D2C-BFAB40B7" direction="recipient"> <state>terminated</state> <local> <target uri="sip:[email protected]"> <param pname="x-line-id" pval="0" /> </target> </local> <remote> <identity display="User ext7200">sip:[email protected]</identity> <target uri="sip:[email protected]"> <param pname="x-sipX-nonat" pval="" /> </target> </remote> </dialog> </dialog-info> --b88b51ab CONTENT-ID: <[email protected]> CONTENT-TYPE: application/rlmi+xml CONTENT-TRANSFER-ENCODING: binary <?xml version="1.0"?> <list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:[email protected]" version="0" fullState="true"> <resource uri="sip:[email protected]"> <name>test</name> <instance id="s-4374e03528cdbbb1-258,1f60c3ad,2652880-28DC4BE7" state="active" cid="[email protected]"/> </resource> </list> --b88b51ab-- ==================================================================================================================== SIP/2.0 200 OK From: <sip:[email protected]>;tag=1939c44f To: <sip:[email protected]>;tag=35a7b2be8686cf178af07ddbcd51b507 Call-Id: ssc-7ab8c84ac338b5ab85e57d5678397...@28b70d10c2d661262affe918ab9e2955 Cseq: 1 NOTIFY Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK-sipXecs-556a4c572fd52534e95f061c79bd08e9eb14 Via: SIP/2.0/TCP 192.168.1.1:5140;branch=z9hG4bK-sipXecs-64f1e3211777a98386e7d0a930059f81e69a Date: Tue, 22 Dec 2009 09:23:09 GMT Contact: sip:192.168.1.99:62621 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PING, INFO, REGISTER, SUBSCRIBE, NOTIFY User-Agent: sipX/1.3.0 (WinNT) Content-Length: 0 ==================================================================================================================== NOTIFY sip:[email protected]:62621;x-sipX-nonat SIP/2.0 From: <sip:[email protected]>;tag=1939c44f To: <sip:[email protected]>;tag=35a7b2be8686cf178af07ddbcd51b507 Cseq: 2 NOTIFY Call-Id: ssc-7ab8c84ac338b5ab85e57d5678397...@28b70d10c2d661262affe918ab9e2955 Event: dialog Subscription-State: active;expires=3020 Content-Type: multipart/related;type="application/rlmi+xml";start="<[email protected]>";boundary="b00a5834" Contact: <sip:[email protected]:5140;x-sipX-nonat> Date: Tue, 22 Dec 2009 09:22:04 GMT Max-Forwards: 19 User-Agent: sipXecs/4.0.1 sipXecs/rls (Linux) Accept-Language: en Require: eventlist Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK-sipXecs-557da0dfb2e8307a7d1b0e75bbb6578cdcee Via: SIP/2.0/TCP 192.168.1.1:5140;branch=z9hG4bK-sipXecs-64f447b8e1acd8677beea39556a8880272ec Content-Length: 1266 --b00a5834 CONTENT-ID: <[email protected]> CONTENT-TYPE: application/dialog-info+xml CONTENT-TRANSFER-ENCODING: binary <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="27" state="partial" entity="sip:[email protected]"> <dialog id="id9af4cf16" call-id="[email protected]" local-tag="6053B995-3B3FB6F0" remote-tag="74365B68-DB3CF203" direction="recipient"> <state>early</state> <local> <target uri="sip:[email protected]"> <param pname="x-line-id" pval="0" /> </target> </local> <remote> <identity display="User ext7200">sip:[email protected]</identity> <target uri="sip:[email protected]"> <param pname="x-sipX-nonat" pval="" /> </target> </remote> </dialog> </dialog-info> --b00a5834 CONTENT-ID: <[email protected]> CONTENT-TYPE: application/rlmi+xml CONTENT-TRANSFER-ENCODING: binary <?xml version="1.0"?> <list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:[email protected]" version="1" fullState="false"> <resource uri="sip:[email protected]"> <name>test</name> <instance id="s-4374e03528cdbbb1-258,1f60c3ad,2652880-28DC4BE7" state="active" cid="[email protected]"/> </resource> </list> --b00a5834-- ==================================================================================================================== SIP/2.0 481 Transaction Does Not Exist From: <sip:[email protected]>;tag=1939c44f To: <sip:[email protected]>;tag=35a7b2be8686cf178af07ddbcd51b507 Call-Id: ssc-7ab8c84ac338b5ab85e57d5678397...@28b70d10c2d661262affe918ab9e2955 Cseq: 2 NOTIFY Via: SIP/2.0/UDP 192.168.1.1;branch=z9hG4bK-sipXecs-557da0dfb2e8307a7d1b0e75bbb6578cdcee Via: SIP/2.0/TCP 192.168.1.1:5140;branch=z9hG4bK-sipXecs-64f447b8e1acd8677beea39556a8880272ec Date: Tue, 22 Dec 2009 09:23:18 GMT Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PING, INFO, REGISTER, SUBSCRIBE, NOTIFY User-Agent: sipX/1.3.0 (WinNT) Content-Length: 0 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
