[#XTRN-168] PhoneEasy does not show "Call Waiting" for dialog-info state="partial" NOTIFYs

External

PhoneEasy does not show "Call Waiting" for dialog-info state="partial" NOTIFYs

Created: 2008-06-05 20:39 Updated: 2008-10-09 10:41

Component/s:

AdvaTel - PhoneEasy

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
File Attachments:	1. polycom_call_wait_NOTIFY_failure.pcap (22 kb)
Environment:	« Hide Polycom SoundPoint IP 601 Application SIP v 2.1.2.0078 registrar: SCS500 Release 2 Show » Polycom SoundPoint IP 601 Application SIP v 2.1.2.0078 registrar: SCS500 Release 2

Description

« Hide

The Polycom does not send information about ALL the calls at the UA, only the most recent activity.
This leads to two problems: other UAs are not able to display the Polycom in Call Waiting state. If the second call abandons the call, the Polycom appears to be idle when there is in fact an established call.

In the attached trace:
Polycom is 1665
Two LG-Nortel 68XX are 1663 & 1664
Other UA is 1662, SUBSCRIBEd to 1665 - Polycom

From 1663 (LG) call the Polycom and answer the call.
NOTIFY is correct.

From 1664 (other LG) dial the Polycom
Notify only contains information about this latest call.

Abandon this second call at the LG
Notify only contains information (terminated DIALOG) about this latest call - therefore Polycom appears idle.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brad Marusiak - 2008-08-15 16:12

Polycom Reference ID: VOIP-45164

[ Permlink | « Hide ]

Aaron Brumpton - 2008-09-03 14:25

Should the sipXrls not be consolidating the dialog documents for the BLF subscriber

[ Permlink | « Hide ]

Paul Mossman - 2008-09-12 14:55

Polycom Position: "This behavior is by design. We are looking through the RFC's and specs to determine if this can be construed as incorrect behavior. Our guess is that there is no reason to have to consolidate all BLF information when a single line changes state as it should be the server that takes the new information and propagates the completed list to the attending phone. We believe this behavior can be rectified by server or 'non-Polycom' end-point changes."

I agree with the Polycom's position. The Polycom NOTIFY dialog-info element's state attribute is "partial", so it does not claim to be a "full" list of all active dialogs, as Advatel PhoneEasy seems to be assuming. However sipXrls is able consolidate "partial" NOTIFYs from UAs it is subscribed to, into "full" NOTIFYs when distributed to subscribers. But, in order to get this you need to subscribe to the Consolidated (or "Broadworks") format Resource List URI: ~~rl~[NNN]c@[DOMAIN]. (See http://sipx-wiki.calivia.com/index.php/HowTo_manually_configure_BLF_in_a_phone)

I've tested this and confirmed that using the Consolidated Resource List URI, Advatel PhoneEasy is able to show "Call Waiting" BLF indication for Polycom SoundPoint IP phones.