History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XTRN-153
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Brad Marusiak
Reporter: Ashwini Madapatty
Votes: 0
Watchers: 1
Available Workflow Actions

Resolve
Request Information
Operations

If you were logged in you would be able to see more operations.
External

Polycom - Display name fails to get projected on phone TUI

Created: 2008-05-23 08:08   Updated: 2008-10-15 13: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: 1. File 0004f2104fa0-sipx-phone.cfg (5 kb)
2. File 0004f2104fa0-sipx-sip.cfg (150 kb)
3. GZip Archive sipx-configuration-mars.qantom.int.tar.gz (563 kb)

Image Attachments:

1. web_ui_displayname.JPG
(141 kb)
Environment:
sipxproxy 3.10.2-012712 2008-05-22T03:12:33 oem-centos5
  sipxconfig 3.10.2-012712 2008-05-22T03:24:25 oem-centos5
firmware version 3.0.0.0258


 Description  « Hide
Precondition: Register a Polycom phone with the user 603 to sipXchange

Steps to Reproduce:

1)Navigate to user identification page of the user 603 and update the Last name and First name .
     Last name : Software
     First name : Qantom
2) Click on Ok button
3) Projects the profiles for the phone.

Expected Result : The "displayName" ie last name and first name should be displayed on 603 phone TUI.

Actual Result : "displayName" is not displayed on the phone TUI .

Observation : 1) phone.cfg gets updated under tftp as
                         reg.1.displayName="qantom software"
                      2)gets updated in web Ui of the phone

Attachments:
                    1) Generated configuration files for the phone 603
                         0004f2104fa0-sipx-phone
                         0004f2104fa0-sipx-sip
                    2) web_ui_displayname screen shot
                    3)Snapshot :- sipx-configuration-mars.qantom.int.tar

Thanks
-Ashwini


 .

 All   Comments   Work Log   Change History      Sort Order:
Scott Lawrence - 2008-05-23 08:50
I've also seen a variation on this on my production (sipxchange.pingtel.com x162) Polycom in configuring speed dial buttons; I added several speed dials a couple of days ago, and the buttons are there but there are no names on them (pretty useless).

Damian Krzeminski - 2008-05-23 09:02
If it's in sipXconfig generated configuration and if it shows in phone WEB UI, the fact that is not displayed in phone TUI is a Polycom problem.

BTW: Scott's problem sounds unrelated to this.

Ashwini Madapatty - 2008-10-10 00:30
Verified the subjected issue on the following build with the Polycom phone's firmware version 3.1.0.0084 and it still continues to exists.

sipxproxy 3.11.6-013497 2008-09-23T21:40:12 oem-centos5
sipxconfig 3.11.6-013497 2008-09-23T21:52:01 oem-centos5


Thanks,
Ashwini

Chris Parfitt - 2008-10-15 09:07
Could you please re-test with the latest Polycom firmware and against the latest sane SCS500 2.5 build:Please close those issues that no longer exist and assign the others to Paul Mossman

Chris Parfitt - 2008-10-15 09:59
Verified the subjected issue on the following build with the Polycom phone's firmware version 3.1.0.0084 and it still continues to exists.

Paul Mossman - 2008-10-15 11:21
The Polycom Admin Guide has the following Interpretation of reg.x.displayName: "Display name used for local user interface as well as SIP signaling." This does seem to imply that the value should be seen on the TUI of the phone. We see only the "userPart" of the reg.x.address value, which does seem correct according to the Interpretation of reg.x.label.

Regarding reg.x.displayName, please clarify where in the "local user interface" this value should be observed.

Brad Marusiak - 2008-10-15 13:30
The only place I can find the "displayName" presented on the local UI is in the line status screen (Menu->status->lines->Line info...). Its possible this used to be shown in other locations and has since died off.

Label is really the configuration field the original reporter wanted to be using.

I will suggest that our documentation team amend the description of the displayName parameter to reflect the fact that it is really only used for sip signalling/caller ID.