Author |
|
speedvoip Vetran
Joined: August 07 2008 Location: Canada Posts: 156
|
Posted: November 19 2008 at 3:02am | IP Logged
|
|
|
Hi Support:
With latest media engine v6 release, I have found registration interop issue with my customer's sip proxy server. By using sip account provided by my customer, eyebeam is registered with sip proxy successfully, but single line phone example is failed with prompt "register time out".
Testing parameter is as follows:
sip proxy: sip.checkcdr.com:5060
user name: 9991114
password: 445566
SIP log as follows:
Code:
************* Log Opened (Nov 19 16:59:51) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [16:59:57.287] 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:5060;rport;branch=z9hG4bK01580149
From: <sip:9991114@sip.checkcdr.com>;tag=157edb3
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747124 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [16:59:57.852] 0 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01580149
From: <sip:9991114@sip.checkcdr.com>;tag=157edb3
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747124 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [17:00:06.291] 9004 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0157ff7a
From: <sip:9991114@sip.checkcdr.com>;tag=157b780
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747125 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [17:00:06.796] 8944 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0157ff7a
From: <sip:9991114@sip.checkcdr.com>;tag=157b780
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747125 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, [17:00:15.294] 9003 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01584204
From: <sip:9991114@sip.checkcdr.com>;tag=157f33e
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747126 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, [17:00:15.820] 9024 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01584204
From: <sip:9991114@sip.checkcdr.com>;tag=157f33e
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747126 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, [17:00:24.299] 9004 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01583b15
From: <sip:9991114@sip.checkcdr.com>;tag=158488a
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747127 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, [17:00:24.923] 9103 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01583b15
From: <sip:9991114@sip.checkcdr.com>;tag=158488a
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747127 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#5, [17:00:33.302] 9004 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158938f
From: <sip:9991114@sip.checkcdr.com>;tag=1584db7
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747128 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#5, [17:00:33.898] 8975 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158938f
From: <sip:9991114@sip.checkcdr.com>;tag=1584db7
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747128 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#6, [17:00:42.304] 9002 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158a39a
From: <sip:9991114@sip.checkcdr.com>;tag=158ad5c
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747129 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#6, [17:00:42.827] 8929 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158a39a
From: <sip:9991114@sip.checkcdr.com>;tag=158ad5c
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747129 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#7, [17:00:51.306] 9002 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158d524
From: <sip:9991114@sip.checkcdr.com>;tag=1587d7c
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747130 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#7, [17:00:51.820] 8993 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158d524
From: <sip:9991114@sip.checkcdr.com>;tag=1587d7c
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747130 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085203", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#8, [17:01:00.310] 9003 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158cc17
From: <sip:9991114@sip.checkcdr.com>;tag=158e54d
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747131 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#8, [17:01:00.840] 9020 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158cc17
From: <sip:9991114@sip.checkcdr.com>;tag=158e54d
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747131 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085266", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#9, [17:01:09.312] 9003 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158af70
From: <sip:9991114@sip.checkcdr.com>;tag=158d46e
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747132 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#9, [17:01:09.813] 8973 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158af70
From: <sip:9991114@sip.checkcdr.com>;tag=158d46e
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747132 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085266", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#10, [17:01:18.315] 9003 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158ff64
From: <sip:9991114@sip.checkcdr.com>;tag=158dc71
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747133 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#10, [17:01:18.818] 9005 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0158ff64
From: <sip:9991114@sip.checkcdr.com>;tag=158dc71
To: <sip:9991114@sip.checkcdr.com>
CSeq: 5747133 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227085266", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#11, [17:01:27.317] 9002 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01590923
From: <sip:9991114@sip.checkcdr.com>;tag=15906c2
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 81a161d4-878d-4223-a7f5-e858adfd3bc5-00001750@192.168.1.100
CSeq: 5747134 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
|
|
|
|
Back to Top |
|
|
speedvoip Vetran
Joined: August 07 2008 Location: Canada Posts: 156
|
Posted: November 19 2008 at 3:20am | IP Logged
|
|
|
Hi Support:
Update last post on registration failure as follows: 401 response can be received from far end proxy, but media engine can not generate second register request with authorization.
Lastest SIP Log:
Code:
************* Log Opened (Nov 19 17:15:48) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [17:15:54.634] 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:5060;rport;branch=z9hG4bK016688de
From: <sip:9991114@sip.checkcdr.com>;tag=16692ef
To: <sip:9991114@sip.checkcdr.com>
Call-Id: e68d38bb-0098-4e60-b0e6-74aafc63ca94-00000950@192.168.1.100
CSeq: 6707950 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [17:15:55.084] 0 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK016688de
From: <sip:9991114@sip.checkcdr.com>;tag=16692ef
To: <sip:9991114@sip.checkcdr.com>
CSeq: 6707950 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227086161", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [17:16:03.646] 9013 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01669b29
From: <sip:9991114@sip.checkcdr.com>;tag=166532f
To: <sip:9991114@sip.checkcdr.com>
Call-Id: e68d38bb-0098-4e60-b0e6-74aafc63ca94-00000950@192.168.1.100
CSeq: 6707951 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [17:16:04.205] 9121 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK01669b29
From: <sip:9991114@sip.checkcdr.com>;tag=166532f
To: <sip:9991114@sip.checkcdr.com>
CSeq: 6707951 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227086161", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, [17:16:12.649] 9003 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0166ddb3
From: <sip:9991114@sip.checkcdr.com>;tag=1668eed
To: <sip:9991114@sip.checkcdr.com>
Call-Id: e68d38bb-0098-4e60-b0e6-74aafc63ca94-00000950@192.168.1.100
CSeq: 6707952 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, [17:16:13.213] 9008 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0166ddb3
From: <sip:9991114@sip.checkcdr.com>;tag=1668eed
To: <sip:9991114@sip.checkcdr.com>
CSeq: 6707952 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227086161", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, [17:16:21.651] 9002 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0166d6c4
From: <sip:9991114@sip.checkcdr.com>;tag=166e439
To: <sip:9991114@sip.checkcdr.com>
Call-Id: e68d38bb-0098-4e60-b0e6-74aafc63ca94-00000950@192.168.1.100
CSeq: 6707953 REGISTER
Expires: 1800
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.100:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.0 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, [17:16:22.535] 9322 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.100:5060;rport;branch=z9hG4bK0166d6c4
From: <sip:9991114@sip.checkcdr.com>;tag=166e439
To: <sip:9991114@sip.checkcdr.com>
CSeq: 6707953 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227086161", algorithm=MD5
Content-Length: 0
************* Log Closed (Nov 19 17:16:30) *************
|
|
|
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: November 19 2008 at 10:33am | IP Logged
|
|
|
Hi George,
We will look into this right away. Don’t worry, we will fix it whatever it is.
Support
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: November 19 2008 at 10:51am | IP Logged
|
|
|
George,
We are looking at this right now. Will repost with results shortly. It appears to be another "WWW-Authenticate:" SIP header parsing issue.
Hmmmm......
Support
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: November 19 2008 at 12:05pm | IP Logged
|
|
|
Hi George,
We see what the problem is: There is no call ID header in the 401 Unauthorized SIP response. The media engine needs a Call ID header in order to properly map the 401 response to the original REGISTER request.
What server (product name, version, etc) are they using at checkcdr.com? We are curious.
We can still create a workable fix for this but we are under the impression that all SIP responses MUST contain a “Call-Ud:” header as per the SIP RFC3261.
Hmm……
We have never seen this SIP behavior before. Another issue now is this: If other SIP requests are challenged by the checkcdr.com VOIP domain, will any of the challenge responses contain call ID headers? If not, then we may have a larger problem. Hopefully this behavior is restricted only to REGISTER requests.
We will test a fix shortly.
Support
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: November 19 2008 at 2:13pm | IP Logged
|
|
|
Hi George,
We have implemented a fix that will be in the v6.0.0.1 product image. As far as we can tell, the challenge response should have a call id header. Maybe you can look into why its not present and post back here.
Anyway, after the appropriate update to the media engine, all functions as expected.
Here is a log registering and the un-registering to the server (uses media engine v6.0.0.1):
Code:
************* Log Opened (Nov 19 14:05:07) *************
>>>> TxTxTxTxTx (#1, [14:05:13.187] 0 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK018c5c64
From: <sip:9991114@sip.checkcdr.com>;tag=18c3b3a
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 9d709107-8a54-4d57-bf46-6806304da4c8-00001968@192.168.1.2
CSeq: 9194439 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.1 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#1, [14:05:13.421] 0 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK018c5c64
From: <sip:9991114@sip.checkcdr.com>;tag=18c3b3a
To: <sip:9991114@sip.checkcdr.com>
CSeq: 9194439 REGISTER
WWW-Authenticate: Digest realm="217.72.243.59", nonce="1227124999", algorithm=MD5
Content-Length: 0
>>>> TxTxTxTxTx (#2, [14:05:13.421] 234 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK018c75a0
From: <sip:9991114@sip.checkcdr.com>;tag=18c3b3a
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 9d709107-8a54-4d57-bf46-6806304da4c8-00001968@192.168.1.2
CSeq: 9194440 REGISTER
Authorization: Digest algorithm=md5,nonce="1227124999",realm="217.72.243.59",
response="1161d1c154644817664184f39d4bc741",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.4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.1 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#2, [14:05:13.640] 219 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK018c75a0
To: <sip:9991114@sip.checkcdr.com>
From: <sip:9991114@sip.checkcdr.com>;tag=18c3b3a
Call-ID: 9d709107-8a54-4d57-bf46-6806304da4c8-00001968@192.168.1.2
CSeq: 9194440 REGISTER
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
Expires: 30
Content-Length: 0
>>>> TxTxTxTxTx (#3, [14:05:23.890] 10469 Ms, To: 217.72.243.59:5060) >>>>
REGISTER sip:sip.checkcdr.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5088;rport;branch=z9hG4bK018c8519
From: <sip:9991114@sip.checkcdr.com>;tag=18c3d1e
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 9d709107-8a54-4d57-bf46-6806304da4c8-00001968@192.168.1.2
CSeq: 9194441 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:9991114@192.168.1.2:5088>;user=phone
User-Agent: LanScape Utility Softphone/5.10.0.4
x-CustomHeader-Extension-9991114: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.1 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRx (#3, [14:05:24.078] 10438 Ms, From: 217.72.243.59:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5088;received=75.73.107.63;
rport=5088;branch=z9hG4bK018c8519
From: <sip:9991114@sip.checkcdr.com>;tag=18c3d1e
To: <sip:9991114@sip.checkcdr.com>
Call-Id: 9d709107-8a54-4d57-bf46-6806304da4c8-00001968@192.168.1.2
CSeq: 9194441 REGISTER
Expires: 30
Contact: <sip:9991114@192.168.1.2:5088>;user=phone;expires=30
Content-Length: 0
************* Log Closed (Nov 19 14:05:38) *************
|
|
|
Support
|
Back to Top |
|
|
speedvoip Vetran
Joined: August 07 2008 Location: Canada Posts: 156
|
Posted: November 20 2008 at 3:29am | IP Logged
|
|
|
Hi Support:
Without doubt, it is obvious that 401 response from sip proxy server is not standard one. So media engine must be tolerant. So if fixed, pls give us v6.0.0.1 product image for own testing via email. Thanks!!
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: November 20 2008 at 9:39am | IP Logged
|
|
|
George,
We just sent you the update that will fix this issue.
Thanks,
Support
|
Back to Top |
|
|
|
|