LanScape Support Forum: Communication problem (Part 2)

		Active Topics Member List Search Help Register Login

SIP Proxy and Media Proxy - Pre-Sales Technical Support
LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support

Topic: Communication problem (Part 2)

Author

Message

<< Prev Topic | Next Topic >>

vocdev
Intermediate

Joined: September 25 2006
Posts: 3

Posted: October 04 2006 at 3:31am \| IP Logged

Hello,

I´ve installed Centrex Sip Proxy Server and Sip Media Server trial version in the same machine in a private network. In the same private network I´ve got a Sip Software Phone (Phone A).
When I make a call from 'Phone A' to other phone placed in public network (Phone B) it works successful; but when I tried to make a call from 'Phone B' to 'Phone A', Centrex Proxy Server said: "Error parsing received SIP protocol packet from 87.218.10.196:5060 Possibly non-compliant SIP message".

These phones are software phones, but I´ve tried hardware phones too and other software phones with the same result.

I´ve redirected these ports to Proxy´s machine: 5060, 16000, 16001 and 16002.

What´s is the problem?

These are the logs:

VoipMediaProxy.log
=============
#Rec#2#10:00:24 10/04/06#***************************** VOIP Media Proxy Session Start *****************************
#Rec#2#10:00:24 10/04/06#VOIP Media Proxy® Starting...
#Rec#2#10:00:24 10/04/06#Initializing control Port 16000...
#Rec#2#10:00:24 10/04/06#Initializing Media Ports 16001-16002...
#Rec#2#10:00:24 10/04/06#Initializing address information for SIP Proxy "192.168.1.41", (192.168.1.41:5020).
#Rec#2#10:00:25 10/04/06#Communications with SIP Proxy 192.168.1.41:5020 has been established.
#Rec#2#10:00:25 10/04/06#Media session monitor started.
#Rec#2#10:00:25 10/04/06#VOIP Media Proxy® Ready

CentrexProxyEventLog.log
==================
#Rec#2#10:00:22 10/04/06#***************************** Proxy Session Start *****************************
#Rec#2#10:00:22 10/04/06#LanScape Centrex Proxy® Starting...
#Rec#2#10:00:22 10/04/06#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#10:00:22 10/04/06#Server Name: LanScape Corporation, LanScape Centrex Proxy/3.41
#Rec#2#10:00:22 10/04/06#Private IP: 192.168.1.41
#Rec#2#10:00:22 10/04/06#WAN IP: 84.77.96.41
#Rec#2#10:00:22 10/04/06#Server Port: 5060
#Rec#2#10:00:22 10/04/06#Domain: MyCompany.com
#Rec#2#10:00:22 10/04/06#Authentication: on
#Rec#2#10:00:22 10/04/06#Authentication Realm: MyCompany.com
#Rec#2#10:00:22 10/04/06#Initializing local authentication database.
#Rec#2#10:00:22 10/04/06#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#10:00:22 10/04/06#Call Routing: DISABLED
#Rec#2#10:00:22 10/04/06#Initializing control Port 5020...
#Rec#2#10:00:22 10/04/06#Media Proxy support started. Using control port 5020.
#Rec#2#10:00:22 10/04/06#Proxy Ready
#Rec#2#10:00:24 10/04/06#VOIP Media Proxy 192.168.1.41:16000 is on-line.
#Rec#8#10:00:33 10/04/06#REGISTER paco@192.168.1.43:5060 (5000 sec)    Received from: 192.168.1.43:5060    Registering UA/Contact: 192.168.1.43:5060
#Rec#8#10:00:38 10/04/06#REGISTER alberto@87.218.10.196:5060 (5000 sec)    Received from: 87.218.10.196:5060    Registering UA/Contact: 87.218.10.196:5060
#Rec#0#10:00:46 10/04/06#Error parsing received SIP protocol packet from 87.218.10.196:5060. Possibly non-compliant SIP message.
#Rec#0#10:00:48 10/04/06#Error parsing received SIP protocol packet from 87.218.10.196:5060. Possibly non-compliant SIP message.

