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™ - Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Subject Topic: 403 Forbidden Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
PaulR
Intermediate
Intermediate


Joined: June 24 2011
Location: Philippines
Posts: 9
Posted: June 24 2011 at 1:00pm | IP Logged Quote PaulR
Hi Support,

Need help with our issue, when we try to place a call it failed due to the error code "403 Forbidden".

Basically what we are doing is to use SBC to proxy everything to/from the agent/acd.

We already did it in a softphone(Eyebeam) but when we tried it in lanscape, it failed. The Registration was successful but when trying to initiate a call/INVITE, the issue occurs.
Below is the sip message log of the whole process from registration to intitaiting a call

Code:

************* Log Opened (Jun 22 04:00:36) *************

Log file contents deleted....

************* Log Closed (Jun 22 04:00:47) *************



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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 24 2011 at 2:36pm | IP Logged Quote support
Hi Paul,

Can you re-post that SIP log again with appropriate <cr><lf> endings. Its too hard to read....

Thanks





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: June 24 2011 at 2:38pm | IP Logged Quote support
Thanks Paul. New log file:

(Note: Ip addresses changed)

Code:


************* Log Opened (Jun 22 04:00:36) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [04:00:36.258] 0 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:5060;rport;branch=z9hG4bK2065c785
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672826 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:5060>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [04:00:36.383] 0 Ms, From: 10.112.75.14:5060) <<<<




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [04:00:36.508] 125 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:5060;rport=31869;received=234.124.15.13;branch=z9hG4bK2065c785
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672826 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, [04:00:36.633] 125 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.107.25.202:5060;rport=31869;received=234.124.15.13;branch=z9hG4bK2065c785
WWW-Authenticate: Digest realm="infonxx.local",nonce="23052d176368a009a755bce3962f54154e00f885",qop="auth"
To: <sip:4108@ca1acd04.infonxx.local>;tag=3517678637-406516
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672826 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@10.107.25.202:5060>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [04:00:36.633] 375 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 234.124.15.13:31869;rport;branch=z9hG4bK2065909d
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672827 REGISTER
Authorization: Digest algorithm=md5,cnonce="0065ab71",nc=00000001,
 nonce="23052d176368a009a755bce3962f54154e00f885",qop=auth,realm="infonxx.local",
 response="198263e40b6dcc1f75d447f540520944",uri="sip:ca1acd04.infonxx.local",username="4108"
Expires: 3600
Max-Forwards: 70
Contact: <sip:4108@234.124.15.13:31869>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, [04:00:36.883] 250 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065909d
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672827 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#5, [04:00:36.993] 110 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065909d
To: <sip:4108@ca1acd04.infonxx.local>;tag=3517678637-406516
From: <sip:4108@ca1acd04.infonxx.local>;tag=20658f3b
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672827 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@234.124.15.13:31869>
Expires: 179
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, [04:00:38.008] 1375 Ms, To: 200.222.129.15:5060) >>>>
INVITE sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:31869;rport;branch=z9hG4bK2065781a
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
To: <sip:*88@ca1acd04.infonxx.local>
Contact: <sip:4108@234.124.15.13:31869>
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 INVITE
Max-Forwards: 70
Organization: 21C1D6D4-7A73-41FB-B20E-F14C1AE96830
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 171
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=4108 543513750 543513750 IN IP4 234.124.15.13
s=LanScape
c=IN IP4 234.124.15.13
t=0 0
m=audio 3044 RTP/AVP 0
a=rtpmap:0 PCMU/8000/1
a=sendrecv
a=ptime:20




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#6, [04:00:38.258] 1265 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065781a
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
To: <sip:*88@ca1acd04.infonxx.local>
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 INVITE
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#7, [04:00:38.258] 0 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.107.25.202:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065781a
To: <sip:*88@ca1acd04.infonxx.local>;tag=3517678639-43210
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:*88@200.222.129.15:5060>
Call-Info: <sip:200.222.129.15>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, [04:00:38.555] 547 Ms, To: 200.222.129.15:5060) >>>>
ACK sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:31869;received=234.124.15.13;rport=31869;branch=z9hG4bK2065781a
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
To: <sip:*88@ca1acd04.infonxx.local>;tag=3517678639-43210
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 ACK
Max-Forwards: 70
Route: <sip:*88@200.222.129.15>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#8, [04:00:38.758] 500 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.107.25.202:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065781a
To: <sip:*88@ca1acd04.infonxx.local>;tag=3517678639-43210
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:*88@200.222.129.15:5060>
Call-Info: <sip:200.222.129.15>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#5, [04:00:38.774] 219 Ms, To: 200.222.129.15:5060) >>>>
ACK sip:*88@200.222.129.15 SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:31869;received=234.124.15.13;rport=31869;branch=z9hG4bK2065781a
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065a4bb
To: <sip:*88@ca1acd04.infonxx.local>;tag=3517678639-43210
Call-ID: 39da99be-790c-4dae-a7a3-bb41cd16b8ff-00001760@234.124.15.13
CSeq: 6664151 ACK
Max-Forwards: 70
Route: <sip:*88@200.222.129.15>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#6, [04:00:46.227] 7453 Ms, To: 200.222.129.15:5060) >>>>
INVITE sip:*89@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:31869;rport;branch=z9hG4bK2065e809
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065e166
To: <sip:*89@ca1acd04.infonxx.local>
Contact: <sip:4108@234.124.15.13:31869>
Call-ID: 6a02e59f-f649-4c25-9ce9-6926c53e46d0-00001760@234.124.15.13
CSeq: 6684213 INVITE
Max-Forwards: 70
Organization: 21C1D6D4-7A73-41FB-B20E-F14C1AE96830
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 171
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=4108 543521953 543521953 IN IP4 234.124.15.13
s=LanScape
c=IN IP4 234.124.15.13
t=0 0
m=audio 3044 RTP/AVP 0
a=rtpmap:0 PCMU/8000/1
a=sendrecv
a=ptime:20




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#9, [04:00:46.446] 7688 Ms, From: 10.112.75.14:5060) <<<<




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#10, [04:00:46.477] 31 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065e809
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065e166
To: <sip:*89@ca1acd04.infonxx.local>
Call-ID: 6a02e59f-f649-4c25-9ce9-6926c53e46d0-00001760@234.124.15.13
CSeq: 6684213 INVITE
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#11, [04:00:46.477] 0 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.107.25.202:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065e809
To: <sip:*89@ca1acd04.infonxx.local>;tag=3517678647-259323
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065e166
Call-ID: 6a02e59f-f649-4c25-9ce9-6926c53e46d0-00001760@234.124.15.13
CSeq: 6684213 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:*89@200.222.129.15:5060>
Call-Info: <sip:200.222.129.15>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#7, [04:00:46.493] 266 Ms, To: 200.222.129.15:5060) >>>>
ACK sip:*89@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:31869;received=234.124.15.13;rport=31869;branch=z9hG4bK2065e809
From: 4108 <sip:4108@ca1acd04.infonxx.local>;tag=2065e166
To: <sip:*89@ca1acd04.infonxx.local>;tag=3517678647-259323
Call-ID: 6a02e59f-f649-4c25-9ce9-6926c53e46d0-00001760@234.124.15.13
CSeq: 6684213 ACK
Max-Forwards: 70
Route: <sip:*89@200.222.129.15>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#8, [04:00:46.649] 156 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 234.124.15.13:31869;rport;branch=z9hG4bK2065c67e
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672828 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:4108@234.124.15.13:31869>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#12, [04:00:46.899] 422 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065c67e
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672828 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#13, [04:00:47.024] 125 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK2065c67e
WWW-Authenticate: Digest realm="infonxx.local",nonce="2292f8e93bf24602bc0593509046898f4e00f88f",qop="auth"
To: <sip:4108@ca1acd04.infonxx.local>;tag=3517678647-796233
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672828 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@234.124.15.13:31869>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#9, [04:00:47.024] 375 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 234.124.15.13:31869;rport;branch=z9hG4bK20659891
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672829 REGISTER
Authorization: Digest algorithm=md5,cnonce="0065e958",nc=00000001,
nonce="2292f8e93bf24602bc0593509046898f4e00f88f",qop=auth,re alm="infonxx.local",
response="1a910689006f9a7e4a050d6d12f59f87",uri="sip:ca1acd0 4.infonxx.local",username="4108"
Expires: 0
Max-Forwards: 70
Contact: <sip:4108@234.124.15.13:31869>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#14, [04:00:47.274] 250 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK20659891
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672829 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#15, [04:00:47.383] 109 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 234.124.15.13:31869;rport=31869;received=234.124.15.13;branch=z9hG4bK20659891
To: <sip:4108@ca1acd04.infonxx.local>;tag=3517678647-796233
From: <sip:4108@ca1acd04.infonxx.local>;tag=20657e83
Call-ID: 10630fb4-0a7b-4949-96db-7152853aa8ea-00001760@10.107.25.202
CSeq: 6672829 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




