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

Key: XCF-1350
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Innovational Support
Votes: 0
Watchers: 1
Available Workflow Actions

Resolve
Request Information
Operations

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

Can not select template version for Polycom phone groups

Created: 2006-10-26 11:17   Updated: 2007-04-06 09:07
Component/s: polycom
Affects Version/s: 3.6
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: Polycom 301, 501, 601, and 430s


 Description  « Hide
Polycom uses different phone templates for v1.6.x and v2.0 releases of their sip.ld. When setting up phone groups, there is no way to select which version of the template to be used with the group. It only shows v2.0. Until v2.0 is thoroughly tested on the older models of phones (i.e. 301 and 501), customer needs the ability to support both version of the templates on the system.

We know from testing, that you can not use a v2.0 template with v1.6.x. The behavior is unpredicable (phones may reboot).

This may be covered by issue XCF-860, but we thought you could decide if they should be combined.

 All   Comments   Work Log   Change History      Sort Order:
Douglas Hubler - 2007-02-27 13:51
I'm not sure why I marked this for 3.7.5.

Supporting multiple phone firmwares is available in 3.6. Its true you _cannot_ assign firmware by phone groups as Innovational mentioned.

You can
 - assign individual phones as 1.6 or 2.0
 - change all phones to 1.6 or 2.0 at any given time

This covers the case where you want to test 2.0 on a few select phones and then when you are ready, bulk change all the phones. If there is a phone that cannot upgrade, you can even leave that phone on 1.6.

Supporting large groups of phones in running different firmware from each other is not supported, nor it is a high priority issue as it's a very difficult environment to support in general.