CentrexProxySipLog.log
================
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.43:5060) <<<<
REGISTER sip:192.168.1.41 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060
From: paco <sip:paco@192.168.1.41>
To: paco <sip:paco@192.168.1.41>
Call-ID: 23852ff5-25807-45236a59@192.168.1.41
CSeq: 5 REGISTER
Contact: "paco" <sip:paco@192.168.1.43:5060>
User-Agent: VaxSIPUserAgent/2.0
Expires: 5000
Max-Forwards: 70
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.43:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;received=192.168.1.43;wanip=84. 77.96.41
From: paco <sip:paco@192.168.1.41>
To: paco <sip:paco@192.168.1.41>
Call-ID: 23852ff5-25807-45236a59@192.168.1.41
CSeq: 5 REGISTER
WWW-Authenticate: Digest realm="MyCompany.com", nonce="782b1e4db74da8aa162a491f358ca50a", opaque="55ca72d9d0dc8b05e1bf363aed709bbf"
Server: LanScape Centrex Proxy/3.41 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.43:5060) <<<<
REGISTER sip:192.168.1.41 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.43:5060
From: paco <sip:paco@192.168.1.41>
To: paco <sip:paco@192.168.1.41>
Call-ID: 23852ff5-25807-45236a59@192.168.1.41
CSeq: 6 REGISTER
Contact: "paco" <sip:paco@192.168.1.43:5060>
Authorization: Digest username="paco", realm="MyCompany.com", nonce="782b1e4db74da8aa162a491f358ca50a", uri="sip:192.168.1.41", response="aab19e55c9c636a0d786ec09b3891dc5", algorithm=MD5, opaque="55ca72d9d0dc8b05e1bf363aed709bbf"
User-Agent: VaxSIPUserAgent/2.0
Expires: 5000
Max-Forwards: 70
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.43:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.43:5060;rport=5060;received=192.168.1.43;wanip=84. 77.96.41
From: paco <sip:paco@192.168.1.41>
To: paco <sip:paco@192.168.1.41>;tag=41
Call-ID: 23852ff5-25807-45236a59@192.168.1.41
CSeq: 6 REGISTER
Contact: "paco" <sip:paco@192.168.1.43:5060>;expires=5000
Expires: 5000
Server: LanScape Centrex Proxy/3.41 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 87.218.10.196:5060) <<<<
REGISTER sip:84.77.96.41 SIP/2.0
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bKc8ab7338e15d95b6915746d1dda 9c44c
Via: SIP/2.0/UDP 10.24.64.3:5060
From: alberto <sip:alberto@84.77.96.41>
To: alberto <sip:alberto@84.77.96.41>
Call-ID: 365ba6-75814-45236a5d@84.77.96.41
CSeq: 17 REGISTER
Contact: "alberto" <sip:alberto@87.218.10.196>
user-agent: VaxSIPUserAgent/2.0
expires: 5000
max-forwards: 69
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 87.218.10.196:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bKc8ab7338e15d95b6915746d1dda 9c44c;rport=5060;received=87.218.10.196
Via: SIP/2.0/UDP 10.24.64.3:5060
From: alberto <sip:alberto@84.77.96.41>
To: alberto <sip:alberto@84.77.96.41>
Call-ID: 365ba6-75814-45236a5d@84.77.96.41
CSeq: 17 REGISTER
WWW-Authenticate: Digest realm="MyCompany.com", nonce="782b1e4db74da8aa162a491f358ca50a", opaque="cc42f7b7feb709ced87597d1a718797c"
Server: LanScape Centrex Proxy/3.41 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 87.218.10.196:5060) <<<<
REGISTER sip:84.77.96.41 SIP/2.0
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bK89b1405d95dbf9992c35f53cc21 fea86
Via: SIP/2.0/UDP 10.24.64.3:5060
From: alberto <sip:alberto@84.77.96.41>
To: alberto <sip:alberto@84.77.96.41>
Call-ID: 365ba6-75814-45236a5d@84.77.96.41
CSeq: 18 REGISTER
Contact: "alberto" <sip:alberto@87.218.10.196>
Authorization: Digest username="alberto", realm="MyCompany.com", nonce="782b1e4db74da8aa162a491f358ca50a", uri="sip:84.77.96.41", response="edb30db4031ab3b1c26612ad00a16585", algorithm=MD5, opaque="cc42f7b7feb709ced87597d1a718797c"
user-agent: VaxSIPUserAgent/2.0
expires: 5000
max-forwards: 69
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 87.218.10.196:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bK89b1405d95dbf9992c35f53cc21 fea86;rport=5060;received=87.218.10.196
Via: SIP/2.0/UDP 10.24.64.3:5060
From: alberto <sip:alberto@84.77.96.41>
To: alberto <sip:alberto@84.77.96.41>;tag=18467
Call-ID: 365ba6-75814-45236a5d@84.77.96.41
CSeq: 18 REGISTER
Contact: "alberto" <sip:alberto@87.218.10.196>;expires=5000
Expires: 5000
Server: LanScape Centrex Proxy/3.41 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 87.218.10.196:5060) <<<<
INVITE sip:paco@84.77.96.41 SIP/2.0
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bKe88dd7ca95aa821f99a71b8bf13 6f7dc
Via: SIP/2.0/UDP 10.24.64.3:5060
From: alberto <sip:alberto@84.77.96.41>;tag=536d258
To: <sip:paco@84.77.96.41>
Call-ID: 367a2a-8582e-45236a65@10.24.64.3
CSeq: 592 INVITE
Contact: <sip:alberto@87.218.10.196>
subject: no subject
user-agent: VaxSIPUserAgent/2.0
max-forwards: 69
Allow: ACK, INFO, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER
Content-Type: application/sdp
Content-Length: 28383

