Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

LanScape VOIP Media Engine™ - Pre-Sales Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Subject Topic: missing tag in To: header with SUBSCRIBE Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
jmatthewsr
Junior
Junior


Joined: April 09 2008
Posts: 40
Posted: April 16 2008 at 5:25pm | IP Logged Quote jmatthewsr
Testing against the multi-session conf example (5.12.8.1), when the conf app receives a SUBSCRIBE, it does not append a Tag to the To: header in the 200Ok. I beleive this is what is causing a UA (Aastra 57i) to repeatadly send SUBSCRIBE requests. I didn't test other out-of-dialog requests.

thanks,

-justin
Back to Top View jmatthewsr's Profile Search for other posts by jmatthewsr
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 17 2008 at 3:03pm | IP Logged Quote support
Hi Justin,

Ok… we will have to look into that. Feel free to post a SIP log to this thread. We’d like to see it. When you post SIP log data, place the log data into a “code” block (see the forum codes).

Example:

Code:

   SIP log data…




Support


Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: April 17 2008 at 4:26pm | IP Logged Quote support
Hi Justin,

Good eye. We fixed it this afternoon. We are surprised this was not reported sooner. It will be added to the next release.

Here is a SIP log of the media engine sending a SUBSCRIBE request to itself… no proxy was configured or used.

Code:

************* Log Opened (Apr 17 16:24:24) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#1, 33102812 Ms, To: 192.168.1.2:5066) >>>>
SUBSCRIBE sip:333@192.168.1.2:5066 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5066;rport;branch=z9hG4bK01f9349b
From: <sip:333@192.168.1.2:5066>;tag=1f96400
To: <sip:333@192.168.1.2:5066>
Call-Id: 65036ef2-b7ea-4e4a-87bc-ceb4e71157c0-00002470@192.168.1.2
CSeq: 16325654 SUBSCRIBE
Expires: 3600
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:5066>
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Param1, Param2, Param3"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#1, 33102812 Ms, From: 192.168.1.2:5066) <<<<
SUBSCRIBE sip:333@192.168.1.2:5066 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5066;rport;branch=z9hG4bK01f9349b
From: <sip:333@192.168.1.2:5066>;tag=1f96400
To: <sip:333@192.168.1.2:5066>
Call-Id: 65036ef2-b7ea-4e4a-87bc-ceb4e71157c0-00002470@192.168.1.2
CSeq: 16325654 SUBSCRIBE
Expires: 3600
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:5066>
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Param1, Param2, Param3"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#2, 0 Ms, To: 192.168.1.2:5066) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5066;rport=5066;branch=z9hG4bK01f9349b
From: <sip:333@192.168.1.2:5066>;tag=1f96400
To: <sip:333@192.168.1.2:5066>;tag=d21e0200
Call-Id: 65036ef2-b7ea-4e4a-87bc-ceb4e71157c0-00002470@192.168.1.2
CSeq: 16325654 SUBSCRIBE
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Event: vphone-test-event-0;param="Param1, Param2, Param3"
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#2, 0 Ms, From: 192.168.1.2:5066) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5066;rport=5066;branch=z9hG4bK01f9349b
From: <sip:333@192.168.1.2:5066>;tag=1f96400
To: <sip:333@192.168.1.2:5066>;tag=d21e0200
Call-Id: 65036ef2-b7ea-4e4a-87bc-ceb4e71157c0-00002470@192.168.1.2
CSeq: 16325654 SUBSCRIBE
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Event: vphone-test-event-0;param="Param1, Param2, Param3"
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#3, 2469 Ms, To: 192.168.1.2:5066) >>>>
SUBSCRIBE sip:333@192.168.1.2:5066 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5066;rport;branch=z9hG4bK01f962ef
From: <sip:333@192.168.1.2:5066>;tag=1f97064
To: <sip:333@192.168.1.2:5066>
Call-Id: 62fa7496-afed-4a34-9011-40598b3a4f1a-00002470@192.168.1.2
CSeq: 16354582 SUBSCRIBE
Expires: 0
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:5066>
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Param1, Param2, Param3"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#3, 2469 Ms, From: 192.168.1.2:5066) <<<<
SUBSCRIBE sip:333@192.168.1.2:5066 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5066;rport;branch=z9hG4bK01f962ef
From: <sip:333@192.168.1.2:5066>;tag=1f97064
To: <sip:333@192.168.1.2:5066>
Call-Id: 62fa7496-afed-4a34-9011-40598b3a4f1a-00002470@192.168.1.2
CSeq: 16354582 SUBSCRIBE
Expires: 0
Max-Forwards: 70
Contact: <sip:333@192.168.1.2:5066>
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
Event: vphone-test-event-0;param="Param1, Param2, Param3"
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#4, 0 Ms, To: 192.168.1.2:5066) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5066;rport=5066;branch=z9hG4bK01f962ef
From: <sip:333@192.168.1.2:5066>;tag=1f97064
To: <sip:333@192.168.1.2:5066>;tag=c9680900
Call-Id: 62fa7496-afed-4a34-9011-40598b3a4f1a-00002470@192.168.1.2
CSeq: 16354582 SUBSCRIBE
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Event: vphone-test-event-0;param="Param1, Param2, Param3"
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#4, 0 Ms, From: 192.168.1.2:5066) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5066;rport=5066;branch=z9hG4bK01f962ef
From: <sip:333@192.168.1.2:5066>;tag=1f97064
To: <sip:333@192.168.1.2:5066>;tag=c9680900
Call-Id: 62fa7496-afed-4a34-9011-40598b3a4f1a-00002470@192.168.1.2
CSeq: 16354582 SUBSCRIBE
User-Agent: LanScape VOIP Media Engine/5.12.8.3  (www.LanScapeCorp.com)
x-CustomHeader-Extension-333: "This is a modified transmitted SIP message."
Event: vphone-test-event-0;param="Param1, Param2, Param3"
Content-Length: 0

************* Log Closed (Apr 17 16:25:12) *************



Thanks,


Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
jmatthewsr
Junior
Junior


Joined: April 09 2008
Posts: 40
Posted: April 17 2008 at 5:09pm | IP Logged Quote jmatthewsr
Thanks for the quick turnaround.
Back to Top View jmatthewsr's Profile Search for other posts by jmatthewsr
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights