[#XTRN-6] Call gets dropped for non digit user id in Polycom 2.1 Firmware -- Polycom 2.1firmware issue

External

Call gets dropped for non digit user id in Polycom 2.1 Firmware -- Polycom 2.1firmware issue

Created: 2007-06-12 08:55 Updated: 2008-09-16 16:34

Component/s:

Polycom - SoundPoint IP

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
File Attachments:	1. Polycom_2.1_Firmware.gz (764 kb)
Environment:	« Hide sipxpbx 3.8.0-010292 2007-06-08T17:38:02 eagle.pingtel.com sipxvxml 3.8.0-010292 2007-06-08T17:23:45 eagle.pingtel.com Show » sipxpbx 3.8.0-010292 2007-06-08T17:38:02 eagle.pingtel.com sipxvxml 3.8.0-010292 2007-06-08T17:23:45 eagle.pingtel.com

Description

« Hide

Precondition: Register 3 Polycom phones with user id 205 ,+207 and 239.

Steps :
1. Call phone +207 from phone 205(Polycom 1.6 ).
2. Call is established.
Callid=3216c89-79ffe33f-5f647f5c\@176.25.10.183
3. Call phone +207 from phone 239 (Polycom 2.1)
Callid=d9c25380-eae90f92-a7c53cf9\@176.25.10.180

Expected : Call should be established.

Actual : Call is dropped. The TO field is set to %2B207 in the logs. The registrar sends 404 Not Found message.

Attachment: Snap_shot

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Lih-Shyng Tzeng - 2007-06-12 21:59

Sangeetha, Does this problem only exist with Polycom 2.1.1 firmware? For example, does this problem exist with LG phones? I am trying to find out if this is a phone problem or a sipX problem. Thanks.

[ Permlink | « Hide ]

Sangeetha.R.S - 2007-06-14 01:45

This problem does not exist in LG and Snom phones. This seems to be a Polycom 2.1.1 firmware issue.

[ Permlink | « Hide ]

Dale R. Worley - 2008-02-29 14:43

The INVITEs as generated by the two phones are:

INVITE sip:+207@sipx-brblab.qantom.int SIP/2.0
From: "Sangeetha R.S" <sip:205@sipx-brblab.qantom.int>;tag=CF771A35-E47D5332
To: <sip:+207@sipx-brblab.qantom.int>
CSeq: 1 INVITE
Call-ID: 3216c89-79ffe33f-5f647f5c@176.25.10.183
Contact: <sip:205@176.25.10.183>
User-Agent: PolycomSoundPointIP-SPIP_301-UA/1.6.5.0043

INVITE sip:%2B207@sipx-brblab.qantom.int SIP/2.0
From: "A5 acd" <sip:239@sipx-brblab.qantom.int>;tag=22E98024-F7062F4B
To: <sip:%2B207@sipx-brblab.qantom.int>
CSeq: 1 INVITE
Call-ID: d9c25380-eae90f92-a7c53cf9@176.25.10.180
Contact: <sip:239@176.25.10.180>
User-Agent: PolycomSoundPointIP-SPIP_301-UA/2.1.0.2708

As you can see, the one from the 2.1 firmware escapes the '+' as '%2B'
(even though '+' is a legitimate character in a SIP URI user-part).
It looks like this is a problem with sipX, in that sipX should be
treating the two the same -- according to RFC 3261 section 19.1.4:
"Characters other than those in the "reserved" set (see RFC 2396 [5])
are equivalent to their ""%" HEX HEX" encoding."

I've been working on code improvements that will fix this problem.

But it is unlikely that other systems are not having problems with
this change to the phone's behavior, too.

[ Permlink | « Hide ]

Dale R. Worley - 2008-02-29 14:43

Can yout test this with Polycom firmware 2.2 to see if it is still a problem?

[ Permlink | « Hide ]

Dale R. Worley - 2008-03-07 16:24

I just tested 2.2.0.0047 and it shows this problem.

[ Permlink | « Hide ]

Akshata Saralaya - 2008-03-26 06:53

This issue still exist.
Verified with polycom 2.2.2.0084 firmware
with build,
sipxproxy 3.10.0-012086 2008-03-19T23:28:54 oem-centos5
sipxconfig 3.10.0-012086 2008-03-20T00:03:36 oem-centos5

Thanks,
Akshata

[ Permlink | « Hide ]

Ashwini Madapatty - 2008-05-26 07:31

Verified the issue on the following build with the polycom phone (3.0.0.0258 firmware version),The issue still exist's .
sipxproxy 3.10.2-012712 2008-05-22T03:12:33 oem-centos5
sipxconfig 3.10.2-012712 2008-05-22T03:24:25 oem-centos5

Thanks
-Ashwini

[ Permlink | « Hide ]

Aaron Brumpton - 2008-09-16 16:34

You should find this is resolved in Polycom 3.1.0. Please retest.