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

LanScape VOIP Media Engine™ - Pre-Sales Technical Support
 LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Subject Topic: Registration issue with sipXecs Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
peter.conklin
Intermediate
Intermediate


Joined: May 01 2008
Location: Australia
Posts: 9
Posted: September 12 2008 at 6:47am | IP Logged Quote peter.conklin
Hi,

I am trying to register using the Lanscape single line test application with sipXecs registrar. When I attempt to register with the Lanscape demo I get 401 Unauthorized erros. However if I use X-Lite with the same details it can register fine. Has Lanscape been tested with sipXecs or known to work with it?

I have logs of both the X-Lite and Lanscape demo but they may be too large to post here. Is there anyway I can email or FTP the logs?

Below is an excerpt of the Lanscape logs:

Code:

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#1, 9929218 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:veridian.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:48578;rport;branch=z9hG4bK0097f2e4
From: <sip:200@veridian.local:48578>;tag=97c58f
To: <sip:200@veridian.local:48578>
Call-Id: d431e896-5184-4c0a-a198-3543f3feee1a-0000145c@192.168.1.20
CSeq: 9931864 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.20:48578>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1  (www.LanScapeCorp.com - This is a trial version not for general deployment)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#1, 9929250 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@veridian.local:48578>;tag=97c58f
To: <sip:200@veridian.local:48578>
Call-Id: d431e896-5184-4c0a-a198-3543f3feee1a-0000145c@192.168.1.20
Cseq: 9931864 REGISTER
Via: SIP/2.0/UDP 192.168.1.20:48578;rport=48578;branch=z9hG4bK0097f2e4
Www-Authenticate: Digest realm="sip.local", nonce="0b3bf60e40c12e6787be440b6f2d7ca048c99ddd"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Thu, 11 Sep 2008 22:38:21 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



Regards


Back to Top View peter.conklin's Profile Search for other posts by peter.conklin
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 12 2008 at 8:23am | IP Logged Quote support
Hi Peter,

Thanks for posting.

If we need to exchange large files, then we can get you set up with a support FTP account. We can do this later.

We have to test the VOIP Media Engine against so many SIP servers and devices…. its hard to keep up.

The last version of the soft PBX we tested against was:

sipX PBX v3.7.5-8790

…running on Fedora Core 5.

Granted, at this time this is not the latest release, but we would think that something as simple as registrations would not be broke.

Here is a SIP log of some test we quickly performed this morning after reading your post. Look through the log for our comments in RED.

Notes:

1)
We have SipX configured in our lab at 192.168.1.121.

2)
We used two VOIP Media Engine based soft phones. One is configured as extension 200 and the other as 203.

3)
The SIP log below is the log for soft phone 200.


Code:


************* Log Opened (Sep 12 07:53:16) *************

Extension 200 tries to register…

