SIPfoundry Issue Tracker

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options
    • Planning Board
    • Task Board
    • Chart Board
    • Released Board
    • Rapid Board
    • Manage Rapid Boards
    • Getting Started
  • sipXecs
  • XX-485

Polycom IP650 w/ sidecar: After configuring 18 speeddial entries w/ BLF none show up on the phone

  • Rapid Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 3.10.2
  • Component/s: None
  • Labels:
    None
  • Environment:
    Polycom firmware 2.2.2.0084

Description

Polycom IP650 phone w/ one sidecar. The phone has one line configured.

Case 1: Configured 18 speeddial entries using the user portal. They all have BLF enabled. After rebooting the phone no speeddial entries are visible on the phone. Only the registered line is there.

Case 2: Reduced the number of speeddial entries to 14. After rebooting they display correctly on the phone

Case 3: Added two more for a total of 16. Again, none display on the phone

Case 4: 15 speeddial entries -> No speeddial are displayed

Case 5: Reduced the number of entries down to 8 and still do not get any to display,

I noticed that the behavior can be quite erratic where sometimes speeddial entries are displayed and sometimes not. With only one registered line the phone allows a maximum of 19 speeddial positions. Limits should be enforced if there are such limits. Once the user configures speeddial on the user portal the expectation is that they show up after the phone restarts, but they do not do that consistently,
  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. File
    0004f21515f0-sipx-phone.cfg
    2008-04-01 10:42
    13 kB
    Damian Krzeminski
  2. File
    0004f21515f0-sipx-sip.cfg
    2008-04-01 10:42
    147 kB
    Damian Krzeminski
  3. GZip Archive
    sipx-configuration.tar.gz
    2008-04-01 10:42
    660 kB
    Damian Krzeminski

Issue Links

depends on

Bug - A problem which impairs or prevents the functions of the product. XX-465 Incoming RLS SUBSCRIBEs have request-URI sip:[ext]@[host name/addr]:[port] rather than sip:[ext]@[domain]

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
has part

Bug - A problem which impairs or prevents the functions of the product. XX-475 Remove fixed limit on number of Mime multipart body parts

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. XX-487 Try TCP first for large messages

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
related to

Bug - A problem which impairs or prevents the functions of the product. XX-271 Monitoring the Call Park Ext on Polycom phone buttons does not show parked call

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Bug - A problem which impairs or prevents the functions of the product. XX-2615 Polycom: enabling Presence (BLF) for speed dial entry causes disorder in other sped dial entries

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Damian Krzeminski added a comment - 2008-03-31 16:25
The BLF functionality is implemented by configuring Resource List Server (/etc/sipxpbx/resource-lists.xml).
Please attach a snapshot. It'll make possible to determine if the problems are related to sipXconfig generating incorrect file or some issues between sipXrls and the Polycom phone.
If possible attach files configuration profile of the phone generated by sipXconfig as well.
Show
Damian Krzeminski added a comment - 2008-03-31 16:25 The BLF functionality is implemented by configuring Resource List Server (/etc/sipxpbx/resource-lists.xml). Please attach a snapshot. It'll make possible to determine if the problems are related to sipXconfig generating incorrect file or some issues between sipXrls and the Polycom phone. If possible attach files configuration profile of the phone generated by sipXconfig as well.
Hide
Permalink
Damian Krzeminski added a comment - 2008-04-01 10:43
I attached files e-mailed by Mike.
Show
Damian Krzeminski added a comment - 2008-04-01 10:43 I attached files e-mailed by Mike.
Hide
Permalink
Martin Steinnman2 added a comment - 2008-04-01 10:49
The attached files were taken with 8 speed dial entries defined for this phone all with BLF enabled. The phone does not display any speed dial entries after rebooting with this config.
Show
Martin Steinnman2 added a comment - 2008-04-01 10:49 The attached files were taken with 8 speed dial entries defined for this phone all with BLF enabled. The phone does not display any speed dial entries after rebooting with this config.
Hide
Permalink
Damian Krzeminski added a comment - 2008-04-01 10:52
Configuration appears to be correct:

/0004f21515f0-sipx-phone.cfg: <attendant attendant.uri="sip:~~rl~1268c@pingtel.com" attendant.reg="1"/>

And resource-list.xml contains ressource list identified by '~~rl~1268' which corresponds to the list of contacts configured in sipXconfig UI.

It appears to be an issues between Polycom and sipXrls: moving to sipXecs for further investigation.

Show
Damian Krzeminski added a comment - 2008-04-01 10:52 Configuration appears to be correct: /0004f21515f0-sipx-phone.cfg: <attendant attendant.uri="sip:~~rl~1268c@pingtel.com" attendant.reg="1"/> And resource-list.xml contains ressource list identified by '~~rl~1268' which corresponds to the list of contacts configured in sipXconfig UI. It appears to be an issues between Polycom and sipXrls: moving to sipXecs for further investigation.
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2008-04-03 22:02
Dale, Please take a look at this. Thanks.
Show
Lih-Shyng Tzeng added a comment - 2008-04-03 22:02 Dale, Please take a look at this. Thanks.
Hide
Permalink
Dale Worley added a comment - 2008-04-11 17:40
Martin writes in XECS-1313:

Martin Steinmann - 2008-04-11 15:56

After updating the software on our production system I tried this again. I assigned 18 speed dial entries for my IP650 phone with side car. After rebooting no speed dial entries were shown. Today at 4:52pm. I then reduced the number of speed dial entries to 14 and after rebooting still no speed dial entries displayed (today at 4:55pm).

Martin Steinmann - 2008-04-11 16:00

then picked 13 speed dial entries and after reboot they showed up on the phone (hurray). Today at 5pm. This can be coincidental though and I would claim that this anything to do with the number of entries.
Show
Dale Worley added a comment - 2008-04-11 17:40 Martin writes in XECS-1313: Martin Steinmann - 2008-04-11 15:56 After updating the software on our production system I tried this again. I assigned 18 speed dial entries for my IP650 phone with side car. After rebooting no speed dial entries were shown. Today at 4:52pm. I then reduced the number of speed dial entries to 14 and after rebooting still no speed dial entries displayed (today at 4:55pm). Martin Steinmann - 2008-04-11 16:00 then picked 13 speed dial entries and after reboot they showed up on the phone (hurray). Today at 5pm. This can be coincidental though and I would claim that this anything to do with the number of entries.
Hide
Permalink
Dale Worley added a comment - 2008-04-25 09:56
The Polycom UDP packet size limitation (XECS-1383) contributes to these symptoms.
Show
Dale Worley added a comment - 2008-04-25 09:56 The Polycom UDP packet size limitation (XECS-1383) contributes to these symptoms.
Hide
Permalink
Dale Worley added a comment - 2008-04-25 09:58
The limitation on the number of MIME multiparts (XECS-1360) contributes to these symptoms.
Show
Dale Worley added a comment - 2008-04-25 09:58 The limitation on the number of MIME multiparts (XECS-1360) contributes to these symptoms.
Hide
Permalink
Dale Worley added a comment - 2008-05-07 13:51
Issue XECS-1360 generates some of these problems. The "Polycom UDP packet size limitation" generates other instances of this problem. The latter is being addressed in XECS-1383. I think that accounts for all observed absences of BLF indicators.

It would also be desirable in the Config Server to prevent (or at least warn) when an attempt is made to add more BLFs than can be displayed on a phone. (This can also be triggered by adding a line to a phone that is displaying the maximum.) However, with the Polycom sidecar system, the room available for BLFs cannot be predicted (and it can change any time the phone is restarted). Worse, there can be more than one phone for a single extension number, and different phones can have different limits. What limit would we enforce? -- So I am going to leave this limit problem unfixed because there is no solution that is not more confusing than the current situation.
Show
Dale Worley added a comment - 2008-05-07 13:51 Issue XECS-1360 generates some of these problems. The "Polycom UDP packet size limitation" generates other instances of this problem. The latter is being addressed in XECS-1383. I think that accounts for all observed absences of BLF indicators. It would also be desirable in the Config Server to prevent (or at least warn) when an attempt is made to add more BLFs than can be displayed on a phone. (This can also be triggered by adding a line to a phone that is displaying the maximum.) However, with the Polycom sidecar system, the room available for BLFs cannot be predicted (and it can change any time the phone is restarted). Worse, there can be more than one phone for a single extension number, and different phones can have different limits. What limit would we enforce? -- So I am going to leave this limit problem unfixed because there is no solution that is not more confusing than the current situation.
Hide
Permalink
Dale Worley added a comment - 2008-05-19 14:20
Now that XECS-1383 is fixed on 3.10.2 and 4.0, all of the known fundamental errors that contribute to this issue are fixed in both versions. I'm marking this resolved and sending it back to Martin to test once the production system is upgraded to 3.10.2.
Show
Dale Worley added a comment - 2008-05-19 14:20 Now that XECS-1383 is fixed on 3.10.2 and 4.0, all of the known fundamental errors that contribute to this issue are fixed in both versions. I'm marking this resolved and sending it back to Martin to test once the production system is upgraded to 3.10.2.
Hide
Permalink
Anushree Ganguly added a comment - 2008-05-21 06:52 - edited
This issue is resolved .Verified in the build 3.10.2-012682
901 is a Polycom 650 phone with a sidecar.I have added 18 speed dial entries and subscribed it to presence.On rebooting, the first five BLF entries are displayed in the Polycom 650 device and the other 13 entries in the sidecar.On making any BLF user busy ,the respective LED in the sidecar/device starts glowing.
I verified the same by adding 8 speed dial entries.It is working fine.
Show
Anushree Ganguly added a comment - 2008-05-21 06:52 - edited This issue is resolved .Verified in the build 3.10.2-012682 901 is a Polycom 650 phone with a sidecar.I have added 18 speed dial entries and subscribed it to presence.On rebooting, the first five BLF entries are displayed in the Polycom 650 device and the other 13 entries in the sidecar.On making any BLF user busy ,the respective LED in the sidecar/device starts glowing. I verified the same by adding 8 speed dial entries.It is working fine.
Hide
Permalink
Ananda Teertha added a comment - 2008-06-02 08:10