************* Log Closed (Jun 22 04:00:47) *************


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: June 24 2011 at 3:13pm | IP Logged Quote support
Paul,

I don't see anything that looks like a mistake in the INVITE request that was sent to the sipXecs.

Is there some kind of extended logging capability on the sipXecs you can turn ON so we can get more details as to why he is not liking the SIP?

One thing I noticed is that no DTMF is being negotiated in the INVITE. I wonder if that is causing the grief. Does sipXecs require DTMF to be in the INVITE?

If you have a log for a successful call using Eyebeam, you can email that to us. We can do a comparison.

Another issue appears that sipXecs is also not responding to the ACK we send back. We can look into this after we get a successful INVITE working.

If you can describe your sipXecs setup, we can configure one here and test. I have an Ubuntu and SUSE host ready for testing if needed.


Its getting late in the day at my location. We will do what we can today but this may have to carry over to Monday. We'll get all your call flows working...

By the way, were just about completed with the speex codec work you need.



Thanks,

RJ

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: June 24 2011 at 4:53pm | IP Logged Quote support
Paul,

I did a bit of testing. I have a CentOS install of sipXecs/3.10.2 from some time ago. I set up two soft phones that use the LanScape VOIP Media Engine (LME). One phone is extension 200 and the other is 203.

Both phones register with authentication as expected. Then I place a call from extension 203 to 200 (I used the new Speex codec support we just completed but the calls were ok using other codecs).

The call went through no issue. Once the call was connected through sipXecs, I terminated the call by hanging up extension 203. All works as expected.

Strange – I wonder what’s up. Maybe Monday I can run the same testing against v0.0.4.5.2 that you are using. It should still work ok with your version.

You should enable RFC2833 DTMF for all of your LME phone lines and try your calls again. Something weird is going on. See the InitializeRfc2833DtmfDecoder() and SetRfc2833DtmfDecoderEnableState() API procs in the LanScape docs.

Anyway, here are the SIP logs from my test setup.



Extension 203 registering and making a call to extension 200:


Code:

************* Log Opened (Jun 24 16:37:46) *************