v=0
o=alberto 11599489016 11599489016 IN IP4 87.218.10.196
s=VaxSoft Inc.
c=IN IP4 87.218.10.196
t=0 0
m=audio 7070 RTP/AVP 3 98 8 0 101
a=rtpmap:3 GSM/8000
a=rtpmap:98 iLBC/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16

****** Error: Last SIP message could not be parsed. Hex dump follows ***** (From: 87.218.10.196:5060) <<<<

0000 49 4E 56 49 54 45 20 73 - 69 70 3A 70 61 63 6F 40     INVITE sip:paco@
0010 38 34 2E 37 37 2E 39 36 - 2E 34 31 20 53 49 50 2F     84.77.96.41 SIP/
0020 32 2E 30 0D 0A 56 69 61 - 3A 20 53 49 50 2F 32 2E     2.0..Via: SIP/2.
0030 30 2F 55 44 50 20 38 37 - 2E 32 31 38 2E 31 30 2E     0/UDP 87.218.10.
0040 31 39 38 3A 35 30 36 30 - 3B 62 72 61 6E 63 68 3D     198:5060;branch=
0050 7A 39 68 47 34 62 4B 65 - 38 38 64 64 37 63 61 39     z9hG4bKe88dd7ca9
0060 35 61 61 38 32 31 66 39 - 39 61 37 31 62 38 62 66     5aa821f99a71b8bf
0070 31 33 36 66 37 64 63 0D - 0A 56 69 61 3A 20 53 49     136f7dc..Via: SI
0080 50 2F 32 2E 30 2F 55 44 - 50 20 31 30 2E 32 34 2E     P/2.0/UDP 10.24.
0090 36 34 2E 33 3A 35 30 36 - 30 0D 0A 46 72 6F 6D 3A     64.3:5060..From:
00A0 20 61 6C 62 65 72 74 6F - 20 3C 73 69 70 3A 61 6C      alberto <sip:al
00B0 62 65 72 74 6F 40 38 34 - 2E 37 37 2E 39 36 2E 34     berto@84.77.96.4
00C0 31 3E 3B 74 61 67 3D 35 - 33 36 64 32 35 38 0D 0A     1>;tag=536d258..
00D0 54 6F 3A 20 3C 73 69 70 - 3A 70 61 63 6F 40 38 34     To: <sip:paco@84
00E0 2E 37 37 2E 39 36 2E 34 - 31 3E 0D 0A 43 61 6C 6C     .77.96.41>..Call
00F0 2D 49 44 3A 20 33 36 37 - 61 32 61 2D 38 35 38 32     -ID: 367a2a-8582
0100 65 2D 34 35 32 33 36 61 - 36 35 40 31 30 2E 32 34     e-45236a65@10.24
0110 2E 36 34 2E 33 0D 0A 43 - 53 65 71 3A 20 35 39 32     .64.3..CSeq: 592
0120 20 49 4E 56 49 54 45 0D - 0A 43 6F 6E 74 61 63 74      INVITE..Contact
0130 3A 20 3C 73 69 70 3A 61 - 6C 62 65 72 74 6F 40 38     : <sip:alberto@8
0140 37 2E 32 31 38 2E 31 30 - 2E 31 39 38 3E 0D 0A 73     7.218.10.198>..s
0150 75 62 6A 65 63 74 3A 20 - 6E 6F 20 73 75 62 6A 65     ubject: no subje
0160 63 74 0D 0A 75 73 65 72 - 2D 61 67 65 6E 74 3A 20     ct..user-agent:
0170 56 61 78 53 49 50 55 73 - 65 72 41 67 65 6E 74 2F     VaxSIPUserAgent/
0180 32 2E 30 0D 0A 6D 61 78 - 2D 66 6F 72 77 61 72 64     2.0..max-forward
0190 73 3A 20 36 39 0D 0A 41 - 6C 6C 6F 77 3A 20 41 43     s: 69..Allow: AC
01A0 4B 2C 20 49 4E 46 4F 2C - 20 42 59 45 2C 20 43 41     K, INFO, BYE, CA
01B0 4E 43 45 4C 2C 20 49 4E - 56 49 54 45 2C 20 4E 4F     NCEL, INVITE, NO
01C0 54 49 46 59 2C 20 4F 50 - 54 49 4F 4E 53 2C 20 52     TIFY, OPTIONS, R
01D0 45 46 45 52 2C 20 52 45 - 47 49 53 54 45 52 0D 0A     EFER, REGISTER..
01E0 43 6F 6E 74 65 6E 74 2D - 54 79 70 65 3A 20 61 70     Content-Type: ap
01F0 70 6C 69 63 61 74 69 6F - 6E 2F 73 64 70 0D 0A 43     plication/sdp..C
0200 6F 6E 74 65 6E 74 2D 4C - 65 6E 67 74 68 3A 20 32     ontent-Length: 2
0210 38 33 38 33 0D 0A 0D 0A - 76 3D 30 0D 0A 6F 3D 61     8383....v=0..o=a
0220 6C 62 65 72 74 6F 20 31 - 31 35 39 39 34 38 39 30     lberto 115994890
0230 31 36 20 31 31 35 39 39 - 34 38 39 30 31 36 20 49     16 11599489016 I
0240 4E 20 49 50 34 20 38 37 - 2E 32 31 38 2E 31 30 2E     N IP4 87.218.10.
0250 31 39 38 0D 0A 73 3D 56 - 61 78 53 6F 66 74 20 49     198..s=VaxSoft I
0260 6E 63 2E 0D 0A 63 3D 49 - 4E 20 49 50 34 20 38 37     nc...c=IN IP4 87
0270 2E 32 31 38 2E 31 30 2E - 31 39 38 0D 0A 74 3D 30     .218.10.198..t=0
0280 20 30 0D 0A 6D 3D 61 75 - 64 69 6F 20 37 30 37 30      0..m=audio 7070
0290 20 52 54 50 2F 41 56 50 - 20 33 20 39 38 20 38 20      RTP/AVP 3 98 8
02A0 30 20 31 30 31 0D 0A 61 - 3D 72 74 70 6D 61 70 3A     0 101..a=rtpmap:
02B0 33 20 47 53 4D 2F 38 30 - 30 30 0D 0A 61 3D 72 74     3 GSM/8000..a=rt
02C0 70 6D 61 70 3A 39 38 20 - 69 4C 42 43 2F 38 30 30     pmap:98 iLBC/800
02D0 30 0D 0A 61 3D 72 74 70 - 6D 61 70 3A 38 20 50 43     0..a=rtpmap:8 PC
02E0 4D 41 2F 38 30 30 30 0D - 0A 61 3D 72 74 70 6D 61     MA/8000..a=rtpma
02F0 70 3A 30 20 50 43 4D 55 - 2F 38 30 30 30 0D 0A 61     p:0 PCMU/8000..a
0300 3D 72 74 70 6D 61 70 3A - 31 30 31 20 74 65 6C 65     =rtpmap:101 tele
0310 70 68 6F 6E 65 2D 65 76 - 65 6E 74 2F 38 30 30 30     phone-event/8000
0320 0D 0A 61 3D 66 6D 74 70 - 3A 31 30 31 20 30 2D 31     ..a=fmtp:101 0-1
0330 36 0D 0A        &nbs p;        &nbs p;        &nbs p;        &nbs p;      6..

