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: Robust Handing of 407 lacking call-id Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
speedvoip
Vetran
Vetran


Joined: August 07 2008
Location: Canada
Posts: 156
Posted: November 21 2008 at 9:41am | IP Logged Quote speedvoip
Hi Support:
It seems that u are going to release v6.0.0.3 right now. With latest product image, when 407 response missing header "Call-ID" is received for first outgoing Invite request, media engine not generate second Invite. Therefore call is frozing.
Over deep research, I found that literal expression of callid header for Invite request is "Call-Id", obvious not RFC3261 compliant, it should be "Call-ID". So maybe far end sip proxy can not parse Invite callid, so it is absent.
In my opinion, there are two things to be done.
I: Pls fix callid expression into proper form at media engine.
II: Make enhancement to be tolerant to 407 missing callid

Here is SIP log:

Code:

************* Log Opened (Nov 21 17:19:38) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [17:19:44.984] 0 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:6061;rport;branch=z9hG4bK0085b331
From: <sip:9991114@sip.checkcdr.com>;tag=858638
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 903ec77b-9634-4c5a-842e-706829fca54e-000002ec@192.168.1.100
CSeq: 8752780 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:6061>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.2  (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [17:19:45.393] 0 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP  192.168.1.100:6061;received=61.141.174.171;rport=57783;branc h=z9hG4bK0085b331
From: <sip:9991114@sip.checkcdr.com>;tag=858638
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 903ec77b-9634-4c5a-842e-706829fca54e-000002ec@192.168.1.100
CSeq: 8752780 REGISTER
Expires: 30
Contact:  <sip:9991114@192.168.1.100:6061>;user=phone;expires=30 
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [17:20:51.348] 66363 Ms, To: 217.72.243.59:5060) >>>>
INVITE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:6061;rport;branch=z9hG4bK0086944b
From: "SpeedVoIP SoftPhone" <sip:9991114@sip.checkcdr.com>;tag=869599
To: <sip:12127773456@sip.checkcdr.com>
Contact: <sip:9991114@192.168.1.100:6061>
Call-Id: 1edb5547-4397-4430-acb6-8b9636c34c59-000002ec@192.168.1.100
CSeq: 8834161 INVITE
Max-Forwards: 70
Organization:  6A8361EE-CBCB-4E2D-A584-76CEF7FBC2F5
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.2 (www.LanScapeCorp.com)
Content-Length: 226
User-Agent: LanScape VOIP Media Engine/6.0.0.2  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9991114 8804859 8804859 IN IP4 192.168.1.100
s=LanScape
c=IN IP4 192.168.1.100
t=0 0
m=audio 8930 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=ptime:20
a=fmtp:101 0-16




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [17:20:51.750] 66357 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.100:6061;rport;branch=z9hG4bK0086944b
From: "SpeedVoIP SoftPhone" <sip:9991114@sip.checkcdr.com>;tag=869599
To: <sip:12127773456@sip.checkcdr.com>
CSeq: 8834161 INVITE
Proxy-Authenticate: Digest realm="217.72.243.59", nonce="1227259257", algorithm=MD5
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, [17:20:54.458] 3110 Ms, To: 217.72.243.59:5060) >>>>
CANCEL sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:6061;rport;branch=z9hG4bK0086944b
From: "SpeedVoIP SoftPhone" <sip:9991114@sip.checkcdr.com>;tag=869599
To: <sip:12127773456@sip.checkcdr.com>
Call-Id: 1edb5547-4397-4430-acb6-8b9636c34c59-000002ec@192.168.1.100
CSeq: 8834161 CANCEL
Max-Forwards: 70
User-Agent: LanScape VOIP Media Engine/6.0.0.2  (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, [17:20:54.864] 3114 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 481 transaction does not exist
Via: SIP/2.0/UDP  192.168.1.100:6061;received=61.141.174.171;rport=57783;branc h=z9hG4bK0086944b
To: <sip:12127773456@sip.checkcdr.com>
From: "SpeedVoIP SoftPhone" <sip:9991114@sip.checkcdr.com>;tag=869599
Call-ID: 1edb5547-4397-4430-acb6-8b9636c34c59-000002ec@192.168.1.100
CSeq: 8834161 CANCEL
Server: Sansay/8.0
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, [17:21:11.618] 17161 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:6061;rport;branch=z9hG4bK0086f14b
From: <sip:9991114@sip.checkcdr.com>;tag=86a951
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 903ec77b-9634-4c5a-842e-706829fca54e-000002ec@192.168.1.100
CSeq: 8752781 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:6061>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.2  (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.2 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, [17:21:12.047] 17183 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP  192.168.1.100:6061;received=61.141.174.171;rport=57783;branc h=z9hG4bK0086f14b
From: <sip:9991114@sip.checkcdr.com>;tag=86a951
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 903ec77b-9634-4c5a-842e-706829fca54e-000002ec@192.168.1.100
CSeq: 8752781 REGISTER
Expires: 30
Contact:  <sip:9991114@192.168.1.100:6061>;user=phone;expires=30 
Content-Length: 0




************* Log Closed (Nov 21 17:21:12) *************



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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 21 2008 at 10:15am | IP Logged Quote support
Hi George,

Good post…..

You know, I look at a ton of SIP logs every week and I never noticed the difference between the media engine’s “Call-Id:” header case and the “Call-ID:” header case in SIP RFC3261.

We will change the case of the call ID header in the media engine to use “Call-ID:”. That way we can hopefully remove future possible inter-op issues with other SIP devices.

Note:
SIP headers (only the header portion) like call ID are supposed to be processes in a case insensitive manner. If I am wrong, please correct me.

Question 1:
Why does the SIP server at checkcdr.com not respond with proper Call ID headers?

Question 2:
Is it because the call ID header case the media engine is using? SIP header case should not make a difference.

Question 3:
If you modify all the transmitted SIP messages of the media engine to use “Call-ID:” headers, will the server respond properly with call ID headers in the responses? It would be a good test to perform. Simply modify any transmitted SIP message by handling the SipModifySipMessage immediate event and calling the ModifySipMessage() API proc.

Not sure if we want to tolerate missing call ID headers in call setups. Tell me why we should support this – it sounds like a hack. Shouldn’t they fix their server instead?


Thanks,


Randal

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: November 21 2008 at 1:27pm | IP Logged Quote support
Hi George,

Just for the heck of it, we tried calling the sip.checkcdr.com domain again from our lab using the updated version v6.0.0.3 of the media engine that uses the “Call-ID” header update. It seems the “Sansay-SIP/8.0” border controller/switch at that location does not handle the “Call-Id” header case. This is a bug in their code and they should fix it.

Anyway, just so you are updated, the “Call-ID” header update allows everything to function as expected. We will definitely keep this change in the media engine so we do not have problems in the future.

Good job on your part for having a “sharp eye”. Thank you.

Here is a log of various call operations:

Code:

************* Log Opened (Nov 21 13:23:57) *************

>>>> TxTxTxTxTx (#1, [13:24:05.578] 0 Ms, To: 216.109.159.141:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e333f7
From: <sip:9991114@sip.checkcdr.com>;tag=6e34e6f
To: <sip:9991114@sip.checkcdr.com>
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879847 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#1, [13:24:05.781] 0 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e333f7
From: <sip:9991114@sip.checkcdr.com>;tag=6e34e6f
To: <sip:9991114@sip.checkcdr.com>
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879847 REGISTER
WWW-Authenticate: Digest realm="216.109.159.141", nonce="1227295332", algorithm=MD5
Content-Length: 0



>>>> TxTxTxTxTx (#2, [13:24:05.781] 203 Ms, To: 216.109.159.141:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e351cf
From: <sip:9991114@sip.checkcdr.com>;tag=6e34e6f
To: <sip:9991114@sip.checkcdr.com>
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879848 REGISTER
Authorization: Digest algorithm=md5,nonce="1227295332",realm="216.109.159.141",
 response="1ff6de5349fc4b1d26b19eff16c4074d",uri="sip:sip.checkcdr.com",username="9991114"
Expires: 3600
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#2, [13:24:05.953] 172 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e351cf
To: <sip:9991114@sip.checkcdr.com>
From: <sip:9991114@sip.checkcdr.com>;tag=6e34e6f
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879848 REGISTER
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
Expires: 30
Content-Length: 0



>>>> TxTxTxTxTx (#3, [13:24:11.484] 5703 Ms, To: 216.109.159.141:5060) >>>>
INVITE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e37504
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e370b9;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>
Contact: <sip:9991114@192.168.1.2:5088>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902016 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 438
User-Agent: LanScape Utility Softphone/5.10.0.5
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9991114 115548468 115548468 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 12006 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#3, [13:24:11.625] 5672 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e37504
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e370b9;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902016 INVITE
Proxy-Authenticate: Digest realm="216.109.159.141", nonce="1227295338", algorithm=MD5
Content-Length: 0



>>>> TxTxTxTxTx (#4, [13:24:11.625] 141 Ms, To: 216.109.159.141:5060) >>>>
ACK sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e37504
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e370b9;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902016 ACK
Max-Forwards: 70
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#5, [13:24:11.625] 0 Ms, To: 216.109.159.141:5060) >>>>
INVITE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e37592
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>
Contact: <sip:9991114@192.168.1.2:5088>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902158 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Proxy-Authorization: Digest algorithm=md5,nonce="1227295338",realm="216.109.159.141",
 response="7c6d6f2e8aa2581f7f238ae7d70adc64",uri="sip:12127773456@sip.checkcdr.com",username="9991114"
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 438
User-Agent: LanScape Utility Softphone/5.10.0.5
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9991114 115548609 115548609 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 12006 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#4, [13:24:11.734] 109 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e37592
To: <sip:12127773456@sip.checkcdr.com>
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902158 INVITE
Server: Sansay-SIP/8.0
Content-Length: 0



<<<< RxRxRxRxRx (#5, [13:24:14.812] 3078 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e37592
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902158 INVITE
Server: Sansay-SIP/8.0
Content-Type: application/sdp
Content-Length: 241

v=0
o=Sansay-SPX 11 11 IN IP4 216.109.159.171
s=Session Controller
c=IN IP4 216.109.159.171
t=0 0
m=audio 12016 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


<<<< RxRxRxRxRx (#6, [13:24:14.921] 109 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e37592
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902158 INVITE
Server: Sansay-SIP/8.0
Contact: <sip:216.109.159.141:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 241

v=0
o=Sansay-SPX 11 11 IN IP4 216.109.159.171
s=Session Controller
c=IN IP4 216.109.159.171
t=0 0
m=audio 12016 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


>>>> TxTxTxTxTx (#6, [13:24:14.921] 3296 Ms, To: 216.109.159.141:5060) >>>>
ACK sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e37592
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902158 ACK
Max-Forwards: 70
Route: <sip:216.109.159.141>
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#7, [13:25:23.468] 68547 Ms, To: 216.109.159.141:5060) >>>>
INVITE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e4430c
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Contact: <sip:9991114@192.168.1.2:5088>
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902159 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 434
User-Agent: LanScape Utility Softphone/5.10.0.5
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9991114 115620453 115620453 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 12006 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#7, [13:25:23.562] 68641 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4430c
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902159 INVITE
Server: Sansay/8.0
Content-Length: 0



<<<< RxRxRxRxRx (#8, [13:25:23.890] 328 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4430c
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902159 INVITE
Server: Sansay-SIP/8.0
Contact: <sip:216.109.159.141:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 241

v=0
o=Sansay-SPX 11 12 IN IP4 216.109.159.171
s=Session Controller
c=IN IP4 216.109.159.171
t=0 0
m=audio 12016 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


>>>> TxTxTxTxTx (#8, [13:25:23.906] 438 Ms, To: 216.109.159.141:5060) >>>>
ACK sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4430c
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902159 ACK
Max-Forwards: 70
Route: <sip:216.109.159.141>
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#9, [13:25:26.671] 2765 Ms, To: 216.109.159.141:5060) >>>>
INVITE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e4568b
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Contact: <sip:9991114@192.168.1.2:5088>
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902160 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 438
User-Agent: LanScape Utility Softphone/5.10.0.5
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=9991114 115623656 115623656 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 12006 RTP/AVP 18 97 0 8 124 125 126 101
a=rtpmap:18 G729/8000/1
a=rtpmap:97 ILBC/8000/1
a=rtpmap:0 PCMU/8000/1
a=rtpmap:8 PCMA/8000/1
a=rtpmap:124 PCM/8000/1
a=rtpmap:125 PCM/11050/1
a=rtpmap:126 PCM/22050/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:18 annexb=no
a=fmtp:97 mode=20
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#9, [13:25:26.796] 2906 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4568b
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902160 INVITE
Server: Sansay/8.0
Content-Length: 0



<<<< RxRxRxRxRx (#10, [13:25:27.562] 766 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4568b
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902160 INVITE
Server: Sansay-SIP/8.0
Contact: <sip:216.109.159.141:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 241

v=0
o=Sansay-SPX 11 13 IN IP4 216.109.159.171
s=Session Controller
c=IN IP4 216.109.159.171
t=0 0
m=audio 12016 RTP/AVP 18 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20


>>>> TxTxTxTxTx (#10, [13:25:27.578] 907 Ms, To: 216.109.159.141:5060) >>>>
ACK sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4568b
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902160 ACK
Max-Forwards: 70
Route: <sip:216.109.159.141>
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#11, [13:25:39.031] 11453 Ms, To: 216.109.159.141:5060) >>>>
BYE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e484e9
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902161 BYE
Max-Forwards: 70
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#11, [13:25:39.109] 11547 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e484e9
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902161 BYE
Proxy-Authenticate: Digest realm="216.109.159.141", nonce="1227295426", algorithm=MD5
Content-Length: 0



>>>> TxTxTxTxTx (#12, [13:25:39.125] 94 Ms, To: 216.109.159.141:5060) >>>>
BYE sip:12127773456@sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e493df
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902162 BYE
Max-Forwards: 70
Proxy-Authorization: Digest algorithm=md5,nonce="1227295426",realm="216.109.159.141",
 response="e3c0bf3d146bc3aa1bb51357a3b7e1d0",uri="sip:12127773456@sip.checkcdr.com",username="9991114"
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#12, [13:25:39.234] 125 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e493df
To: <sip:12127773456@sip.checkcdr.com>;tag=16015563-tdb345
From: "LanScape Phone 9991114" <sip:9991114@sip.checkcdr.com>;tag=6e37147;x-UaId=xxxxx-yyyy-zzzzzz
Call-ID: 00ecafd1-903f-4633-9cd0-3dcbbfe379bb-00002a94@192.168.1.2
CSeq: 14902162 BYE
Server: Sansay/8.0
Content-Length: 0



>>>> TxTxTxTxTx (#13, [13:25:43.468] 4343 Ms, To: 216.109.159.141:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK06e4d0b1
From: <sip:9991114@sip.checkcdr.com>;tag=6e488b2
To: <sip:9991114@sip.checkcdr.com>
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879849 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.5
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.3 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#13, [13:25:43.609] 4375 Ms, From: 216.109.159.141:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;rport=5088;branch=z9hG4bK06e4d0b1
From: <sip:9991114@sip.checkcdr.com>;tag=6e488b2
To: <sip:9991114@sip.checkcdr.com>
Call-ID: b27dd225-552e-4bc4-a467-d1249a237e3e-00002a94@192.168.1.2
CSeq: 14879849 REGISTER
Expires: 30
Contact: <sip:9991114@192.168.1.2:5088>;user=phone;expires=30
Content-Length: 0


************* Log Closed (Nov 21 13:25:46) *************




Thanks,


Randal


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


Joined: August 07 2008
Location: Canada
Posts: 156
Posted: November 22 2008 at 12:31am | IP Logged Quote speedvoip
Hi Support:
Pls give me latest v6.0.0.3 product image via email. Thanks
Back to Top View speedvoip's Profile Search for other posts by speedvoip Visit speedvoip's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 22 2008 at 7:50am | IP Logged Quote support
Hi George,

We are working today (Saturday). We will send it out for you to test. Repost your test results.

Support

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

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