>>>> TxTxTxTxTx (#1, [16:37:57.328] 0 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024bcdf6
From: <sip:203@lslab.com>;tag=24bbe35
To: <sip:203@lslab.com>
Call-ID: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
CSeq: 4944603 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:203@192.168.1.2:5096>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#1, [16:37:57.343] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:203@lslab.com>;tag=24bbe35
To: <sip:203@lslab.com>
Call-Id: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
Cseq: 4944603 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bcdf6
Www-Authenticate: Digest realm="lslab.com", nonce="8dcc3f770d5709ba6b366401a61fc72048d2457d"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:11:41 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#2, [16:37:57.343] 15 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024b761a
From: <sip:203@lslab.com>;tag=24bbe35
To: <sip:203@lslab.com>
Call-ID: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
CSeq: 4944604 REGISTER
Authorization: Digest algorithm=md5,nonce="8dcc3f770d5709ba6b366401a61fc72048d2457d",
 realm="lslab.com",response="57df98763dba4c8e65dbbd1aa8fa132c",uri="sip:lslab.com",username="203"
Expires: 3600
Max-Forwards: 70
Contact: <sip:203@192.168.1.2:5096>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#2, [16:37:57.343] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:203@lslab.com>;tag=24bbe35
To: <sip:203@lslab.com>;tag=2089018456
Call-Id: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
Cseq: 4944604 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024b761a
Contact: <sip:203@192.168.1.2:5096>;EXPIRES=2611
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:11:41 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#3, [16:37:59.250] 1907 Ms, To: 192.168.1.191:5060) >>>>
INVITE sip:200@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024bc759
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>
Contact: <sip:203@192.168.1.2:5096>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-ID: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
CSeq: 4954504 INVITE
Max-Forwards: 70
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 250
User-Agent: LanScape Utility Softphone/5.10.0.11
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=203 38496859 38496859 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8048 RTP/AVP 126 101
a=rtpmap:126 SPEEX/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:126 mode="3,any"
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#3, [16:37:59.250] 1907 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 100 Trying
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
Content-Length: 0



<<<< RxRxRxRxRx (#4, [16:37:59.281] 31 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
User-Agent: LanScape Utility Softphone/5.10.0.11
X-Customheader-Extension-200: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0
Date: Thu, 18 Sep 2008 12:11:43 GMT



<<<< RxRxRxRxRx (#5, [16:38:02.609] 3328 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
Record-Route: <sip:192.168.1.191>
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
Contact: <sip:200@192.168.1.2:5294>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape Utility Softphone/5.10.0.11
X-Customheader-Extension-200: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 259
Content-Type: application/sdp
Date: Thu, 18 Sep 2008 12:11:46 GMT

v=0
o=LanScape 2147483647 2147483647 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8064 RTP/AVP 126 101
a=rtpmap:126 SPEEX/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:126 mode="3,any"
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#4, [16:38:02.609] 3359 Ms, To: 192.168.1.191:5060) >>>>
ACK sip:200@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-ID: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
CSeq: 4954504 ACK
Max-Forwards: 70
Route: <sip:192.168.1.191>,<sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#5, [16:38:16.250] 13641 Ms, To: 192.168.1.191:5060) >>>>
BYE sip:200@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024bd1a7
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-ID: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
CSeq: 4954505 BYE
Max-Forwards: 70
Route: <sip:192.168.1.191>,<sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#6, [16:38:16.265] 13656 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bd1a7
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954505 BYE
User-Agent: LanScape Utility Softphone/5.10.0.11
X-Customheader-Extension-200: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0
Date: Thu, 18 Sep 2008 12:12:00 GMT



>>>> TxTxTxTxTx (#6, [16:38:18.312] 2062 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024bfcf9
From: <sip:203@lslab.com>;tag=24bb4fd
To: <sip:203@lslab.com>
Call-ID: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
CSeq: 4944605 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:203@192.168.1.2:5096>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#7, [16:38:18.312] 2047 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:203@lslab.com>;tag=24bb4fd
To: <sip:203@lslab.com>
Call-Id: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
Cseq: 4944605 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bfcf9
Www-Authenticate: Digest realm="lslab.com", nonce="e9cc745944c6ffe9e7ef7b503966065048d24592"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:12:02 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#7, [16:38:18.312] 0 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5096;rport;branch=z9hG4bK024bcd95
From: <sip:203@lslab.com>;tag=24bb4fd
To: <sip:203@lslab.com>
Call-ID: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
CSeq: 4944606 REGISTER
Authorization: Digest algorithm=md5,nonce="e9cc745944c6ffe9e7ef7b503966065048d24592",
 realm="lslab.com",response="4d06b990bf4d9d807bf3d38d1f7fbf10",uri="sip:lslab.com",username="203"
Expires: 0
Max-Forwards: 70
Contact: <sip:203@192.168.1.2:5096>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-203: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#8, [16:38:18.328] 16 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:203@lslab.com>;tag=24bb4fd
To: <sip:203@lslab.com>;tag=1656478042
Call-Id: 71b28cf0-5675-4cfd-976d-699edfa6e15f-0000204c@192.168.1.2
Cseq: 4944606 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bcd95
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:12:02 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0




************* Log Closed (Jun 24 16:38:28) *************






This log shows extension 200 registering and receiving a call from extension 203:

Code:

************* Log Opened (Jun 24 16:37:47) *************

>>>> TxTxTxTxTx (#1, [16:37:55.828] 0 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK024bb346
From: <sip:200@lslab.com>;tag=24b7fb4
To: <sip:200@lslab.com>
Call-ID: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
CSeq: 4963815 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#1, [16:37:55.843] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@lslab.com>;tag=24b7fb4
To: <sip:200@lslab.com>
Call-Id: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
Cseq: 4963815 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK024bb346
Www-Authenticate: Digest realm="lslab.com", nonce="61d0c350164727e3c5d25948d7eab36248d2457c"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:11:40 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#2, [16:37:55.843] 15 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK024b9c80
From: <sip:200@lslab.com>;tag=24b7fb4
To: <sip:200@lslab.com>
Call-ID: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
CSeq: 4963816 REGISTER
Authorization: Digest algorithm=md5,nonce="61d0c350164727e3c5d25948d7eab36248d2457c",
 realm="lslab.com",response="0ae80f8445df7589657e1a5d1717dba7",uri="sip:lslab.com",username="200"
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#2, [16:37:55.843] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:200@lslab.com>;tag=24b7fb4
To: <sip:200@lslab.com>;tag=1125898167
Call-Id: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
Cseq: 4963816 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK024b9c80
Contact: <sip:200@192.168.1.2:5294>;EXPIRES=1993
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:11:40 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



<<<< RxRxRxRxRx (#3, [16:37:59.265] 3422 Ms, From: 192.168.1.191:5060) <<<<
INVITE sip:200@192.168.1.2:5294 SIP/2.0
Record-Route: <sip:192.168.1.191:5060;lr;sipXecs-rs=%2Afrom%7EMjRiODMxYg%60%60.400_authrules%2Aauth%7E%215e169d506ceef125f8de9eb50db4f767>
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>
Contact: <sip:203@192.168.1.2:5096>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
Max-Forwards: 18
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
X-Customheader-Extension-203: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 250
User-Agent: LanScape Utility Softphone/5.10.0.11
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Date: Thu, 18 Sep 2008 12:11:43 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-00998f797d52560feafc0c09f3cb91d4ae8e
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-0095ce129eab5f89d0d8341c39112b8f4499~365d79ea7c05ada8d09b87ea1158b621
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759

v=0
o=203 38496859 38496859 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8048 RTP/AVP 126 101
a=rtpmap:126 SPEEX/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:126 mode="3,any"
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#3, [16:37:59.281] 3438 Ms, To: 192.168.1.191:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.191:5060;received=192.168.1.191;branch=z9hG4bK-sipXecs-00998f797d52560feafc0c09f3cb91d4ae8e
Via: SIP/2.0/UDP 192.168.1.191:5060;branch=z9hG4bK-sipXecs-0095ce129eab5f89d0d8341c39112b8f4499~365d79ea7c05ada8d09b87ea1158b621
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#4, [16:37:59.281] 0 Ms, To: 192.168.1.191:5060) >>>>
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.191:5060;received=192.168.1.191;branch=z9hG4bK-sipXecs-00998f797d52560feafc0c09f3cb91d4ae8e
Via: SIP/2.0/UDP 192.168.1.191:5060;branch=z9hG4bK-sipXecs-0095ce129eab5f89d0d8341c39112b8f4499~365d79ea7c05ada8d09b87ea1158b621
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 INVITE
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#5, [16:38:02.593] 3312 Ms, To: 192.168.1.191:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.191:5060;received=192.168.1.191;branch=z9hG4bK-sipXecs-00998f797d52560feafc0c09f3cb91d4ae8e
Via: SIP/2.0/UDP 192.168.1.191:5060;branch=z9hG4bK-sipXecs-0095ce129eab5f89d0d8341c39112b8f4499~365d79ea7c05ada8d09b87ea1158b621
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
Record-Route: <sip:192.168.1.191>
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-ID: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
CSeq: 4954504 INVITE
Contact: <sip:200@192.168.1.2:5294>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 259
Content-Type: application/sdp

v=0
o=LanScape 2147483647 2147483647 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8064 RTP/AVP 126 101
a=rtpmap:126 SPEEX/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendrecv
a=fmtp:126 mode="3,any"
a=ptime:20
a=fmtp:101 0-16


<<<< RxRxRxRxRx (#4, [16:38:02.609] 3344 Ms, From: 192.168.1.191:5060) <<<<
ACK sip:200@192.168.1.2:5294 SIP/2.0
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954504 ACK
Max-Forwards: 20
User-Agent: LanScape Utility Softphone/5.10.0.11
X-Customheader-Extension-203: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0
Date: Thu, 18 Sep 2008 12:11:46 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-009b799eb38ab735c3b602a4b3f6674c680b
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bc759
Route: <sip:200@lslab.com>



<<<< RxRxRxRxRx (#5, [16:38:16.250] 13641 Ms, From: 192.168.1.191:5060) <<<<
BYE sip:200@192.168.1.2:5294 SIP/2.0
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-Id: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
Cseq: 4954505 BYE
Max-Forwards: 20
User-Agent: LanScape Utility Softphone/5.10.0.11
X-Customheader-Extension-203: "Modified transmitted SIP message."
X-Phoneline: 0
X-Voip-Sdk: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0
Date: Thu, 18 Sep 2008 12:12:00 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-009e50b6b9018a9462eec9182b23f674a518
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bd1a7
Route: <sip:200@lslab.com>



>>>> TxTxTxTxTx (#6, [16:38:16.250] 13657 Ms, To: 192.168.1.191:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.191:5060;received=192.168.1.191;branch=z9hG4bK-sipXecs-009e50b6b9018a9462eec9182b23f674a518
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK024bd1a7
From: "Extension 203" <sip:203@lslab.com>;tag=24b831b;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:200@lslab.com>;tag=24b833a
Call-ID: 8612a674-7723-431c-ad12-1a43e6b7cf32-0000204c@192.168.1.2
CSeq: 4954505 BYE
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



>>>> TxTxTxTxTx (#7, [16:38:19.812] 3562 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK024c02d3
From: <sip:200@lslab.com>;tag=24bbad9
To: <sip:200@lslab.com>
Call-ID: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
CSeq: 4963817 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#6, [16:38:19.812] 3562 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@lslab.com>;tag=24bbad9
To: <sip:200@lslab.com>
Call-Id: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
Cseq: 4963817 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK024c02d3
Www-Authenticate: Digest realm="lslab.com", nonce="aa82d7046c623d2ccb0cfe036170253448d24593"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:12:03 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#8, [16:38:19.812] 0 Ms, To: 192.168.1.191:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK024bd36f
From: <sip:200@lslab.com>;tag=24bbad9
To: <sip:200@lslab.com>
Call-ID: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
CSeq: 4963818 REGISTER
Authorization: Digest algorithm=md5,nonce="aa82d7046c623d2ccb0cfe036170253448d24593",
 realm="lslab.com",response="9a23ce071e607c6a14954b56a310154f",uri="sip:lslab.com",username="200"
Expires: 0
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>
User-Agent: LanScape Utility Softphone/5.10.0.11
x-CustomHeader-Extension-200: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0



<<<< RxRxRxRxRx (#7, [16:38:19.812] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:200@lslab.com>;tag=24bbad9
To: <sip:200@lslab.com>;tag=1131176229
Call-Id: 0f49dfcf-afcd-4ebb-9d89-3da3406be60c-00002ce4@192.168.1.2
Cseq: 4963818 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK024bd36f
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 18 Sep 2008 12:12:03 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0




************* Log Closed (Jun 24 16:38:25) *************






We can continue this on Monday. Post any new information you have in the meantime.

Have a good weekend.


RJ

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


Joined: June 24 2011
Location: Philippines
Posts: 9
Posted: June 27 2011 at 8:04am | IP Logged Quote PaulR
Hi RJ,

Thanks for a quick response last friday, very much appreciated.Hope we resolve the issue today.
Going back to my problem, my hunch why the invite is failing is because of the via header. Lanscape used different IP in Via header when trying to register again.

Lanscape
Code:

1. --> REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:5060;rport;branch=z9hG4bK2488f00f

2. <-- SIP/2.0 401 Unauthorized

3. --> REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 234.124.15.13:22617;rport;branch=z9hG4bK2489294d

4. <--SIP/2.0 200 OK

5. -->INVITE sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:22617;rport;branch=z9hG4bK24895c12

6. <--SIP/2.0 403 Forbidden


As you can see, the IP in Via header of the 1st registration is 10.107.25.202, and Sip/acd response it with an Unauthorized. Lanscape try to register again
but using differrent Ip in Via Header which is 234.124.15.13, and then Sip/acd response it with an OK. Then when I try the Invite, Lanscape uses the IP 10.107.25.202 in via header

Comparing to Eyebeam, it uses the same IP when try to register again.

EyeBeam
Code:

1. -->REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202 :10104;branch=z9hG4bK-d87543-dc7a966e9108dc3f-1--d87543-;rpo rt

2. <-- SIP/2.0 401 Unauthorized

3. --> REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202 :10104;branch=z9hG4bK-d87543-7c29fe4cc6322f5b-1--d87543-;rpo rt

4. <--SIP/2.0 200 OK

5. --> INVITE sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:10104;branch=z9hG4bK-d87543-937aef3ff554147d-1--d87543-;rport

5. <--SIP/2.0 200 OK


What do you think? is there something I missed to enable/configure in Lanscape

Here's the complete log for Eyebeam
Code:

SENDING TO: 200.222.129.15:5060
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202 :10104;branch=z9hG4bK-d87543-dc7a966e9108dc3f-1--d87543-;rpo rt
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:10104>
To: "4108"<sip:4108@ca1acd04.infonxx.local>
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=553e2918
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Supported: eventlist
User-Agent: eyeBeam release 3010n stamp 19039
Content-Length: 0


19:55:09.4 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-dc7a966e9108dc3f-1--d87543-
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=553e2918
To: "4108" <sip:4108@ca1acd04.infonxx.local>
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 REGISTER
Content-Length: 0


19:55:09.5 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-dc7a966e9108dc3f-1--d87543-
WWW-Authenticate: Digest realm="infonxx.local",nonce="34f751fed63330f913b2d111c0ac920d4e086f7f",qop="auth"
To: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=3518167910-56805
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=553e2918
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@10.107.25.202:10104>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0


19:55:10.0 
SENDING TO: 200.222.129.15:5060
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202 :10104;branch=z9hG4bK-d87543-7c29fe4cc6322f5b-1--d87543-;rpo rt
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:10104>
To: "4108"<sip:4108@ca1acd04.infonxx.local>
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=553e2918
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Supported: eventlist
User-Agent: eyeBeam release 3010n stamp 19039
Authorization: Digest username="4108",realm="infonxx.local",nonce="34f751fed63330f913b2d111c0ac920d4e086f7f",
 uri="sip:ca1acd04.infonxx.local",response="e6e44dd233f12a5e2e767c7d24929b06",cnonce="7629fb3579060c7a",
 nc=00000001,qop=auth,algorithm=MD5
Content-Length: 0


19:55:10.3 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-7c29fe4cc6322f5b-1--d87543-
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=553e2918
To: "4108" <sip:4108@ca1acd04.infonxx.local>
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 REGISTER
Content-Length: 0


19:55:10.4 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-7c29fe4cc6322f5b-1--d87543-
To: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=3518167910-56805
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=553e2918
Call-ID: 7675bc336025687d@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@10.107.25.202:10104>
Expires: 179
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0


19:56:09.0 
SENDING TO: 200.222.129.15:5060
INVITE sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:10104;branch=z9hG4bK-d87543-937aef3ff554147d-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:10104>
To: <sip:*88@ca1acd04.infonxx.local>
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Supported: eventlist
User-Agent: eyeBeam release 3010n stamp 19039
Content-Length: 307

v=0
o=- 1032825822 1032825882 IN IP4 10.107.25.202
s=eyeBeam
c=IN IP4 10.107.25.202
t=0 0
m=audio 10106 RTP/AVP 100 6 0 8 3 18 97 5 101
a=alt:1 1 : 1E9703FE 0000007D 10.107.25.202 10106
a=fmtp:101 0-15
a=rtpmap:100 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

19:56:09.3 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-937aef3ff554147d-1--d87543-
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=d301b411
To: <sip:*88@ca1acd04.infonxx.local>
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 INVITE
Content-Length: 0


19:56:09.4 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-937aef3ff554147d-1--d87543-
Proxy-Authenticate: Digest realm="infonxx.local",nonce="09f575b5d1cedc4a4e22a44a870beb584e086fba",qop="auth"
To: <sip:*88@ca1acd04.infonxx.local>;tag=3518167969-938867
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 INVITE
Contact: <sip:*88@200.222.129.15:5060>
Call-Info: <sip:200.222.129.15>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0


19:56:09.4 
SENDING TO: 200.222.129.15:5060
ACK sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:10104;branch=z9hG4bK-d87543-937aef3ff554147d-1--d87543-;rport
To: <sip:*88@ca1acd04.infonxx.local>;tag=3518167969-938867
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 1 ACK
Content-Length: 0


19:56:09.5 
SENDING TO: 200.222.129.15:5060
INVITE sip:*88@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:10104;branch=z9hG4bK-d87543-d53a0f2a0c1e224b-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:10104>
To: <sip:*88@ca1acd04.infonxx.local>
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Content-Type: application/sdp
Proxy-Authorization: Digest username="4108",realm="infonxx.local",
 nonce="09f575b5d1cedc4a4e22a44a870beb584e086fba",uri="sip:*88@ca1acd04.infonxx.local",
 response="886ac7cbd12d762aedf6d7ba0741f801",cnonce="2cc906b9ef0cc82e",nc=00000001,qop=auth,algorithm=MD5
Supported: eventlist
User-Agent: eyeBeam release 3010n stamp 19039
Content-Length: 307

v=0
o=- 1032825822 1032825882 IN IP4 10.107.25.202
s=eyeBeam
c=IN IP4 10.107.25.202
t=0 0
m=audio 10106 RTP/AVP 100 6 0 8 3 18 97 5 101
a=alt:1 1 : 1E9703FE 0000007D 10.107.25.202 10106
a=fmtp:101 0-15
a=rtpmap:100 speex/16000
a=rtpmap:97 speex/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

19:56:09.7 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-d53a0f2a0c1e224b-1--d87543-
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=d301b411
To: <sip:*88@ca1acd04.infonxx.local>
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 INVITE
Content-Length: 0


19:56:09.9 
RECEIVING FROM: 200.222.129.15:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.107.25.202:10104;rport=38955;received=234.124.15.13;branch=z9hG4bK-d87543-d53a0f2a0c1e224b-1--d87543-
To: <sip:*88@ca1acd04.infonxx.local>;tag=3518167970-411066
From: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Remote-Party-Id: "*88" <sip:*88@10.112.75.14>;privacy=off;screen=no
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 INVITE
Allow: NOTIFY
Allow: REFER
Allow: REGISTER
Allow: INFO
Allow: UPDATE
Allow: MESSAGE
Allow: OPTIONS
Allow: CANCEL
Allow: BYE
Allow: ACK
Allow: INVITE
Contact: <sip:*88@200.222.129.15:5060>
Call-Info: <sip:200.222.129.15>;method="NOTIFY;Event=telephone-event;Duration=1000"
Allow-Events: refer
Allow-Events: hold
Allow-Events: talk
Content-Type: application/sdp
Content-Length: 250

v=0
o=PA0NXTSBC01 1309162883 1309162884 IN IP4 200.222.129.15
s=sip call
c=IN IP4 209.92.129.105
t=0 0
m=audio 17778 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20

19:56:10.0 
SENDING TO: 200.222.129.15:5060
ACK sip:*88@200.222.129.15:5060 SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:10104;branch=z9hG4bK-d87543-0868361bf56b4f20-1--d87543-;rport
Max-Forwards: 70
Contact: <sip:4108@10.107.25.202:10104>
To: <sip:*88@ca1acd04.infonxx.local>;tag=3518167970-411066
From: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=d301b411
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 ACK
User-Agent: eyeBeam release 3010n stamp 19039
Content-Length: 0


19:56:11.9 
RECEIVING FROM: 200.222.129.15:5060
BYE sip:4108@10.107.25.202:10104;x-sipx-nonat SIP/2.0
Max-Forwards: 19
To: "4108" <sip:4108@ca1acd04.infonxx.local>;tag=d301b411
From: <sip:*88@ca1acd04.infonxx.local>;tag=3518167970-411066
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 BYE
Allow: NOTIFY
Allow: REFER
Allow: REGISTER
Allow: INFO
Allow: UPDATE
Allow: MESSAGE
Allow: OPTIONS
Allow: CANCEL
Allow: BYE
Allow: ACK
Allow: INVITE
Via: SIP/2.0/UDP 200.222.129.15:5060;branch=z9hG4bK02090dc5aab7c5b1c2e9350be9ad347e
Contact: <sip:*88@200.222.129.15:5060>
Reason: Q.850;cause=16;text="NORMAL_CLEARING"
Content-Length: 0


19:56:11.9 Call (l:'4108' r:'sip:*88@ca1acd04.infonxx.local') - Call being terminated. Reasons: "BYE", (code: 0)

19:56:12.0 
SENDING TO: 200.222.129.15:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 200.222.129.15:5060;branch=z9hG4bK02090dc5aab7c5b1c2e9350be9ad347e
Contact: <sip:4108@10.107.25.202:10104>
To: "4108"<sip:4108@ca1acd04.infonxx.local>;tag=d301b411
From: <sip:*88@ca1acd04.infonxx.local>;tag=3518167970-411066
Call-ID: 780383170b5bf95a@cGgwYWRtbHQyNzAwLmluZm9ueHgubG9jYWw.
CSeq: 2 BYE
User-Agent: eyeBeam release 3010n stamp 19039
Content-Length: 0




Thanks,
Paul

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 27 2011 at 10:04am | IP Logged Quote support
Paul,

You could be right.

In your code, call the UseRportInViaHeader() API proc and disable rport use. Retry your calls again and see what occurs.

Also, if you suspect some interop issue with the SIP, you can change/alter any of the received or transmitted SIP messages using the SipModifySipMessage immediate event and the ModifySipMessage() API proc.


RJ

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


Joined: June 24 2011
Location: Philippines
Posts: 9
Posted: June 27 2011 at 12:00pm | IP Logged Quote PaulR
I tried UseRportInViaHeader() but no success, it failed upon registration.
error: SipRegisterTimeOut

any other config that I can try?
For the meantime,I'll try ModifySipMessage() API and will let you know.

Here's the log using UseRportInViaHeader(false)
Code:


************* Log Opened (Jun 28 00:53:21) *************
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [00:53:21.689] 0 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 10.107.25.202:5060
From: <sip:4107@ca1acd04.infonxx.local>;tag=3ea0628a
To: <sip:4107@ca1acd04.infonxx.local>
Call-ID: de897620-696b-40b7-b0be-f58a008c00d5-00000608@10.107.25.202
CSeq: 10494793 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:4107@10.107.25.202:5060>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [00:53:21.939] 0 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.107.25.202:5060;received=234.124.15.13
From: <sip:4107@ca1acd04.infonxx.local>;tag=3ea0628a
To: <sip:4107@ca1acd04.infonxx.local>
Call-ID: de897620-696b-40b7-b0be-f58a008c00d5-00000608@10.107.25.202
CSeq: 10494793 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [00:53:22.064] 125 Ms, From: 200.222.129.15:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.107.25.202:5060;received=234.124.15.13
WWW-Authenticate: Digest realm="infonxx.local",nonce="2b04c00695f3628b86920e13170c6eaf4e08b560",qop="auth"
To: <sip:4107@ca1acd04.infonxx.local>;tag=3518185802-429205
From: <sip:4107@ca1acd04.infonxx.local>;tag=3ea0628a
Call-ID: de897620-696b-40b7-b0be-f58a008c00d5-00000608@10.107.25.202
CSeq: 10494793 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4107@10.107.25.202:5060>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [00:53:22.064] 375 Ms, To: 200.222.129.15:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 234.124.15.13:5060
From: <sip:4107@ca1acd04.infonxx.local>;tag=3ea0628a
To: <sip:4107@ca1acd04.infonxx.local>
Call-ID: de897620-696b-40b7-b0be-f58a008c00d5-00000608@10.107.25.202
CSeq: 10494794 REGISTER
Authorization: Digest algorithm=md5,cnonce="00a016df",nc=00000001,
 nonce="2b04c00695f3628b86920e13170c6eaf4e08b560",qop=auth,realm="infonxx.local",
 response="64988217fd81cd0cd3e78585702d7f62",uri="sip:ca1acd04.infonxx.local",username="4107"
Expires: 3600
Max-Forwards: 70
Contact: <sip:4107@234.124.15.13:5060>
User-Agent: IDEA Application using Lanscape Media/v1.2.3.4 (www.LanScapeCorp.com)
x-VOIP-SDK: LanScape VOIP Media Engine/6.0.0.17 (www.LanScapeCorp.com)
Content-Length: 0




************* Log Closed (Jun 28 00:53:26) *************



Thanks,
Paul
Back to Top View PaulR's Profile Search for other posts by PaulR
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 27 2011 at 12:38pm | IP Logged Quote support
Paul,

Could I get access to the server. I can perform some testing from here.

What would be good is to allow me to register two extension, generate a few calls between them and test.

If you want, email the info I need.


RJ

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: June 28 2011 at 10:12am | IP Logged Quote support
Paul,

I will be testing using the server shortly. Will post back when I have further info.

RJ
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: June 28 2011 at 10:25am | IP Logged Quote support
Paul,

If you can, email the authentication passwords to me for the two test extensions.

I'm being challenged.... :)

RJ

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: June 28 2011 at 11:24am | IP Logged Quote support
Paul,

OK, we must have a config issue or something really simple to overcome at your end.

I set up two extensions at my location. I am behind a NAT router. I use an LS "utility" soft phone that we use for test, etc. The soft phone uses the media enigne.

I registered OK. From extension 4108, i called ext 4109. Looks OK. Here is the log:

(IP addresses have been changed)
Code:


************* Log Opened (Jun 28 11:03:20) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#1, [11:03:20.296] 0 Ms, To: 109.192.129.14:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK00428564
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369709 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:4108@192.168.1.2:5260>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#1, [11:03:20.343] 0 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00428564
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369709 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#2, [11:03:20.468] 125 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00428564
WWW-Authenticate: Digest realm="infonxx.local",nonce="6db0bccd5554e2bc1024e35856ac68464e09fb25",qop="auth"
To: <sip:4108@ca1acd04.infonxx.local>;tag=3518269213-682917
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369709 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@192.168.1.2:5260>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#2, [11:03:20.468] 172 Ms, To: 109.192.129.14:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK0042a66b
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369710 REGISTER
Authorization: Digest algorithm=md5,cnonce="0042755b",nc=00000001,
 nonce="6db0bccd5554e2bc1024e35856ac68464e09fb25",qop=auth,realm="infonxx.local",
 response="fcc5992fad0d10e527b4ea37e8f62ad8",uri="sip:ca1acd04.infonxx.local",username="4108"
Expires: 3600
Max-Forwards: 70
Contact: <sip:4108@192.168.1.2:5260>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#3, [11:03:20.515] 47 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0042a66b
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369710 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#4, [11:03:20.640] 125 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0042a66b
To: <sip:4108@ca1acd04.infonxx.local>;tag=3518269213-682917
From: <sip:4108@ca1acd04.infonxx.local>;tag=42cf99
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369710 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@192.168.1.2:5260>
Expires: 179
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#3, [11:03:44.546] 24078 Ms, To: 109.192.129.14:5060) >>>>
INVITE sip:4109@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK00430b30
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:4109@ca1acd04.infonxx.local>
Contact: <sip:4108@192.168.1.2:5260>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382766 INVITE
Max-Forwards: 70
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 219
User-Agent: LanScape Utility Softphone/5.11.0.2
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=4108 4378125 4378125 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8938 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 (#5, [11:03:44.593] 23953 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00430b30
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:4109@ca1acd04.infonxx.local>
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382766 INVITE
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#6, [11:03:44.718] 125 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00430b30
Proxy-Authenticate: Digest realm="infonxx.local",nonce="b7987d50da705c8de5233567cb755f004e09fb3d",qop="auth"
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269237-943192
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382766 INVITE
Contact: <sip:4109@109.192.129.14:5060>
Call-Info: <sip:109.192.129.14>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#4, [11:03:44.718] 172 Ms, To: 109.192.129.14:5060) >>>>
ACK sip:4109@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;received=175.73.198.149;rport=5260;branch=z9hG4bK00430b30
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269237-943192
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382766 ACK
Max-Forwards: 70
Route: <sip:4109@109.192.129.14>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#5, [11:03:44.734] 16 Ms, To: 109.192.129.14:5060) >>>>
INVITE sip:4109@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK00430bec
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:4109@ca1acd04.infonxx.local>
Contact: <sip:4108@192.168.1.2:5260>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382970 INVITE
Max-Forwards: 70
Organization: 44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Proxy-Authorization: Digest algorithm=md5,cnonce="0042ecb9",nc=00000001,
 nonce="b7987d50da705c8de5233567cb755f004e09fb3d",qop=auth,realm="infonxx.local",
 response="24726148a0959caadd7d942520cf1893",uri="sip:4109@ca1acd04.infonxx.local",username="4108"
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 219
User-Agent: LanScape Utility Softphone/5.11.0.2
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=4108 4378312 4378312 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8938 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 (#7, [11:03:44.781] 63 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00430bec
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:4109@ca1acd04.infonxx.local>
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382970 INVITE
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#8, [11:03:45.218] 437 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00430bec
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269238-446309
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382970 INVITE
Contact: <sip:4109@109.192.129.14:5060>
Call-Info: <sip:109.192.129.14>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#9, [11:03:50.375] 5157 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00430bec
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269238-446309
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382970 INVITE
Allow: INVITE
Allow: ACK
Allow: OPTIONS
Allow: BYE
Allow: CANCEL
Allow: SUBSCRIBE
Allow: NOTIFY
Contact: <sip:4109@109.192.129.14:5060>
Call-Info: <sip:109.192.129.14>;method="NOTIFY;Event=telephone-event;Duration=1000"
Content-Type: application/sdp
Content-Length: 235

v=0
o=PA0NXTSBC01 2147483647 2147483647 IN IP4 109.192.129.14
s=sip call
c=IN IP4 192.168.1.2
t=0 0
m=audio 9424 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



>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#6, [11:03:50.375] 5641 Ms, To: 109.192.129.14:5060) >>>>
ACK sip:4109@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;received=175.73.198.149;rport=5260;branch=z9hG4bK00430bec
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269238-446309
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382970 ACK
Max-Forwards: 70
Route: <sip:4109@109.192.129.14>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#7, [11:04:14.562] 24187 Ms, To: 109.192.129.14:5060) >>>>
BYE sip:4109@ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK00436ad0
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269238-446309
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382971 BYE
Max-Forwards: 70
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-PhoneLine: 0
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#10, [11:04:14.890] 24515 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK00436ad0
To: <sip:4109@ca1acd04.infonxx.local>;tag=3518269238-446309
From: "ext 4108" <sip:4108@ca1acd04.infonxx.local>;tag=42e6cd
Call-ID: 79649385-c847-4cfe-9676-ab662018c00d-00000d90@192.168.1.2
CSeq: 4382971 BYE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4109@109.192.129.14:5060>
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#8, [11:04:25.968] 11406 Ms, To: 109.192.129.14:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK0043b813
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369711 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:4108@192.168.1.2:5260>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#11, [11:04:26.031] 11141 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0043b813
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369711 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#12, [11:04:26.140] 109 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0043b813
WWW-Authenticate: Digest realm="infonxx.local",nonce="06081e4bd3e9a35b3d70eca4921305714e09fb66",qop="auth"
To: <sip:4108@ca1acd04.infonxx.local>;tag=3518269279-362297
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369711 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Contact: <sip:4108@192.168.1.2:5260>
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0




>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (#9, [11:04:26.140] 172 Ms, To: 109.192.129.14:5060) >>>>
REGISTER sip:ca1acd04.infonxx.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5260;rport;branch=z9hG4bK0043895b
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369712 REGISTER
Authorization: Digest algorithm=md5,cnonce="0043d821",nc=00000001,
 nonce="06081e4bd3e9a35b3d70eca4921305714e09fb66",qop=auth,realm="infonxx.local",
 response="e3f68181b4991e3fc16dffe5efc96900",uri="sip:ca1acd04.infonxx.local",username="4108"
Expires: 0
Max-Forwards: 70
Contact: <sip:4108@192.168.1.2:5260>
User-Agent: LanScape Utility Softphone/5.11.0.2
x-CustomHeader-Extension-4108: "Modified transmitted SIP message."
x-VOIP-SDK: LanScape VOIP Media Engine(Windows)/6.0.1.18 (www.LanScapeCorp.com)
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#13, [11:04:26.203] 63 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0043895b
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
To: <sip:4108@ca1acd04.infonxx.local>
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369712 REGISTER
Content-Length: 0




<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (#14, [11:04:26.312] 109 Ms, From: 109.192.129.14:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5260;rport=5260;received=175.73.198.149;branch=z9hG4bK0043895b
To: <sip:4108@ca1acd04.infonxx.local>;tag=3518269279-362297
From: <sip:4108@ca1acd04.infonxx.local>;tag=437016
Call-ID: 483ad554-7b62-4bd6-a7d9-015c15ae1668-00000d90@192.168.1.2
CSeq: 4369712 REGISTER
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Expires: 0
User-Agent: sipXecs/0.0.4.5.2 sipXecs/registry (Linux)
Content-Length: 0

************* Log Closed (Jun 28 11:04:26) *************




Maybe you can spot the difference in this log and the one you previously posted.

In the media engine, the soft phone specified the following settings:

Domain: ca1acd04.infonxx.local
Use registration server: The IP:port you gave me.
SIP proxy: The IP:port you gave me.
Authentication info: As you specified

The call was made by the phone using MakeCalUri() API proc using this call destination:

sip:4109@ca1acd04.infonxx.local:5060


I will look over the SIP logs for my call and your call and see what differences I can spot.

Strange.

Post back if you figure it out in the mantime.


RJ


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


Joined: June 24 2011
Location: Philippines
Posts: 9
Posted: June 28 2011 at 11:57am | IP Logged Quote PaulR
Hi RJ,

Looks like we have something here.. If you able to make it work then, I think I just missed something.

Things I noticed:
1. Version - I'm using the version 6.0.0.17, WHILE you used the version 6.0.1.18. - Is there any major changes between the 2 versions?

2.Via header(2nd registration) - In your testing, the IP in VIA header on your 2nd Registration is the same with the first Registration, WHILE in my testing, its different(hmmm looks like this is really my issue). Would you know why Lanscape used different IP when retrying to register again?

Would it be okay if you can forward to me the tool that you've used in your testing so i can try it here? If you can forward to as well the screenshot of configuration you've set, much better.

Thanks
Paul
Back to Top View PaulR's Profile Search for other posts by PaulR
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 28 2011 at 12:42pm | IP Logged Quote support
Paul,

1.
I will send you the version info for 6.0.0.18 via email. Chris in Texas has this new image. You can get it from him if you want to test using it. There are differences but nothing that would affect the basic SIP interoperability.

2.
Do you have SetWanIpAddress() API enabled? Maybe turn this OFF. I need to look at the code to see if this is causing the IP change. I will keep looking myself this afternoon. I am in and out this afternoon but I am sure we will figure this out soon.

3.
I will email you Vphone.exe test app. You will need to get the v6.0.0.18 LME from Chris to use this. Note: This is not a piece of polished software – simply used for test. It will come with an INI file that configures the phone to extension 4108.


RJ


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


Joined: June 24 2011
Location: Philippines
Posts: 9
Posted: June 28 2011 at 4:51pm | IP Logged Quote PaulR
Hi RJ,

Finally, I was able to make it work. The reason why it changed the IP address of the 2nd REGISTER is because of, the parameter RegisterNatAutoDetectEnabled under the method EnableSipRegisterServer, It was set to true. When I changed it to False, viola!!! It works :)

My reference code when coding LanScape is the "MultiLine Phone" application under "VOIP Media Engine\Release 6\Software Examples". The application does not have a settings in UI to change the value of RegisterNatAutoDetectEnabled(so I assume it always true) Unlike in Vphone , it has a setting of "Register NAT Detection".

Thank you very much with your help and support.Much appreciated.! :) thumbs up!

Paul



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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: June 29 2011 at 11:17am | IP Logged Quote support
Great job!

Thanks

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