************************************************************ *********************************

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 87.218.10.196:5060) >>>>
SIP/2.0 400 SIP Parse Error
Via: SIP/2.0/UDP 87.218.10.196:5060;branch=z9hG4bKe88dd7ca95aa821f99a71b8bf13 6f7dc
From: alberto <sip:alberto@84.77.96.41>;tag=536d258
To: <sip:paco@84.77.96.41>
Call-ID: 367a2a-8582e-45236a65@10.24.64.3
CSeq: 592 INVITE
Server: LanScape Centrex Proxy/3.41 (www.LanScapeCorp.com)
Content-Length: 0

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: October 04 2006 at 8:38am \| IP Logged

Hi vocdev,

We will take a look at the logs and reply. Problems of this type are generally resolved quickly.

Support.

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: October 04 2006 at 9:31am \| IP Logged

Hi vocdev,

In your SIP log, the user agent reports as:

Code:

user-agent: VaxSIPUserAgent/2.0

Is this the VaxVOIP SDK or some other?

Support

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: October 04 2006 at 10:15am \| IP Logged

vocdev,

Thanks for your post.

We have isolated the cause of your SIP proxy parse error. If you look at the INVITE message your “VaxSIPUserAgent/2.0” client sends to the Centrex Proxy server, it specifies a SIP content header as follows:

Content-Length: 28383

The problem is that the “body” of the SIP INVITE message is not 28,383 bytes. Your SIP client is not formatting the SIP message properly and the Centrex proxy thinks that it has not received the full content of the INVITE SIP message – thus the error. Your SIP client should be setting the content header to be 285 bytes like this:

Content-Length: 285

Here is the “body” of your INVITE message:

Code:

v=0

o=alberto 11599489016 11599489016 IN IP4 87.218.10.196

s=VaxSoft Inc.

c=IN IP4 87.218.10.196

t=0 0

m=audio 7070 RTP/AVP 3 98 8 0 101

a=rtpmap:3 GSM/8000

a=rtpmap:98 iLBC/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

So your SIP client has a bug.

If you really need to use the SIP client you are currently testing with, then we can allow our Centrex proxy server to accept bad content length headers (as a configuration option) but we can only create this custom release for you if you purchase a normal product license.

Repost as required.

Support

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

Printable version

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