The issue is resolved, verified on the following build

 sipxproxy 3.10.2-012798 2008-06-02T00:34:29 oem-centos5
  sipxconfig 3.10.2-012798 2008-06-02T00:45:33 oem-centos5

Steps followed.

1)Registered polycom 650 with the sidecar phone with the user 901.
2)Added 18 speed dial entires with enabled "Subscribe to presence" ,clicked on "Save and Update" button.

 
Result: On rebooting the first five BLF entries are displayed in the Polycom 650 device,13 entries on the sidecar.when called by using speed dial keys , 8 calls can be done successfully and there respective Led's in sidecar/device starts glowing.

Thanks,
-Ashwini
Show
Ananda Teertha added a comment - 2008-06-02 08:10 The issue is resolved, verified on the following build  sipxproxy 3.10.2-012798 2008-06-02T00:34:29 oem-centos5   sipxconfig 3.10.2-012798 2008-06-02T00:45:33 oem-centos5 Steps followed. 1)Registered polycom 650 with the sidecar phone with the user 901. 2)Added 18 speed dial entires with enabled "Subscribe to presence" ,clicked on "Save and Update" button.   Result: On rebooting the first five BLF entries are displayed in the Polycom 650 device,13 entries on the sidecar.when called by using speed dial keys , 8 calls can be done successfully and there respective Led's in sidecar/device starts glowing. Thanks, -Ashwini
Hide
Permalink
Ananda Teertha added a comment - 2008-06-02 08:17
Please note that the above comment was written on behalf of Ashwini.

Thanks,
Show
Ananda Teertha added a comment - 2008-06-02 08:17 Please note that the above comment was written on behalf of Ashwini. Thanks,
Hide
Permalink
Martin Steinnman2 added a comment - 2008-06-02 10:38
Have we tried this with a full load of 3 side cars?
Show
Martin Steinnman2 added a comment - 2008-06-02 10:38 Have we tried this with a full load of 3 side cars?
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2008-06-03 23:23
Raghu, Please comment on Martin's question. Thanks.
Show
Lih-Shyng Tzeng added a comment - 2008-06-03 23:23 Raghu, Please comment on Martin's question. Thanks.
Hide
Permalink
Baslingappa.B Baslingappa.B added a comment - 2008-06-04 01:58
Please note that Ashwini 's comments were based on verification using a single side car.(18 BLF entries)

As per Martin's comment verified with 3 side cars in the following build,
 sipxproxy 3.10.2-012798 2008-06-02T00:34:29 oem-centos5
 sipxconfig 3.10.2-012798 2008-06-02T00:45:33 oem-centos5


Steps followed for verification.
1)Add 47 speed dial entries with subscribe to presence enabled.
2)Each side car has 6 real phones two call park extension and rest were dummy users.

After rebooting Phone TUI and side cars showed up all the speed dial entries and the LED's respective to the users glow when the users were kept busy.

Thanks,
Basling.
Show
Baslingappa.B Baslingappa.B added a comment - 2008-06-04 01:58 Please note that Ashwini 's comments were based on verification using a single side car.(18 BLF entries) As per Martin's comment verified with 3 side cars in the following build,  sipxproxy 3.10.2-012798 2008-06-02T00:34:29 oem-centos5  sipxconfig 3.10.2-012798 2008-06-02T00:45:33 oem-centos5 Steps followed for verification. 1)Add 47 speed dial entries with subscribe to presence enabled. 2)Each side car has 6 real phones two call park extension and rest were dummy users. After rebooting Phone TUI and side cars showed up all the speed dial entries and the LED's respective to the users glow when the users were kept busy. Thanks, Basling.

People

  • Assignee:
    Unassigned
    Reporter:
    Martin Steinnman2
Vote (3)
Watch (2)

Dates

  • Created:
    2008-03-31 15:37
    Updated:
    2009-05-04 16:28
    Resolved:
    2008-05-19 14:20

Agile

  • View on Rapid Board
  • Atlassian JIRA (v5.0.6#733-sha1:f48fab7)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for OpenSCS/sipXecs. Try JIRA - bug tracking software for your team.