[#XTRN-9] RLS - Polycom rev. 2.1 does not always report status changes

External

RLS - Polycom rev. 2.1 does not always report status changes

Created: 2007-03-16 17:19 Updated: 2008-10-08 14:30

Component/s:

Polycom - SoundPoint IP

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

merged.xml (542 kb)
2.

merged2.xml (306 kb)
3.

Polycom1.pcap (343 kb)
4.

Polycom1.txt (0.5 kb)
5.

testplan (4 kb)

Environment:

Polycom rev. 2.1

Issue Links:

Duplicate

This issue also reported as:
	~~XPB-943~~ Report Polycom problem: Apparently o...

Description

« Hide

Under some circumstances, the Polycom rev. 2.1 firmware will not generate a NOTIFY for changes in its dialog state.

I can reproduce this consistently using the test setup in the attached file "testplan". The test starts "Call from A:201; Call to 202; Answer on: wait for 212 to ring...". The observed symptom is that after the call is established (between lines 201 and 212), the BLF light for 201 does not light. The siptrace is attached as merged.xml. Toward the end of the siptrace, you can see at frame 416 a 200 OK arrives, making the dialog confirmed. But the phone does not send a NOTIFY for the RLS's subscription. (The subscription was previously working correctly -- see frame 369.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dale R. Worley - 2007-03-19 10:51

I just retested this: Reboot sipX and the phones, then execute the test call. The 201 BLF did not light.

[ Permlink | « Hide ]

Dale R. Worley - 2007-03-19 13:20

Another example of this failure is in the siptrace file merge2.xml. This was another attempt at the stress test and 201 didn't light at all.

[ Permlink | « Hide ]

Dale R. Worley - 2007-03-26 15:17

Attachments Polycom1.txt and Polycom1.pcap describe a simple test case Polycom should be able to reproduce.

[ Permlink | « Hide ]

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

I just retested this with firmware version 2.2.0.0047 and I still see the problem. The test was the one documented in Polycom1.txt, except that the phone had only one line appearance.

[ Permlink | « Hide ]

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

Firmware version 2.2.2.0084 fails the same test as in the previous comment.

[ Permlink | « Hide ]

Michael Haag - 2008-05-12 11:32

Dale, can you run this test case against Polycom 3.0 firmware? (I think support for Polycom 3.0 has been checked into the mainline trunk - Damian would know for sure).

Also, have you tried configuring the Polycom to use TCP and then tested this case?

[ Permlink | « Hide ]

Paul Mossman - 2008-10-08 14:30

Much improved with 3.1.0 firmware. Any open issues are being tracked individually.