| Author |
|
hermes
Junior
Joined: October 27 2006
Posts: 64
|
| Posted: October 27 2006 at 6:21am | IP Logged
|
|
|
Hello, I´ve just downloaded Centrex Proxy Server trial version and it works successful in my private network, but when I tried to register with a software sip phone placed outside private network Proxy response an "Unauthorized" SIP message.
This is the log:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 86.218.11.153:5060) <<<<
REGISTER sip:192.168.1.3:5060 SIP/2.0
Via: SIP/2.0/UDP 86.218.11.153:5060;branch=z9hG4bKabd9803e75c79b95154698b487a 2c53c
Via: SIP/2.0/UDP 10.24.64.14;branch=z9hG4bK-e4133ce322197cb8;rport
From: <sip:user1@192.168.1.3:5060>;tag=41365140
To: <sip:user1@192.168.1.3:5060>
Call-ID: 9862f10d1cae47b755a66b0b06b13d1e
CSeq: 1 REGISTER
Contact: <sip:user1@86.218.11.153:5060>
expires: 15000
date: Fri, 27 Oct 2006 10:45:58 GMT
max-forwards: 19
user-agent: sipX/1.3.0 (WinNT)
supported: replaces
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 86.218.11.153:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 86.218.11.153:5060;branch=z9hG4bKabd9803e75c79b95154698b487a 2c53c;rport=5060;received=86.218.11.153
Via: SIP/2.0/UDP 10.24.64.14;branch=z9hG4bK-e4133ce322197cb8;rport
From: <sip:user1@192.168.1.3:5060>;tag=41365140
To: <sip:user1@192.168.1.3:5060>
Call-ID: 9862f10d1cae47b755a66b0b06b13d1e
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="MyCompany.com", nonce="381555b30d42371624f3f89b12d4cf19", opaque="7ab82a7763caf12db5f0a4eca313c5cb"
Server: LanScape Centrex Proxy/3.41.1.1 (www.LanScapeCorp.com)
Content-Length: 0
Thanks
|
| Back to Top |
|
| |
hermes
Junior
Joined: October 27 2006
Posts: 64
|
| Posted: October 27 2006 at 6:26am | IP Logged
|
|
|
It only happends when User Authentication option is enabled.
|
| Back to Top |
|
| |
hermes
Junior
Joined: October 27 2006
Posts: 64
|
| Posted: October 27 2006 at 9:19am | IP Logged
|
|
|
I´ve tried to register in Centrex Proxy with a Lanscape Phone (from outside my private network) and it work fine; but when I tried to dial Proxy´s log said:
Bad "Content-Length" header detected INVITE message"
Error parsing SIP protocol packet from 87.218.11.153:5060. Possibly non-compliant SIP message
This is the log:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 87.218.11.153:5060) <<<<
INVITE sip:user2@84.77.108.176 SIP/2.0
Via: SIP/2.0/UDP 87.218.11.153:5060;branch=z9hG4bKab7b3fc8bc80cefcfb08e045073 ea095
Via: SIP/2.0/UDP 10.24.64.14:5060;rport;branch=z9hG4bK00f0004e
From: user1 <sip:user1@84.77.108.176>;tag=efe973
To: <sip:user2@84.77.108.176>
Call-ID: 02faf4dc-ce29-4a1c-89b0-5a2b69734569-00000fbc@10.24.64.14
CSeq: 15737221 INVITE
Contact: <sip:user1@10.24.64.14:5060>
max-forwards: 69
organization: BF73E56A-76AC-40F1-B8A8-4E0B4C8641C9
x-mycustomheader: "This is a modified transmitted SIP message."
user-agent: LanScape VOIP Media Engine/5.12.3.6 (www.LanScapeCorp.com - This is a trial version not for general deployment)
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 22828
v=0
o=user1 15710437 15710437 IN IP4 87.218.11.153
s=LanScape
c=IN IP4 87.218.11.153
t=0 0
m=audio 7070 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-15
****** Error: Last SIP message could not be parsed. Hex dump follows ***** (From: 87.218.11.153:5060) <<<<
0000 49 4E 56 49 54 45 20 73 - 69 70 3A 70 61 63 6F 40 INVITE sip:user2@
0010 38 34 2E 37 37 2E 31 30 - 38 2E 31 37 36 20 53 49 84.77.108.176 SI
0020 50 2F 32 2E 30 0D 0A 56 - 69 61 3A 20 53 49 50 2F P/2.0..Via: SIP/
0030 32 2E 30 2F 55 44 50 20 - 38 37 2E 32 31 38 2E 31 2.0/UDP 87.218.1
0040 31 2E 31 35 32 3A 35 30 - 36 30 3B 62 72 61 6E 63 1.152:5060;branc
0050 68 3D 7A 39 68 47 34 62 - 4B 61 62 37 62 33 66 63 h=z9hG4bKab7b3fc
0060 38 62 63 38 30 63 65 66 - 63 66 62 30 38 65 30 34 8bc80cefcfb08e04
0070 35 30 37 33 65 61 30 39 - 35 0D 0A 56 69 61 3A 20 5073ea095..Via:
0080 53 49 50 2F 32 2E 30 2F - 55 44 50 20 31 30 2E 32 SIP/2.0/UDP 10.2
0090 34 2E 36 34 2E 31 34 3A - 35 30 36 30 3B 72 70 6F 4.64.14:5060;rpo
00A0 72 74 3B 62 72 61 6E 63 - 68 3D 7A 39 68 47 34 62 rt;branch=z9hG4b
00B0 4B 30 30 66 30 30 30 34 - 65 0D 0A 46 72 6F 6D 3A K00f0004e..From:
00C0 20 61 6C 62 65 72 74 6F - 20 3C 73 69 70 3A 61 6C user1 <sip:al
00D0 62 65 72 74 6F 40 38 34 - 2E 37 37 2E 31 30 38 2E berto@84.77.108.
00E0 31 37 36 3E 3B 74 61 67 - 3D 65 66 65 39 37 33 0D 176>;tag=efe973.
00F0 0A 54 6F 3A 20 3C 73 69 - 70 3A 70 61 63 6F 40 38 .To: <sip:user2@8
0100 34 2E 37 37 2E 31 30 38 - 2E 31 37 36 3E 0D 0A 43 4.77.108.176>..C
0110 61 6C 6C 2D 49 44 3A 20 - 30 32 66 61 66 34 64 63 all-ID: 02faf4dc
0120 2D 63 65 32 39 2D 34 61 - 31 63 2D 38 39 62 30 2D -ce29-4a1c-89b0-
0130 35 61 32 62 36 39 37 33 - 34 35 36 39 2D 30 30 30 5a2b69734569-000
0140 30 30 66 62 63 40 31 30 - 2E 32 34 2E 36 34 2E 31 00fbc@10.24.64.1
0150 34 0D 0A 43 53 65 71 3A - 20 31 35 37 33 37 32 32 4..CSeq: 1573722
0160 31 20 49 4E 56 49 54 45 - 0D 0A 43 6F 6E 74 61 63 1 INVITE..Contac
0170 74 3A 20 3C 73 69 70 3A - 61 6C 62 65 72 74 6F 40 t: <sip:user1@
0180 31 30 2E 32 34 2E 36 34 - 2E 31 34 3A 35 30 36 30 10.24.64.14:5060
0190 3E 0D 0A 6D 61 78 2D 66 - 6F 72 77 61 72 64 73 3A >..max-forwards:
01A0 20 36 39 0D 0A 6F 72 67 - 61 6E 69 7A 61 74 69 6F 69..organizatio
01B0 6E 3A 20 42 46 37 33 45 - 35 36 41 2D 37 36 41 43 n: BF73E56A-76AC
01C0 2D 34 30 46 31 2D 42 38 - 41 38 2D 34 45 30 42 34 -40F1-B8A8-4E0B4
01D0 43 38 36 34 31 43 39 0D - 0A 78 2D 6D 79 63 75 73 C8641C9..x-mycus
01E0 74 6F 6D 68 65 61 64 65 - 72 3A 20 22 54 68 69 73 tomheader: "This
01F0 20 69 73 20 61 20 6D 6F - 64 69 66 69 65 64 20 74 is a modified t
0200 72 61 6E 73 6D 69 74 74 - 65 64 20 53 49 50 20 6D ransmitted SIP m
0210 65 73 73 61 67 65 2E 22 - 0D 0A 75 73 65 72 2D 61 essage."..user-a
0220 67 65 6E 74 3A 20 4C 61 - 6E 53 63 61 70 65 20 56 gent: LanScape V
0230 4F 49 50 20 4D 65 64 69 - 61 20 45 6E 67 69 6E 65 OIP Media Engine
0240 2F 35 2E 31 32 2E 33 2E - 36 20 20 28 77 77 77 2E /5.12.3.6 (www.
0250 4C 61 6E 53 63 61 70 65 - 43 6F 72 70 2E 63 6F 6D LanScapeCorp.com
0260 20 2D 20 54 68 69 73 20 - 69 73 20 61 20 74 72 69 - This is a tri
0270 61 6C 20 76 65 72 73 69 - 6F 6E 20 6E 6F 74 20 66 al version not f
0280 6F 72 20 67 65 6E 65 72 - 61 6C 20 64 65 70 6C 6F or general deplo
0290 79 6D 65 6E 74 29 0D 0A - 41 6C 6C 6F 77 3A 20 49 yment)..Allow: I
02A0 4E 56 49 54 45 2C 20 41 - 43 4B 2C 20 4F 50 54 49 NVITE, ACK, OPTI
02B0 4F 4E 53 2C 20 42 59 45 - 2C 20 43 41 4E 43 45 4C ONS, BYE, CANCEL
02C0 2C 20 53 55 42 53 43 52 - 49 42 45 2C 20 4E 4F 54 , SUBSCRIBE, NOT
02D0 49 46 59 0D 0A 43 6F 6E - 74 65 6E 74 2D 54 79 70 IFY..Content-Typ
02E0 65 3A 20 61 70 70 6C 69 - 63 61 74 69 6F 6E 2F 73 e: application/s
02F0 64 70 0D 0A 43 6F 6E 74 - 65 6E 74 2D 4C 65 6E 67 dp..Content-Leng
0300 74 68 3A 20 32 32 38 32 - 38 0D 0A 0D 0A 76 3D 30 th: 22828....v=0
0310 0D 0A 6F 3D 61 6C 62 65 - 72 74 6F 20 31 35 37 31 ..o=user1 1571
0320 30 34 33 37 20 31 35 37 - 31 30 34 33 37 20 49 4E 0437 15710437 IN
0330 20 49 50 34 20 38 37 2E - 32 31 38 2E 31 31 2E 31 IP4 87.218.11.1
0340 35 32 0D 0A 73 3D 4C 61 - 6E 53 63 61 70 65 0D 0A 52..s=LanScape..
0350 63 3D 49 4E 20 49 50 34 - 20 38 37 2E 32 31 38 2E c=IN IP4 87.218.
0360 31 31 2E 31 35 32 0D 0A - 74 3D 30 20 30 0D 0A 6D 11.152..t=0 0..m
0370 3D 61 75 64 69 6F 20 37 - 30 37 30 20 52 54 50 2F =audio 7070 RTP/
0380 41 56 50 20 30 20 31 30 - 31 0D 0A 61 3D 72 74 70 AVP 0 101..a=rtp
0390 6D 61 70 3A 30 20 50 43 - 4D 55 2F 38 30 30 30 2F map:0 PCMU/8000/
03A0 31 0D 0A 61 3D 72 74 70 - 6D 61 70 3A 31 30 31 20 1..a=rtpmap:101
03B0 74 65 6C 65 70 68 6F 6E - 65 2D 65 76 65 6E 74 2F telephone-event/
03C0 38 30 30 30 2F 31 0D 0A - 61 3D 73 65 6E 64 72 65 8000/1..a=sendre
03D0 63 76 0D 0A 61 3D 70 74 - 69 6D 65 3A 32 30 0D 0A cv..a=ptime:20..
03E0 61 3D 66 6D 74 70 3A 31 - 30 31 20 30 2D 31 35 0D a=fmtp:101 0-15.
03F0 0A &nbs p; &nbs p; &nbs p; &nbs p; &nbs p; .
************************************************************ *********************************
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 87.218.11.153:5060) >>>>
SIP/2.0 400 SIP Parse Error
Via: SIP/2.0/UDP 87.218.11.153:5060;branch=z9hG4bKab7b3fc8bc80cefcfb08e045073 ea095
From: user1 <sip:user1@84.77.108.176>;tag=efe973
To: <sip:user2@84.77.108.176>
Call-ID: 02faf4dc-ce29-4a1c-89b0-5a2b69734569-00000fbc@10.24.64.14
CSeq: 15737221 INVITE
Server: LanScape Centrex Proxy/3.41.1.1 (www.LanScapeCorp.com)
Content-Length: 0
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: November 14 2006 at 9:30am | IP Logged
|
|
|
Hi hermes,
Sorry for the long delay in this response. This normally does not happen.
Your first problem is that you have authentication enabled on the SIP proxy and it is not enabled on your LanScape soft phone sample application. Either disable authentication at the SIP proxy or set the soft phone to use the proper authentication credentials.
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: November 14 2006 at 9:39am | IP Logged
|
|
|
Hi hermes,
The second issue you have posted shows us that the “Content-Length:” SIP header has a bad value for the SDP data size. The value of 22828 is wrong. We will have to look into this and see why this occurring.
What is happening is this:
1)
The soft phone example application is sending an INVITE to the SIP proxy.
2)
The SIP proxy receives the INVITE and tries to parse the SIP message.
3)
When the “Content-Length:” SIP header gets parsed, the amount of SDP data is stated to be 22828 characters. This value is wrong for some reason.
4)
The SIP proxy parses the SDP data but determines that there is not enough SDP data so it generates a parse error. The SIP proxy thinks that it has receive an incomplete SIP INVITE message. Therefore the error.
We will look into why the Media Engine may be generating this bad value and repost to this thread.
Support
|
| Back to Top |
|
| |
hermes
Junior
Joined: October 27 2006
Posts: 64
|
| Posted: November 14 2006 at 9:50am | IP Logged
|
|
|
Hello,
I don´t understand why it works successfully in a private network and not in a public network. I suppose that the same SIP INVITE message is sended in both cases.
I´ve tested it with other user agents like sipXtapi, VaxVoIP, Lanscape Engine... but none of them works.
Thanks
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: November 14 2006 at 11:02am | IP Logged
|
|
|
Hi hermes,
Ok. We need to get as specific as possible. We need to further understand your situation. We need to know if it’s a bug in our software or something else. The SIP proxy is picking up the valid “Content-Length:” header error as it should. However, the VOIP media engine should not be sending a bad “Content-Length:” header value for the INVITE.
Please help us understand by answering the following questions and performing these tasks:
1)
Does the proxy function in your private network when used with the LanScape VOIP media engine and its example VOIP applications?
2)
Does the proxy function in your private network when used with other vendor soft phones or SIP devices?
3)
Do any of the soft phones/applications (ones from other manufacturers - sipXtapi, VaxVoIP) succeed in making a VOIP phone call via the LanScape Centrex SIP proxy when the soft phones are outside of your private network?
4)
We need to see if the media engine is sending bad INVITE messages. We need to log the SIP messages that are sent by the VOIP media engine single line soft phone sample application when it is running outside of your private network and the SIP proxy.
Enable SIP logging in the single line phone sample app: Goto the Phonebase.cpp module.
Look for the code lines:
StartupParams.LogSipMessages = FALSE;
StartupParams.pSipLogFileName = "SipMessageLog.log";
Change FALSE to TRUE and rebuild the release version of the single line soft phone.
Put the single line soft phone outside of your private network and make a call. Send us a SIP log of the soft phone and a SIP log of the SIP proxy.
We need to see if some other network element is changing the INVITE SIP message between the VOIP media engine single line soft phone and the Centrex SIP proxy in your private network. The INVITE message sent by the soft phone should be exactly the same as the INVITE received by the proxy.
5)
Here is another post from a user that had a similar problem with bad “Content-Length:” headers using the VaxSIPUserAgent/2.0:
http://www.lanscapecorp.com/forum/forum_posts.asp?TID=189&PN =1
Is this previous post also from you or someone else at your location?
We will wait for your responses.
Support
|
| Back to Top |
|
| |
hermes
Junior
Joined: October 27 2006
Posts: 64
|
| Posted: November 16 2006 at 7:18am | IP Logged
|
|
|
Hello,
I´ve tested Centrex Proxy and Media Proxy one more time. The environment is the next one:
1.- Centrex Proxy and Media Proxy servers are located in my private network (Private IP: 192.168.1.3 and Public IP: 84.77.107.136)
2.- user1 is a soft phone locate outside my private network (Private IP: 10.24.64.18 and Public IP: 87.218.11.41).
3.- user2 is a soft phone locate in my private network (Private IP: 192.168.1.8 and Public IP: 84.77.107.136).
Both soft phone are registered successfully. This is the Centrex Proxy´s log when I tried to call from user1 to user2:
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 87.218.11.41:5060) <<<<
INVITE sip:user2@84.77.107.136 SIP/2.0
Via: SIP/2.0/UDP 87.218.11.41:5060;branch=z9hG4bK9f406ef0c7f210b4c90046dee25e d3d0
Via: SIP/2.0/UDP 10.24.64.18;branch=z9hG4bK-b57e788a2c471492;rport
From: <sip:user1@192.168.1.3:5060>;tag=1c10594
To: <sip:user2@84.77.107.136>
Call-ID: s_39120002_49032964c255b44d
CSeq: 29516 INVITE
Contact: <sip:user1@87.218.11.41:5060>
date: Thu, 16 Nov 2006 12:30:36 GMT
max-forwards: 19
user-agent: sipX/1.3.0 (WinNT)
supported: replaces
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, INFO, REGISTER, SUBSCRIBE, NOTIFY
Content-Type: application/sdp
Content-Length: 20202
v=0
o=sipX 5 5 IN IP4 87.218.11.41
s=call
c=IN IP4 87.218.11.41
t=0 0
m=audio 7070 RTP/AVP 0 8 96
a=rtcp:16002
a=rtpmap:0 pcmu/8000/1
a=rtpmap:8 pcma/8000/1
a=rtpmap:96 telephone-event/8000/1
****** Error: Last SIP message could not be parsed. Hex dump follows ***** (From: 87.218.11.41:5060) <<<<
0000 49 4E 56 49 54 45 20 73 - 69 70 3A 61 6C 62 65 72 INVITE sip:alber
0010 74 6F 40 38 34 2E 37 37 - 2E 31 30 37 2E 31 33 39 to@84.77.107.136
0020 20 53 49 50 2F 32 2E 30 - 0D 0A 56 69 61 3A 20 53 SIP/2.0..Via: S
0030 49 50 2F 32 2E 30 2F 55 - 44 50 20 38 37 2E 32 31 IP/2.0/UDP 87.21
0040 38 2E 31 31 2E 34 36 3A - 35 30 36 30 3B 62 72 61 8.11.46:5060;bra
0050 6E 63 68 3D 7A 39 68 47 - 34 62 4B 39 66 34 30 36 nch=z9hG4bK9f406
0060 65 66 30 63 37 66 32 31 - 30 62 34 63 39 30 30 34 ef0c7f210b4c9004
0070 36 64 65 65 32 35 65 64 - 33 64 30 0D 0A 56 69 61 6dee25ed3d0..Via
0080 3A 20 53 49 50 2F 32 2E - 30 2F 55 44 50 20 31 30 : SIP/2.0/UDP 10
0090 2E 32 34 2E 36 34 2E 31 - 38 3B 62 72 61 6E 63 68 .24.64.18;branch
00A0 3D 7A 39 68 47 34 62 4B - 2D 62 35 37 65 37 38 38 =z9hG4bK-b57e788
00B0 61 32 63 34 37 31 34 39 - 32 3B 72 70 6F 72 74 0D a2c471492;rport.
00C0 0A 46 72 6F 6D 3A 20 3C - 73 69 70 3A 70 61 63 6F .From: <sip:user1
00D0 40 31 39 32 2E 31 36 38 - 2E 31 2E 33 3A 35 30 36 @192.168.1.3:506
00E0 30 3E 3B 74 61 67 3D 31 - 63 31 30 35 39 34 0D 0A 0>;tag=1c10594..
00F0 54 6F 3A 20 3C 73 69 70 - 3A 61 6C 62 65 72 74 6F To: <sip:user2
0100 40 38 34 2E 37 37 2E 31 - 30 37 2E 31 33 39 3E 0D @84.77.107.136>.
0110 0A 43 61 6C 6C 2D 49 44 - 3A 20 73 5F 33 39 31 32 .Call-ID: s_3912
0120 30 30 30 32 5F 34 39 30 - 33 32 39 36 34 63 32 35 0002_49032964c25
0130 35 62 34 34 64 0D 0A 43 - 53 65 71 3A 20 32 39 35 5b44d..CSeq: 295
0140 31 36 20 49 4E 56 49 54 - 45 0D 0A 43 6F 6E 74 61 16 INVITE..Conta
0150 63 74 3A 20 3C 73 69 70 - 3A 70 61 63 6F 40 38 37 ct: <sip:user1@87
0160 2E 32 31 38 2E 31 31 2E - 34 36 3A 35 30 36 30 3E .218.11.46:5060>
0170 0D 0A 64 61 74 65 3A 20 - 54 68 75 2C 20 31 36 20 ..date: Thu, 16
0180 4E 6F 76 20 32 30 30 36 - 20 31 32 3A 33 30 3A 33 Nov 2006 12:30:3
0190 36 20 47 4D 54 0D 0A 6D - 61 78 2D 66 6F 72 77 61 6 GMT..max-forwa
01A0 72 64 73 3A 20 31 39 0D - 0A 75 73 65 72 2D 61 67 rds: 19..user-ag
01B0 65 6E 74 3A 20 73 69 70 - 58 2F 31 2E 33 2E 30 20 ent: sipX/1.3.0
01C0 28 57 69 6E 4E 54 29 0D - 0A 73 75 70 70 6F 72 74 (WinNT)..support
01D0 65 64 3A 20 72 65 70 6C - 61 63 65 73 0D 0A 41 6C ed: replaces..Al
01E0 6C 6F 77 3A 20 49 4E 56 - 49 54 45 2C 20 41 43 4B low: INVITE, ACK
01F0 2C 20 43 41 4E 43 45 4C - 2C 20 42 59 45 2C 20 52 , CANCEL, BYE, R
0200 45 46 45 52 2C 20 4F 50 - 54 49 4F 4E 53 2C 20 49 EFER, OPTIONS, I
0210 4E 46 4F 2C 20 52 45 47 - 49 53 54 45 52 2C 20 53 NFO, REGISTER, S
0220 55 42 53 43 52 49 42 45 - 2C 20 4E 4F 54 49 46 59 UBSCRIBE, NOTIFY
0230 0D 0A 43 6F 6E 74 65 6E - 74 2D 54 79 70 65 3A 20 ..Content-Type:
0240 61 70 70 6C 69 63 61 74 - 69 6F 6E 2F 73 64 70 0D application/sdp.
0250 0A 43 6F 6E 74 65 6E 74 - 2D 4C 65 6E 67 74 68 3A .Content-Length:
0260 20 32 30 32 30 32 0D 0A - 0D 0A 76 3D 30 0D 0A 6F 20202....v=0..o
0270 3D 73 69 70 58 20 35 20 - 35 20 49 4E 20 49 50 34 =sipX 5 5 IN IP4
0280 20 38 37 2E 32 31 38 2E - 31 31 2E 34 36 0D 0A 73 87.218.11.41..s
0290 3D 63 61 6C 6C 0D 0A 63 - 3D 49 4E 20 49 50 34 20 =call..c=IN IP4
02A0 38 37 2E 32 31 38 2E 31 - 31 2E 34 36 0D 0A 74 3D 87.218.11.41..t=
02B0 30 20 30 0D 0A 6D 3D 61 - 75 64 69 6F 20 37 30 37 0 0..m=audio 707
02C0 30 20 52 54 50 2F 41 56 - 50 20 30 20 38 20 39 36 0 RTP/AVP 0 8 96
02D0 0D 0A 61 3D 72 74 63 70 - 3A 31 36 30 30 32 0D 0A ..a=rtcp:16002..
02E0 61 3D 72 74 70 6D 61 70 - 3A 30 20 70 63 6D 75 2F a=rtpmap:0 pcmu/
02F0 38 30 30 30 2F 31 0D 0A - 61 3D 72 74 70 6D 61 70 8000/1..a=rtpmap
0300 3A 38 20 70 63 6D 61 2F - 38 30 30 30 2F 31 0D 0A :8 pcma/8000/1..
0310 61 3D 72 74 70 6D 61 70 - 3A 39 36 20 74 65 6C 65 a=rtpmap:96 tele
0320 70 68 6F 6E 65 2D 65 76 - 65 6E 74 2F 38 30 30 30 phone-event/8000
0330 2F 31 0D 0A &nbs p; &nbs p; &nbs p; &nbs p; /1..
************************************************************ *********************************
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 87.218.11.41:5060) >>>>
SIP/2.0 400 SIP Parse Error
Via: SIP/2.0/UDP 87.218.11.41:5060;branch=z9hG4bK9f406ef0c7f210b4c90046dee25e d3d0
From: <sip:user1@192.168.1.3:5060>;tag=1c10594
To: <sip:user2@84.77.107.136>
Call-ID: s_39120002_49032964c255b44d
CSeq: 29516 INVITE
Server: LanScape Centrex Proxy/3.41.1.1 (www.LanScapeCorp.com)
Content-Length: 0
#####################################################
#####################################################
#####################################################
I´ve sniffered user1´s machine and this is the INVITE SIP message sended:
INVITE sip:user2@84.77.107.136 SIP/2.0
From: <sip:user1@84.77.107.136:5060>;tag=1c10594
To: sip:user2@84.77.107.136
Call-Id: s_39120002_49032964c255b44d
Cseq: 29516 INVITE
Contact: <sip:user1@10.24.64.18>
Content-Type: application/sdp
Content-Length: 201
Date: Thu, 16 Nov 2006 12:30:36 GMT
Max-Forwards: 20
User-Agent: sipX/1.3.0 (WinNT)
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, INFO, REGISTER, SUBSCRIBE, NOTIFY
Supported: replaces
Via: SIP/2.0/UDP 10.24.64.18;branch=z9hG4bK-b57e788a2c471492;rport
v=0
o=sipX 5 5 IN IP4 10.24.64.18
s=call
c=IN IP4 10.24.64.18
t=0 0
m=audio 16001 RTP/AVP 0 8 96
a=rtcp:16002
a=rtpmap:0 pcmu/8000/1
a=rtpmap:8 pcma/8000/1
a=rtpmap:96 telephone-event/8000/1
user1 sends a INVITE SIP message with Content-Length = 201 and Centrex Proxy says that the Content-Length is 20202
What´s happenns?
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: November 16 2006 at 9:11am | IP Logged
|
|
|
hermes,
The INVITE message sent from user1 looks OK (The last INVITE message shown in your previous post).
The INVITE received by the LanScape Centrex proxy however is not the same INVITE and it does not appear to be coming directly from the user1 soft phone. I say this because the INVITE received at the LanScape proxy has 2 Via headers. 1 Via header from the original soft phone INVITE and another Via header from somewhere else.
In other words, the INVITE SIP message from your user1 soft phone appears to be coming from another proxy or "HOP".
The SIP messages that are logged by the LanScape proxy are received RAW SIP MESAGES that have not been inspected or processes by the LanScape proxy. To prove this, take your network sniffer software and capture the INVITE that is being received at the LanScape proxy host machine and compare it to what the LanScape proxy is logging. There should be no difference.
From your INVITE messages, this is what your test setup looks like to us:
Code:
user1
soft ---> some other ---> LanScape
phone proxy server??? Centrex Proxy
|
|
|
Whatever is "routing" the user1 INVITE message to the LanScape proxy is corrupting the "Content-Length:" SIP header of the INVITE. This is what you need to fix.
A few questions:
1)
Isn't SipX the open source PBX at the SipFoundary?
https://www.sipfoundry.org/sipX
2)
Are you trying to bridge 2 Sipx pbx nodes using our products?
3)
If you use the single or 2 line LanScape soft phones you have from the VOIP Media Engine product distribution, you should be able to configure a user1 and user2 LanScape soft phone to register with the LanScape Centrex proxy directly and make calls between user1 and user2 with no problems. Have you done this?
Note: for step 3, configure the LanScape Centrex proxy to use one media proxy.
4)
It appears that your single problem is the corrupt "Content-Length:" SIP header. If you fix this you should be OK.
5)
If you want, send an email to:
support 'at' lanscapecorp.com
and we will send you a beta proxy EXE that can be configured to ignore content length header errors.
Support
|
| Back to Top |
|
| |
|
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support
Topic: Register and INVITE problem - sipX
