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

Key: XCF-2402
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Lih-Shyng Tzeng
Votes: 2
Watchers: 2
Available Workflow Actions

Resolve
Request Information
Operations

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

Support Snom phone's BLF feature

Created: 2007-04-08 10:58   Updated: 2008-08-29 12:32
Component/s: snom
Affects Version/s: 3.10.2
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Dependancy
This issue depends on:
XCF-2391 support SNOM v. 7 firmware Major Open
 
Related
This issue related to:
XCF-1706 add support to configure snom Functio... Major Resolved
 


 Description  « Hide
Here's the link to how to configure Snom's BLF feature
http://snom.com/wiki/index.php/Interoperability/Broadsoft

 All   Comments   Work Log   Change History      Sort Order:
Martin Steinmann - 2008-03-28 14:00
BLF was tested against SNOM phones using manual configuration of the BLF feature in the phone in XECS-1253. The remaining issue is now to support the SNOM BLF feature as part of the Speed Dial configuration in sipXconfig

Damian Krzeminski - 2008-03-28 16:41
According to Lih BLF was tested on SNOM firmware version : snom360-SIP 7.1.30

Damian Krzeminski - 2008-04-01 14:00
We do not support SNOM 7 yet. Could you test it on SNOM 6 firmware so that we can fix it in 3.10

Anushree Ganguly - 2008-04-08 07:49
Lih,
Right now we have two Snom 320 (Version : 7.1.30) phones ,and a snom 360 (Version : 7.1.30) phone for testing out of which one of the snom 320 phone's has problem with the keys which we are trying to rectify.
As the issue says we have to test this issue with snom 6 firmware. Could you please tell me if downgrading the firmware version had any bad experience earlier , else we can downgrade the snom phones from 7.1.30 version to any Snom 6 version safely and verify this issue.

Lih-Shyng Tzeng - 2008-04-08 08:46
Michael, Could you please help answer Anushree's questions? Thanks.

Michael Haag - 2008-04-08 09:34
Anushree, as far as I know there's no problem with downgrading the snom from v7 to v6. Here's a relevant link:

   http://wiki.snom.com/Firmware/V7/Downgrade_Description


btw, Lih, your link above, for BLF config instructions, does not point to anything specific to BLF. Perhaps Snom changed the link. Regardless, this is probably what you meant to point to:

   http://wiki.snom.com/Interoperability/Broadsoft

Lastly, note that configuration BLF on a Snom requires setting the Function keys. However, since sipxconfig does not currently provide a GUI for configuring Snom Function keys (see XCF-1706), the function keys can only be configured via the Snom's own web UI. So, we should insure that sipxconfig's 'speed dial/presence' (BLF) configuration does not conflict with Function key configuration done via the Snom's own GUI. (or, even better, address XCF-1706 so that sipxconfig can be fully responsible for the configuration of snom function keys).

Damian Krzeminski - 2008-04-29 15:53
In http://wiki.snom.com/Interoperability/Broadsoft:

Busy Lamp Field (BLF) is supported in application firmware version 7.0 and higher.

Looks like resolving this one does depend on XCF-2391 (support SNOM v. 7 firmware)

Martin Steinmann - 2008-04-30 11:07
From the comments above it sounds QA has not yet verified this with the 6.x firmware. The reference above to the 7,0 firmware requirement is in regards to Broadsoft interoperability. What about standards based BLF using resource lists? I'd like QA to compete the testing on the latest 6.x firmware against interop.pingtel.com

Prakash PM - 2008-05-01 08:00
Snom wiki- http://wiki.snom.com/Interoperability/Broadsoft says "Busy Lamp Field (BLF) is supported in application firmware version 7.0 and higher."
I also tried by configuring a speed dial to the number to be monitored. I've also tried by giving the BLF URI given in the interop server running with 3.10.1-012157, but that didn't work.
Firmware Version of the Phone used : 6.5.17