>>>> TxTxTxTxTx (#1, [07:53:19.421] 0 Ms, To: 192.168.1.121:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport;branch=z9hG4bK006d2000
From: <sip:200@lslab.com>;tag=6d2374
To: <sip:200@lslab.com>
Call-Id: 13123b2f-7370-4fef-aaca-01bb597a8565-000001a4@192.168.1.2
CSeq: 7156335 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5094>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#1, [07:53:19.421] 0 Ms, From: 192.168.1.121:32773) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@lslab.com>;tag=6d2374
To: <sip:200@lslab.com>
Call-Id: 13123b2f-7370-4fef-aaca-01bb597a8565-000001a4@192.168.1.2
Cseq: 7156335 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d2000
Www-Authenticate: Digest realm="lslab.com", nonce="f75daeeb4d47e0da57ceb2b5f107b8ec1206421324"
User-Agent: sipX/3.7.0 sipX/registry (Linux)
Date: Tue, 25 Mar 2008 05:02:04 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#2, [07:53:19.437] 16 Ms, To: 192.168.1.121:5060) >>>>
REGISTER sip:lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport;branch=z9hG4bK006cf62c
From: <sip:200@lslab.com>;tag=6d3b80
To: <sip:200@lslab.com>
Call-Id: 13123b2f-7370-4fef-aaca-01bb597a8565-000001a4@192.168.1.2
CSeq: 7156336 REGISTER
Authorization: Digest algorithm=md5,nonce="f75daeeb4d47e0da57ceb2b5f107b8ec1206421324",
 realm="lslab.com",response="c3a55e392a7482fea8042db94713966b",uri="sip:lslab.com",username="200"
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5094>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#2, [07:53:19.437] 16 Ms, From: 192.168.1.121:32773) <<<<
SIP/2.0 200 OK
From: <sip:200@lslab.com>;tag=6d3b80
To: <sip:200@lslab.com>;tag=1365180540
Call-Id: 13123b2f-7370-4fef-aaca-01bb597a8565-000001a4@192.168.1.2
Cseq: 7156336 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006cf62c
Contact: <sip:200@192.168.1.2:5094>;EXPIRES=1026
User-Agent: sipX/3.7.0 sipX/registry (Linux)
Date: Tue, 25 Mar 2008 05:02:04 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0

Extension 200 is now registered…


Extension 200 now calls extension 203…

>>>> TxTxTxTxTx (#3, [07:53:21.765] 2328 Ms, To: 192.168.1.121:5060) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport;branch=z9hG4bK006d4332
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>
Contact: <sip:200@192.168.1.2:5094>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157116 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 218
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 7138359 7138359 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8704 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



<<<< RxRxRxRxRx (#3, [07:53:21.765] 2328 Ms, From: 192.168.1.121:32773) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157116 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d4332
Content-Length: 0



<<<< RxRxRxRxRx (#4, [07:53:21.781] 16 Ms, From: 192.168.1.121:32773) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d4332
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157116 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.8.12 (www.LanScapeCorp.com)
Content-Length: 2
Date: Tue, 25 Mar 2008 05:02:06 GMT




<<<< RxRxRxRxRx (#5, [07:53:23.453] 1672 Ms, From: 192.168.1.121:32773) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d4332
Record-Route: <sip:192.168.1.121:5080>
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157116 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Tue, 25 Mar 2008 05:02:08 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 8356 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


>>>> TxTxTxTxTx (#4, [07:53:23.453] 1688 Ms, To: 192.168.1.121:5060) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d4332
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157116 ACK
Max-Forwards: 70
Route: <sip:192.168.1.121:5080>,<sip:203@192.168.1.2:5096>
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0

Extension 200 and 203 are now in a call…


Extension 200 places the call on hold…

>>>> TxTxTxTxTx (#5, [07:53:27.031] 3578 Ms, To: 192.168.1.121:5080) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport;branch=z9hG4bK006d1994
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Contact: <sip:200@192.168.1.2:5094>
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157117 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Route: <sip:192.168.1.121:5080>,<sip:203@192.168.1.2:5096>
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 214
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 7143625 7143625 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8704 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#6, [07:53:27.031] 3578 Ms, From: 192.168.1.121:32783) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157117 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d1994
Content-Length: 0



<<<< RxRxRxRxRx (#7, [07:53:27.046] 15 Ms, From: 192.168.1.121:32783) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d1994
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157117 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Tue, 25 Mar 2008 05:02:11 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 8356 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#6, [07:53:27.078] 47 Ms, To: 192.168.1.121:5080) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d1994
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157117 ACK
Max-Forwards: 70
Route: <sip:203@192.168.1.2:5096>
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0

Extension 200 removes the call from hold…

>>>> TxTxTxTxTx (#7, [07:53:32.078] 5000 Ms, To: 192.168.1.121:5080) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport;branch=z9hG4bK006d6bc9
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Contact: <sip:200@192.168.1.2:5094>
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157118 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Route: <sip:192.168.1.121:5080>,<sip:203@192.168.1.2:5096>
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 218
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 7148671 7148671 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8704 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



<<<< RxRxRxRxRx (#8, [07:53:32.078] 5032 Ms, From: 192.168.1.121:32783) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157118 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d6bc9
Content-Length: 0



<<<< RxRxRxRxRx (#9, [07:53:32.078] 0 Ms, From: 192.168.1.121:32783) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d6bc9
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157118 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Tue, 25 Mar 2008 05:02:16 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 8356 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


>>>> TxTxTxTxTx (#8, [07:53:32.109] 31 Ms, To: 192.168.1.121:5080) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5094;rport=5094;branch=z9hG4bK006d6bc9
From: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=6d307f
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157118 ACK
Max-Forwards: 70
Route: <sip:203@192.168.1.2:5096>
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0


Now extension 203 places the call on hold…

<<<< RxRxRxRxRx (#10, [07:53:37.859] 5781 Ms, From: 192.168.1.121:32783) <<<<
INVITE sip:200@192.168.1.2:5094 SIP/2.0
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Contact: <sip:203@192.168.1.2:5096>
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157117 INVITE
Max-Forwards: 20
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 219
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
Content-Type: application/sdp
Date: Tue, 25 Mar 2008 05:02:22 GMT
Via: SIP/2.0/UDP 192.168.1.121:5080;branch=z9hG4bK-325d0454d1c70483ef2a11a11b67a8c6
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d5ff5
Route: <sip:200@lslab.com>

v=0
o=LanScape 7154437 7154437 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8356 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#9, [07:53:37.859] 5750 Ms, To: 192.168.1.121:5080) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.121:5080;received=192.168.1.121;branch=z9hG4bK-325d0454d1c70483ef2a11a11b67a8c6
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d5ff5
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157117 INVITE
Contact: <sip:200@192.168.1.2:5094>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 218
Content-Type: application/sdp

v=0
o=200 7138359 7138359 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8704 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-16


<<<< RxRxRxRxRx (#11, [07:53:37.890] 31 Ms, From: 192.168.1.121:32783) <<<<
ACK sip:200@192.168.1.2:5094 SIP/2.0
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157117 ACK
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Tue, 25 Mar 2008 05:02:22 GMT
Via: SIP/2.0/UDP 192.168.1.121:5080;branch=z9hG4bK-e8b73c7e64bd00afc0f8a5de194955c9
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d5ff5
Route: <sip:200@192.168.1.2:5094>

Extension 203 removes the call from the hold state…

<<<< RxRxRxRxRx (#12, [07:53:39.875] 1985 Ms, From: 192.168.1.121:32783) <<<<
INVITE sip:200@192.168.1.2:5094 SIP/2.0
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Contact: <sip:203@192.168.1.2:5096>
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157118 INVITE
Max-Forwards: 20
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 223
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
Content-Type: application/sdp
Date: Tue, 25 Mar 2008 05:02:24 GMT
Via: SIP/2.0/UDP 192.168.1.121:5080;branch=z9hG4bK-43fb8600767eff9b3cb35b7c54fea08d
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d92dc
Route: <sip:200@lslab.com>

v=0
o=LanScape 7156468 7156468 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8356 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


>>>> TxTxTxTxTx (#10, [07:53:39.875] 2016 Ms, To: 192.168.1.121:5080) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.121:5080;received=192.168.1.121;branch=z9hG4bK-43fb8600767eff9b3cb35b7c54fea08d
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d92dc
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157118 INVITE
Contact: <sip:200@192.168.1.2:5094>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 218
Content-Type: application/sdp

v=0
o=200 7138359 7138359 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8704 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


<<<< RxRxRxRxRx (#13, [07:53:39.921] 46 Ms, From: 192.168.1.121:32783) <<<<
ACK sip:200@192.168.1.2:5094 SIP/2.0
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157118 ACK
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Tue, 25 Mar 2008 05:02:24 GMT
Via: SIP/2.0/UDP 192.168.1.121:5080;branch=z9hG4bK-e2efc11d650d61fee07d966da5e96df6
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d92dc
Route: <sip:200@192.168.1.2:5094>

Extension 203 now terminates the call…

<<<< RxRxRxRxRx (#14, [07:53:50.140] 10219 Ms, From: 192.168.1.121:32783) <<<<
BYE sip:200@192.168.1.2:5094 SIP/2.0
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
Cseq: 7157119 BYE
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitted SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Tue, 25 Mar 2008 05:02:34 GMT
Via: SIP/2.0/UDP 192.168.1.121:5080;branch=z9hG4bK-eb379ed1047d7ee17ca6cec618a5316b
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d9457
Route: <sip:200@lslab.com:5080>



>>>> TxTxTxTxTx (#11, [07:53:50.140] 10265 Ms, To: 192.168.1.121:5080) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.121:5080;received=192.168.1.121;branch=z9hG4bK-eb379ed1047d7ee17ca6cec618a5316b
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK006d9457
From: <sip:203@lslab.com>;tag=6d307f
To: "Extension 200" <sip:200@lslab.com>;tag=6d6405;x-UaId=xxxxx-yyyy-zzzzzz
Call-Id: 66a86671-c1e5-4288-8ebd-7caf4d1547ad-000001a4@192.168.1.2
CSeq: 7157119 BYE
User-Agent: LanScape VOIP Media Engine/5.12.8.12  (www.LanScapeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 0




************* Log Closed (Sep 12 07:53:53) *************




Questions:

1)
This may be a dumb question but: Did you configure authentication credentials in the single line soft phone sample app?

We ask this because if the media engine receives a challenge to a REGISTER request sent to the sipX server, it should be responding with a new REGISTER with computed authentication credentials.

2)
What version of sipX are you running and on what operating system?


Some things we can try:

1)
Give us access to your sipX server and we will register and quickly test from here. We will need a user account and the proper authentication credentials (auth user name, password and realm).

It always comes down to something simple. We are here all day today. Repost as soon as you can so we can get you on your way.


Thanks,

Support

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


Joined: August 26 2008
Location: Australia
Posts: 3
Posted: September 15 2008 at 8:52pm | IP Logged Quote Paul
Before I get to far into the debugging, it's not something simple like registrations not supported in the trial version :)

Questions:

LanScape question #1:
This may be a dumb question but: Did you configure authentication credentials in the single line soft phone sample app?

We ask this because if the media engine receives a challenge to a REGISTER request sent to the sipX server, it should be responding with a new REGISTER with computed authentication credentials.

Response:
Yes we did use the credentials and it does perform the 2nd modified challenge response, which seems the correct details but still gets a 401. I didn't post the complete logs but I can if required.

LanScape question #2:
What version of sipX are you running and on what operating system?

Response:
sipXconfig (3.10.2-013143 2008-07-23T18:09:14 ecs-centos5)


Please see the full challenge below:

Code:

************* Log Opened (Sep 16 11:46:17) *************

>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#1, 3404609 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:sip.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:48578;rport;branch=z9hG4bK0033f36a
From: <sip:200@sip.local:48578>;tag=34198f
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
CSeq: 3432583 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.20:48578>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1
 (www.LanScapeCorp.com - This is a trial version not for general deployment)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#1, 3404640 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@sip.local:48578>;tag=34198f
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
Cseq: 3432583 REGISTER
Via: SIP/2.0/UDP 192.168.1.20:48578;rport=48578;branch=z9hG4bK0033f36a
Www-Authenticate: Digest realm="sip.local", nonce="311d3136cd3a77fd5f97ec761f083bfc48cd254b"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Sun, 14 Sep 2008 14:52:59 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#2, 31 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:sip.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:48578;rport;branch=z9hG4bK003411ac
From: <sip:200@sip.local:48578>;tag=340803
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
CSeq: 3432584 REGISTER
Authorization: Digest  algorithm=md5,nonce="311d3136cd3a77fd5f97ec761f083bfc48cd254 b",
 realm="sip.local", response="9b48cef71ef6cd22bafbe65b40579 0bf",uri="sip:sip.local",username="200"
 Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.20:48578>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1
 (www.LanScapeCorp.com - This is a trial version not for general deployment)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#2, 16 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@sip.local:48578>;tag=340803
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
Cseq: 3432584 REGISTER
Via: SIP/2.0/UDP 192.168.1.20:48578;rport=48578;branch=z9hG4bK003411ac
Www-Authenticate: Digest realm="sip.local", nonce="2b8aeded21582b2256f72c64d364759d48cd254b"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Sun, 14 Sep 2008 14:52:59 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTxTxTxTxTxTxTxTx (#3, 31 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:sip.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.20:48578;rport;branch=z9hG4bK00347259
From: <sip:200@sip.local:48578>;tag=3457f6
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
CSeq: 3432585 REGISTER
Authorization: Digest  algorithm=md5,nonce="2b8aeded21582b2256f72c64d364759d48cd254 b",
 realm="sip.local",response="73721bce8e9166fca05c44fcd30d4 873",uri="sip:sip.local",username="200"
 Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.20:48578>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.1  (www.LanScapeCorp.com - This is a trial version not for general deployment)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRxRxRxRxRxRxRxRx (#3, 31 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@sip.local:48578>;tag=3457f6
To: <sip:200@sip.local:48578>
Call-Id: e67134b2-9dcf-4f07-b158-25c260134c67-000004b0@192.168.1.20
Cseq: 3432585 REGISTER
Via: SIP/2.0/UDP 192.168.1.20:48578;rport=48578;branch=z9hG4bK00347259
Www-Authenticate: Digest realm="sip.local", nonce="52181c1804d0c8c0943f9689c6ab7a2248cd254b"
User-Agent: sipXe





Regards


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 15 2008 at 9:40pm | IP Logged Quote support
Hi Paul,

We are here a bit late tonight so we thought we would respond.

The trial is fully functional – exactly like the normal product. Registrations will work the same in the trial as in the normal product.

You are correct, from an “eye ball” review of your SIP, it looks OK. Its something we are not seeing. We will have to verify that the “response” value is properly being computed.

We will look into getting a running CentOS version installed and take a look. We will post more when we get back in tomorrow morning. If you know of a VmWare workstation CentOS+sipX image we can use, post a link to this forum so we can grab it in the morning for testing.

Feel free to post any further info you may have.


Cheers from the states,


Support

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 17 2008 at 10:44am | IP Logged Quote support
Hi Paul,

Thanks for waiting for this response. It takes time to track down the issues.

We tested the media engine using CentOS v5.2 server (2.6.18-53.1.4.el5) and sipX 3.10.2 (3.10.2-013143 2008-07-23T18:09:14 ecs-centos5).

We were correct – sipX has changed the way they are processing the REGISTER requests. We finally tracked the problem down. The media engine is computing the challenge response properly and this is not the issue.

The media engine uses a new “From:” header tag in the response to the REGISTER’s 401 challenge. sipX 3.10.2 does not like this and therefore will never return a “200 OK” response.

We reviewed the SIP 3261 RFC and see that maintaining the same from header tag for the REGISTER challenge retry is OK. We will keep this change in the media engine moving forward.

We tested using two extensions, 200 and 203.

Here is a SIP log from our tests – from the standpoint of extension 200:


Code:

************* Log Opened (Sep 17 10:18:17) *************

Extension 200 registers…

>>>> TxTxTxTxTx (#1, [10:19:07.125] 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=z9hG4bK00f6aa 05
From: <sip:200@lslab.com>;tag=f6f427
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
CSeq: 16169851 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#1, [10:19:07.125] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@lslab.com>;tag=f6f427
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
Cseq: 16169851 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6aa05
Www-Authenticate: Digest realm="lslab.com", nonce="f0d3c9980 c8e21776e504c273f096e4748d10b41"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Wed, 17 Sep 2008 13:50:57 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, S UBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#2, [10:19:07.140] 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=z9hG4bK00f695 b8
From: <sip:200@lslab.com>;tag=f6f427
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
CSeq: 16169852 REGISTER
Authorization: Digest algorithm=md5,nonce="f0d3c9980c8e21776 e504c273f096e4748d10b41",
 realm="lslab.com",response="4eb362e80626d4fb648668e47e894b2 0",uri="sip:lslab.com",username="200"
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#2, [10:19:07.140] 15 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:200@lslab.com>;tag=f6f427
To: <sip:200@lslab.com>;tag=468703135
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
Cseq: 16169852 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f695b8
Contact: <sip:200@192.168.1.2:5294>;EXPIRES=1529
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Wed, 17 Sep 2008 13:50:57 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, S UBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0


Extension 200 calls extension 203…


>>>> TxTxTxTxTx (#3, [10:19:15.203] 8063 Ms, To: 192.168.1.191:5060) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK00f6b0 8b
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>
Contact: <sip:200@192.168.1.2:5294>;x-inst="VGVzdCBDYW xsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166151 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 220
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 16164171 16164171 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8604 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



<<<< RxRxRxRxRx (#3, [10:19:15.203] 8063 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166151 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6b08b
Content-Length: 0



<<<< RxRxRxRxRx (#4, [10:19:15.218] 15 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6b08b
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166151 INVITE
User-Agent: LanScape VOIP Media Engine/5.12.8.13 (www.LanSca peCorp.com)
Content-Length: 2
Date: Wed, 17 Sep 2008 13:51:02 GMT




<<<< RxRxRxRxRx (#5, [10:19:16.500] 1282 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6b08b
Record-Route: <sip:192.168.1.191>
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166151 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Wed, 17 Sep 2008 13:51:03 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 8620 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


>>>> TxTxTxTxTx (#4, [10:19:16.500] 1297 Ms, To: 192.168.1.191:5060) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6b08b
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166151 ACK
Max-Forwards: 70
Route: <sip:192.168.1.191>,<sip:203@192.168.1.2:509 6>
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 0


Extension 200 places extension 203 on hold…

>>>> TxTxTxTxTx (#5, [10:19:20.468] 3968 Ms, To: 192.168.1.191:5060) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK00f70b 12
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Contact: <sip:200@192.168.1.2:5294>
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166152 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Route: <sip:192.168.1.191>,<sip:203@192.168.1.2:509 6>
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 216
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 16169437 16169437 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8604 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-16



<<<< RxRxRxRxRx (#6, [10:19:20.468] 3968 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166152 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f70b12
Content-Length: 0



<<<< RxRxRxRxRx (#7, [10:19:20.468] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f70b12
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166152 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Wed, 17 Sep 2008 13:51:06 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 8620 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#6, [10:19:20.500] 32 Ms, To: 192.168.1.191:5060) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f70b12
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166152 ACK
Max-Forwards: 70
Route: <sip:203@192.168.1.2:5096>
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 0


Extension 200 takes extension 203 OFF hold…


>>>> TxTxTxTxTx (#7, [10:19:22.046] 1546 Ms, To: 192.168.1.191:5060) >>>>
INVITE sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport;branch=z9hG4bK00f6fb 90
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Contact: <sip:200@192.168.1.2:5294>
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166153 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
Route: <sip:192.168.1.191>,<sip:203@192.168.1.2:509 6>
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 220
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

v=0
o=200 16171000 16171000 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8604 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



<<<< RxRxRxRxRx (#8, [10:19:22.046] 1578 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 100 Trying
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166153 INVITE
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6fb90
Content-Length: 0



<<<< RxRxRxRxRx (#9, [10:19:22.046] 0 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6fb90
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166153 INVITE
Contact: <sip:203@192.168.1.2:5096>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 229
Content-Type: application/sdp
Date: Wed, 17 Sep 2008 13:51:07 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 8620 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


>>>> TxTxTxTxTx (#8, [10:19:22.078] 32 Ms, To: 192.168.1.191:5060) >>>>
ACK sip:203@lslab.com SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6fb90
From: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x -UaId=xxxxx-yyyy-zzzzzz
To: <sip:203@lslab.com>;tag=f6be1b
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166153 ACK
Max-Forwards: 70
Route: <sip:203@192.168.1.2:5096>
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 0


Extension 203 places extension 200 ON hold…

<<<< RxRxRxRxRx (#10, [10:19:23.640] 1594 Ms, From: 192.168.1.191:5060) <<<<
INVITE sip:200@192.168.1.2:5294 SIP/2.0
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Contact: <sip:203@192.168.1.2:5096>
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166152 INVITE
Max-Forwards: 20
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 221
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
Content-Type: application/sdp
Date: Wed, 17 Sep 2008 13:51:08 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-03e7b7 183bf5b090e287be338054efe76641
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f71115
Route: <sip:200@lslab.com>

v=0
o=LanScape 16172593 16172593 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 8620 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=sendonly
a=ptime:20
a=fmtp:101 0-16


>>>> TxTxTxTxTx (#9, [10:19:23.640] 1562 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;b ranch=z9hG4bK-sipXecs-03e7b7183bf5b090e287be338054efe76641
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f71115
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166152 INVITE
Contact: <sip:200@192.168.1.2:5294>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 220
Content-Type: application/sdp

v=0
o=200 16164171 16164171 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8604 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000/1
a=rtpmap:101 telephone-event/8000/1
a=recvonly
a=ptime:20
a=fmtp:101 0-16


<<<< RxRxRxRxRx (#11, [10:19:23.671] 31 Ms, From: 192.168.1.191:5060) <<<<
ACK sip:200@192.168.1.2:5294 SIP/2.0
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166152 ACK
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Wed, 17 Sep 2008 13:51:08 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-03ea77 326fc1ef2286d2e642e7e2491c1674
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f71115
Route: <sip:200@192.168.1.2:5294>


Extension 203 takes the call out of hold…

<<<< RxRxRxRxRx (#12, [10:19:24.984] 1313 Ms, From: 192.168.1.191:5060) <<<<
INVITE sip:200@192.168.1.2:5294 SIP/2.0
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Contact: <sip:203@192.168.1.2:5096>
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166153 INVITE
Max-Forwards: 20
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 225
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
Content-Type: application/sdp
Date: Wed, 17 Sep 2008 13:51:08 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-03ed60 092d3a4746f9a063bc14bc85cfb950
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f708f1
Route: <sip:200@lslab.com>

v=0
o=LanScape 16173953 16173953 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8620 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


>>>> TxTxTxTxTx (#10, [10:19:24.984] 1344 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;b ranch=z9hG4bK-sipXecs-03ed60092d3a4746f9a063bc14bc85cfb950
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f708f1
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166153 INVITE
Contact: <sip:200@192.168.1.2:5294>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 220
Content-Type: application/sdp

v=0
o=200 16164171 16164171 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 192.168.1.2
t=0 0
m=audio 8604 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


<<<< RxRxRxRxRx (#13, [10:19:25.031] 47 Ms, From: 192.168.1.191:5060) <<<<
ACK sip:200@192.168.1.2:5294 SIP/2.0
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166153 ACK
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Wed, 17 Sep 2008 13:51:08 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-03f081 6110c3034a7461b8002a794481089d
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f708f1
Route: <sip:200@192.168.1.2:5294>


Extension 203 terminates the call…


<<<< RxRxRxRxRx (#14, [10:19:27.281] 2250 Ms, From: 192.168.1.191:5060) <<<<
BYE sip:200@192.168.1.2:5294 SIP/2.0
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x-U aId=xxxxx-yyyy-zzzzzz
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
Cseq: 16166154 BYE
Max-Forwards: 20
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
X-Customheader-Extension-203: "This is a modified transmitte d SIP message."
X-Phoneline: 0
Content-Length: 0
Date: Wed, 17 Sep 2008 13:51:10 GMT
Via: SIP/2.0/UDP 192.168.1.191;branch=z9hG4bK-sipXecs-03f36a a8534f94ebf2f469362b9f9c8a45d6
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f70155
Route: <sip:200@lslab.com>



>>>> TxTxTxTxTx (#11, [10:19:27.281] 2297 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;b ranch=z9hG4bK-sipXecs-03f36aa8534f94ebf2f469362b9f9c8a45d6
Via: SIP/2.0/UDP 192.168.1.2:5096;rport=5096;branch=z9hG4bK0 0f70155
From: <sip:203@lslab.com>;tag=f6be1b
To: "Extension 200" <sip:200@lslab.com>;tag=f6a5fd;x-U aId=xxxxx-yyyy-zzzzzz
Call-Id: f62b8459-59d8-4004-a911-b2f9775ada17-00002780@192.1 68.1.2
CSeq: 16166154 BYE
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
x-PhoneLine: 0
Content-Length: 0


Extension 200 un-registers…


>>>> TxTxTxTxTx (#12, [10:19:29.593] 2312 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=z9hG4bK00f725 ab
From: <sip:200@lslab.com>;tag=f6ddae
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
CSeq: 16169853 REGISTER
Expires: 0
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#15, [10:19:29.593] 2312 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@lslab.com>;tag=f6ddae
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
Cseq: 16169853 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f725ab
Www-Authenticate: Digest realm="lslab.com", nonce="1d8e6e6b1 741fb3660b1c867b5938aa948d10b4f"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Wed, 17 Sep 2008 13:51:11 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, S UBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#13, [10:19:29.593] 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=z9hG4bK00f6f6 47
From: <sip:200@lslab.com>;tag=f6ddae
To: <sip:200@lslab.com>
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
CSeq: 16169854 REGISTER
Authorization: Digest algorithm=md5,nonce="1d8e6e6b1741fb366 0b1c867b5938aa948d10b4f",
 realm="lslab.com",response="20c0c15b9fcbda0ccd28a2f34c940a4 8",uri="sip:lslab.com",username="200"
Expires: 0
Max-Forwards: 70
Contact: <sip:200@192.168.1.2:5294>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanSc apeCorp.com)
x-CustomHeader-Extension-200: "This is a modified transmitte d SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#16, [10:19:29.609] 16 Ms, From: 192.168.1.191:5060) <<<<
SIP/2.0 200 OK
From: <sip:200@lslab.com>;tag=f6ddae
To: <sip:200@lslab.com>;tag=635723058
Call-Id: 4e12abac-fd9a-456e-bae5-019be78c9bed-00002780@192.1 68.1.2
Cseq: 16169854 REGISTER
Via: SIP/2.0/UDP 192.168.1.2:5294;rport=5294;branch=z9hG4bK0 0f6f647
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Wed, 17 Sep 2008 13:51:11 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, S UBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0


************* Log Closed (Sep 17 10:19:33) *************




We want to thank you for bringing this to our attention.

We will make ready for you a fully functional time bombed version that you can use for testing moving forward. We will make this download available for you via one of our support FTP servers. This image will be an “engineering release”. You basically take the file images from the “engineering release” and replace the same file names in your installed product image.

We will repost when we have the download set up.

Thanks again Peter and Paul!


Support

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 17 2008 at 11:42am | IP Logged Quote support
Hi Peter and Paul,

We have uploaded an “engineering release” of the media engine to your support FTP account. Please download the “v5.12.8.13 DLL Only - Expires 12-30-08.zip” archive.

See the release notes that come with the image to see how to use it. You can basically take the file images in the archive and replace the standard installed files of the same name. You must rebuild your target VOIP apps when using this release. Note also that you may experience some minor sample application build errors – that should be simple to fix.

You should have received an email with your support FTP account login info. Please post to this forum thread again if you have not received the FTP info.

Please continue to let us know how your testing progresses. It would be good to also test sipX’s ability to challenge other SIP message types. We are not sipX gurus so if you find some other issue, don’t hesitate to contact us again.

Thanks,


Support

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


Joined: May 01 2008
Location: Australia
Posts: 9
Posted: September 18 2008 at 3:10am | IP Logged Quote peter.conklin
Hi,

We have downloaded the modified files and the registration now works (Thanks for that) but ... ;-)

1) When copying the new header file the definitions for:

     SipRegisterIntervalError,                             // API return value, GLOBAL_NOTIFICATION
     SipRegisterTimeOut,                                        // GLOBAL_NOTIFICATION

are incorrect and need to be changed back to:

     SipRegistrationIntervalError,                             // API return value, GLOBAL_NOTIFICATION
     SipRegistrationTimeOut,                                        // GLOBAL_NOTIFICATION

and then they work fine.

Also there seems to be a problem with the latest Sip Communicator causing an access vialotion in the dll. I have attached the logs below. I tested also with X-Lite which worked perfectly.

Regards

Code:

************* Log Opened (Sep 18 18:05:00) *************

>>>> TxTxTxTxTx (#1, [18:06:34.937] 0 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:sip.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.33:5060;rport;branch=z9hG4bK023b0202
From: <sip:200@sip.local>;tag=23b080b
To: <sip:200@sip.local>
Call-Id: 8d0f9dd4-0f3d-4817-9b8f-9a401451351c-00000f88@192.168.1.33
CSeq: 3848496 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.33:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#1, [18:06:34.968] 0 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 401 Unauthorized
From: <sip:200@sip.local>;tag=23b080b
To: <sip:200@sip.local>
Call-Id: 8d0f9dd4-0f3d-4817-9b8f-9a401451351c-00000f88@192.168.1.33
Cseq: 3848496 REGISTER
Via: SIP/2.0/UDP 192.168.1.33:5060;rport=5060;branch=z9hG4bK023b0202
Www-Authenticate: Digest realm="sip.local", nonce="9e3dccf31296482182c8168d13c974d648cf3551"
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Tue, 16 Sep 2008 04:25:53 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



>>>> TxTxTxTxTx (#2, [18:06:34.968] 31 Ms, To: 192.168.2.65:5060) >>>>
REGISTER sip:sip.local SIP/2.0
Via: SIP/2.0/UDP 192.168.1.33:5060;rport;branch=z9hG4bK023b026a
From: <sip:200@sip.local>;tag=23b080b
To: <sip:200@sip.local>
Call-Id: 8d0f9dd4-0f3d-4817-9b8f-9a401451351c-00000f88@192.168.1.33
CSeq: 3848497 REGISTER
Authorization: Digest  algorithm=md5,nonce="9e3dccf31296482182c8168d13c974d648cf355 1",
 realm="sip.local",response="73f9613e6cb1f73dbc228f1060f6a 54c",uri="sip:sip.local",username="200"
 Expires: 3600
Max-Forwards: 70
Contact: <sip:200@192.168.1.33:5060>;user=phone
User-Agent: LanScape VOIP Media Engine/5.12.8.13  (www.LanScapeCorp.com)
x-MyCustomHeader: "This is a modified transmitted SIP message."
Content-Length: 0



<<<< RxRxRxRxRx (#2, [18:06:35.000] 32 Ms, From: 192.168.2.65:5060) <<<<
SIP/2.0 200 OK
From: <sip:200@sip.local>;tag=23b080b
To: <sip:200@sip.local>;tag=1464415775
Call-Id: 8d0f9dd4-0f3d-4817-9b8f-9a401451351c-00000f88@192.168.1.33
Cseq: 3848497 REGISTER
Via: SIP/2.0/UDP 192.168.1.33:5060;rport=5060;branch=z9hG4bK023b026a
Contact: <sip:200@192.168.1.33:5060>;EXPIRES=1688
User-Agent: sipXecs/3.10.2 sipXecs/registry (Linux)
Date: Tue, 16 Sep 2008 04:25:53 GMT
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE
Accept-Language: en
Supported: gruu
Content-Length: 0



<<<< RxRxRxRxRx (#3, [18:08:03.187] 88187 Ms, From: 192.168.2.65:5060) <<<<
INVITE sip:200@192.168.1.33:5060 SIP/2.0
Record-Route:  <sip:192.168.2.65:5060;lr;sipXecs-rs=%2Afrom%7ENTEwNGVmZW U%60.400_authrules%2Aauth%7E%2179d75995b822ae0c309570d3c1d6a bff>
Call-Id: 341fe151e90b2ab1e752164a07c8cac2@0.0.0.0
Cseq: 1 INVITE
From: "1234" <sip:1234@192.168.2.65>;tag=5104efee
To: <sip:200@192.168.2.65>
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0904429bebcd98a289fc4f12 bd9d4eac8569
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0901803b3e3f8e52b07aa187 08bfd02b8e72~ad570d7e443579f689d27f6c7d4bbc70
 Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-08fbe63f538985eafd2fa342 606832189789~7ebaa684a15104e667513f23cab3fc73
 Via: SIP/2.0/UDP  192.168.1.34:5060;branch=z9hG4bK33f766f68de6222041e117b9cee5 ba90
Max-Forwards: 16
User-Agent: SIP Communicator 1.0-alpha3-nightly.build.1316 Windows XP
Contact: "1234" <sip:1234@192.168.1.34:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 154
Date: Tue, 16 Sep 2008 04:26:56 GMT

v=0
o=1234 0 0 IN IP4 192.168.1.34
s=-
c=IN IP4 192.168.1.34
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 110 5 4
m=video 5002 RTP/AVP 34 26 31
a=recvonly


<<<< RxRxRxRxRx (#4, [18:08:03.921] 734 Ms, From: 192.168.2.65:5060) <<<<
INVITE sip:200@192.168.1.33:5060 SIP/2.0
Record-Route:  <sip:192.168.2.65:5060;lr;sipXecs-rs=%2Afrom%7ENTEwNGVmZW U%60.400_authrules%2Aauth%7E%2179d75995b822ae0c309570d3c1d6a bff>
Call-Id: 341fe151e90b2ab1e752164a07c8cac2@0.0.0.0
Cseq: 1 INVITE
From: "1234" <sip:1234@192.168.2.65>;tag=5104efee
To: <sip:200@192.168.2.65>
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0904429bebcd98a289fc4f12 bd9d4eac8569
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0901803b3e3f8e52b07aa187 08bfd02b8e72~ad570d7e443579f689d27f6c7d4bbc70
 Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-08fbe63f538985eafd2fa342 606832189789~7ebaa684a15104e667513f23cab3fc73
 Via: SIP/2.0/UDP  192.168.1.34:5060;branch=z9hG4bK33f766f68de6222041e117b9cee5 ba90
Max-Forwards: 16
User-Agent: SIP Communicator 1.0-alpha3-nightly.build.1316 Windows XP
Contact: "1234" <sip:1234@192.168.1.34:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 154
Date: Tue, 16 Sep 2008 04:26:56 GMT

v=0
o=1234 0 0 IN IP4 192.168.1.34
s=-
c=IN IP4 192.168.1.34
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 110 5 4
m=video 5002 RTP/AVP 34 26 31
a=recvonly


<<<< RxRxRxRxRx (#5, [18:08:05.468] 1547 Ms, From: 192.168.2.65:5060) <<<<
INVITE sip:200@192.168.1.33:5060 SIP/2.0
Record-Route:  <sip:192.168.2.65:5060;lr;sipXecs-rs=%2Afrom%7ENTEwNGVmZW U%60.400_authrules%2Aauth%7E%2179d75995b822ae0c309570d3c1d6a bff>
Call-Id: 341fe151e90b2ab1e752164a07c8cac2@0.0.0.0
Cseq: 1 INVITE
From: "1234" <sip:1234@192.168.2.65>;tag=5104efee
To: <sip:200@192.168.2.65>
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0904429bebcd98a289fc4f12 bd9d4eac8569
Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-0901803b3e3f8e52b07aa187 08bfd02b8e72~ad570d7e443579f689d27f6c7d4bbc70
 Via: SIP/2.0/UDP  192.168.2.65;branch=z9hG4bK-sipXecs-08fbe63f538985eafd2fa342 606832189789~7ebaa684a15104e667513f23cab3fc73
 Via: SIP/2.0/UDP  192.168.1.34:5060;branch=z9hG4bK33f766f68de6222041e117b9cee5 ba90
Max-Forwards: 16
User-Agent: SIP Communicator 1.0-alpha3-nightly.build.1316 Windows XP
Contact: "1234" <sip:1234@192.168.1.34:5060;transport=udp>
Content-Type: application/sdp
Content-Length: 154
Date: Tue, 16 Sep 2008 04:26:56 GMT

v=0
o=1234 0 0 IN IP4 192.168.1.34
s=-
c=IN IP4 192.168.1.34
t=0 0
m=audio 5000 RTP/AVP 0 8 97 3 110 5 4
m=video 5002 RTP/AVP 34 26 31
a=recvonly



************* Log Closed (Sep 18 18:08:11) *************




Back to Top View peter.conklin's Profile Search for other posts by peter.conklin
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 18 2008 at 6:11am | IP Logged Quote support
Hi Peter,

Yes, when using “engineering releases” of the media engine, the sample source code may get minor build errors. Theses are usually due to API updates/changes or like you found, the SipRegistrationIntervalError and SipRegistrationTimeOut enumeration values have been renamed for consistency. This is normal. Do not change anything in the header file – change the sample source code to match the header file.

Regarding SIP Communicator:
We will test immediately and look into this. Please, try to get a full heap crash dump (mini dump) when the media engine app crashes. We can use this mini dump directly to see what is going on. Please upload your full heap mini dump to your support FTP account.

Creating a crash dump:
You probably already know this but… You can create a crash dump by allowing the offending app to be debugged by your Visual Studio 2003/2005/2008 debugger. Once in the debugger, select “Debug->Save Dump As” from the main menu. A “Save As” dialog will be displayed. Make sure to specify “minidump with heap” in the “Save as type” drop down list box. The old “Dr Watson” can also be used if you have that.


Thanks for your continued information and input. Without you and others like you, we would never be able to track down all the SIP inter-op issues or possible bugs… no matter how hard we try and how much we test.


Support

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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 18 2008 at 8:30am | IP Logged Quote support
Hi Peter,

We see right off what is going on. The INVITE coming from the SIP Communication app does not place media attributes into its SDP. For example:

An INVITE request with media attributes:

Code:

INVITE sip:RtpMon@192.168.1.2:5068 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.80:5094;rport;branch=z9hG4bK430aca96
From: "Extension 111" <sip:111@192.168.1.80:5094>;tag=430ac3ad;x-UaId=xxxxx-yyyy-zzzzzz
To: <sip:RtpMon@192.168.1.2:5068>
Contact: <sip:111@192.168.1.80:5094>;x-inst="VGVzdCBDYWxsIERhdGEgZnJvbSB0aGUgVlBob25lIGFwcC4="
Call-Id: 9dbea5e3-0bfb-4a00-9c84-657153362731-00000e08@192.168.1.80
CSeq: 712536 INVITE
Max-Forwards: 70
Organization:  44388BAF-8E86-4E68-8CB3-4ED9BB21E9C4
x-CustomHeader-Extension-111: "This is a modified transmitted SIP message."
x-PhoneLine: 0
Content-Length: 437
User-Agent: LanScape VOIP Media Engine/5.12.8.14  (www.LanScapeCorp.com)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp

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




The SIP Communicator’s INVITE request:

Code:

INVITE sip:333@192.168.1.2:5068 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bKfb609821ad9a5d812ef15e228fe8d9fe8.0
Via: SIP/2.0/UDP 192.168.1.140:61437;branch=z9hG4bKaab8aca45af09bdbac775475fdad26f4;rport=61437;received=192.168.1.140
Record-Route: <sip:192.168.1.2:5060;lr>
From: "203" <sip:203@PS>;tag=439d80af
To: <sip:333@PS>
Call-ID: 6fadafdf1b76870cf6dc214c54eab389@0.0.0.0
CSeq: 2 INVITE
Contact: "203" <sip:203@192.168.1.140:61437;transport=udp>
max-forwards: 69
Server: LanScape Centrex Proxy/3.42.2.9 (www.LanScapeCorp.com)
Content-Type: application/sdp
Content-Length:   153

v=0
o=203 0 0 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 16002 RTP/AVP 0 8 97 3 110 5 4
m=video 16130 RTP/AVP 34 26 31
No media attributes for the specified codecs...
a=recvonly



This lack of media attributes causes the media engine to choke (crash). We will fix this issue in the next engineering release for all known RTP audio and video payload types. Thanks Peter for spotting this issue.

Regarding dynamic payload types 97-127:
It would be good to send an email to the SIP Communicator guys because for dynamic RTP payload types in the range of 97 through 127, the media engine has no idea what codecs are mapped without media attributes. Dynamic payload types should be automatic and require no special configuration other than enabling the codec type on the receiving end of the call. So audio codecs types 97 and 110 above will never be used by the media engine even if the media engine dynamically supports them. Without additional media attributes, there is no way to map them to known dynamic codec types that are enabled or supported. For example: The iLBC 20Ms and 30Ms codecs are supported using dynamic payload numbers.

We will get you a product update when it is ready.

By the way, is your group planning to purchase?


Thanks,


Support


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


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: September 18 2008 at 12:19pm | IP Logged Quote support
Hi Peter,

Please download the following media engine update: “v5.12.8.14 DLL Only - Expires 12-30-08.zip”.

It should take card of the crash issue you reported above.

We tested using SIP Communicator “sip-communicator-1.0-alpha3-nightly.build.1316.exe”.

Right now, we have only tested the media engine with SIP Communicator using aLaw and uLaw codecs. It would be nice to know what the 97 and 110 dynamic payloads are supported by SIP Communicator.

We tested initiating and receiving calls using the media engine and SIP communicator. Call hold/un-hold also looks like it works well from either media engine or SIP Communicator. We tested using LanScape Centrex SIP Proxy + LanScape VOIP Media Proxy and with sipX server v3.10.2.

If there are any further issues, let’s start a new support forum thread – this one is getting kind of long. :)

Let us know what else you find.


Thanks,

Support


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

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

  Post ReplyPost New Topic
Printable version Printable version

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





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