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-4762

Add support for BLA (Bridge Line Appearance) feature

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

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 4.1.1, 4.2
  • Component/s: None
  • Labels:
    None
  • Team:
    Documentation, Management

Description

Polycom phones support BLA (Bridge Line Appearance) feature, which implement the following internet drafts and RFCs.

   - RFC 3680: A Session Initiation Protocol (SIP) Event Package for Registrations
   - RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification
   - draft-ietf-sipping-dialog-package-06
   - draft-anil-sipping-bla-02

sipXpbx shall support the above RFCs and drafts in support of Polycom phones' BLA feature.

Phones to be supported in priority order: LG-Nortel, Polycom, Aastra, Snom

Issue Links

required for

New Feature - A new feature of the product, which has yet to be developed. XX-5439 Add configuation support for BLA (Bridge-Line Appearance) feature

  • 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.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2006-06-29 21:35
Linked this issue with XCF-1114.
Show
Lih-Shyng Tzeng added a comment - 2006-06-29 21:35 Linked this issue with XCF-1114.
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2006-06-29 21:37
Remove the link to XCF-1114, which I added by mistake.
Show
Lih-Shyng Tzeng added a comment - 2006-06-29 21:37 Remove the link to XCF-1114, which I added by mistake.
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2006-06-29 21:38
Woof, You are the proud owner of this feature. Thanks.
Show
Lih-Shyng Tzeng added a comment - 2006-06-29 21:38 Woof, You are the proud owner of this feature. Thanks.
Hide
Permalink
Michal Bielicki added a comment - 2006-06-30 03:28
I think the BLA/BLF feature on the SNOM phones works in the same way as on the Polycoms. Just send a request to SNOM to confirm that. So probably we can have both supported in one go
Show
Michal Bielicki added a comment - 2006-06-30 03:28 I think the BLA/BLF feature on the SNOM phones works in the same way as on the Polycoms. Just send a request to SNOM to confirm that. So probably we can have both supported in one go
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2006-07-02 19:04
Polycom 1.6.3 firmware added the BLA support.
Show
Lih-Shyng Tzeng added a comment - 2006-07-02 19:04 Polycom 1.6.3 firmware added the BLA support.
Hide
Permalink
Lih-Shyng Tzeng added a comment - 2006-07-11 16:38
Take this off 3.6 list, in favor of BLF (XPB-697), which was added to 3.6.
Show
Lih-Shyng Tzeng added a comment - 2006-07-11 16:38 Take this off 3.6 list, in favor of BLF (XPB-697), which was added to 3.6.
Hide
Permalink
Mardy Marshall added a comment - 2007-07-17 14:18
Added clarification of Appearance Number Allocation and initial description of Appearance State Publisher component.
Show
Mardy Marshall added a comment - 2007-07-17 14:18 Added clarification of Appearance Number Allocation and initial description of Appearance State Publisher component.
Hide
Permalink
Michael Picher added a comment - 2008-07-03 06:16
There seems to be some confusion in above comments between BLF and BLA.

BLF = Busy Lamp Field. This would be whether a particular phone is busy or not. This would be the Manager/Assistant relationship mentioned above.

BLA = Bridged Line Appearance. This would be the status of an outside line (FXO port status).
Show
Michael Picher added a comment - 2008-07-03 06:16 There seems to be some confusion in above comments between BLF and BLA. BLF = Busy Lamp Field. This would be whether a particular phone is busy or not. This would be the Manager/Assistant relationship mentioned above. BLA = Bridged Line Appearance. This would be the status of an outside line (FXO port status).
Hide
Permalink
eliot robinson added a comment - 2009-02-17 06:33
many of our users are very interested in bridged line appearances (bla) which is known in the sip world as shared appearances of sip address of record. with the current system, the admin has to transfer the call to the boss.

latest BLISS internet-draft is http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-01.txt which replaces draft-anil-sipping-bla-02.
Show
eliot robinson added a comment - 2009-02-17 06:33 many of our users are very interested in bridged line appearances (bla) which is known in the sip world as shared appearances of sip address of record. with the current system, the admin has to transfer the call to the boss. latest BLISS internet-draft is http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-01.txt which replaces draft-anil-sipping-bla-02.
Hide
Permalink
Aaron Brumpton added a comment - 2009-05-12 14:24
Let me know if you need support from Polycom to implement this feature.
Show
Aaron Brumpton added a comment - 2009-05-12 14:24 Let me know if you need support from Polycom to implement this feature.
Hide
Permalink
Carmi Weinzweig added a comment - 2009-05-13 11:30
There seems to be some confusion over the name/meaning of this function. I have seen it called shared call appearance, bridged call appearance, shared line appearance and several other names. What I mean and I think many others also mean is a feature that would act the following way (a real example from a real company using a Definity):

A manager/admin setup that works as follows:

Sarah, a manager, has a phone on her desk with call appearances for her main number (x-3123). She also has a phone on her office conference table with its own number (x-3302) but also with shared call appearances for her main number (x-3123). She shares a conference room with Ed, John, Steve, Susan and Simon. All their phone numbers have shared call appearances that conference room's phone.

Molly (Sarah's administrative assistant) has a phone with shared call appearances for Sarah, Ed and Susan (two other Executive Team members for whom she provides shared coverage with Wendy and Lisa).

When a call comes in for Sarah on x-3123, Molly can answer it, and just by looking at those little red and green lights on her phone she can tell if Sarah is on a call or not. She can then place this call on hold (not park it, just hit that red hold button) and call Sarah announcing this call.

Sarah can answer this call just by pressing that button next to the flashing light (indicating a call on hold) and picking up her phone. She does not have to use call pick up. She can also pick this call up on her office conference table, or in the Executive Team's conference room in exactly the same way, not needing to understand or know anything else ("press the button with my name on it next to the blinking green led").
Show
Carmi Weinzweig added a comment - 2009-05-13 11:30 There seems to be some confusion over the name/meaning of this function. I have seen it called shared call appearance, bridged call appearance, shared line appearance and several other names. What I mean and I think many others also mean is a feature that would act the following way (a real example from a real company using a Definity): A manager/admin setup that works as follows: Sarah, a manager, has a phone on her desk with call appearances for her main number (x-3123). She also has a phone on her office conference table with its own number (x-3302) but also with shared call appearances for her main number (x-3123). She shares a conference room with Ed, John, Steve, Susan and Simon. All their phone numbers have shared call appearances that conference room's phone. Molly (Sarah's administrative assistant) has a phone with shared call appearances for Sarah, Ed and Susan (two other Executive Team members for whom she provides shared coverage with Wendy and Lisa). When a call comes in for Sarah on x-3123, Molly can answer it, and just by looking at those little red and green lights on her phone she can tell if Sarah is on a call or not. She can then place this call on hold (not park it, just hit that red hold button) and call Sarah announcing this call. Sarah can answer this call just by pressing that button next to the flashing light (indicating a call on hold) and picking up her phone. She does not have to use call pick up. She can also pick this call up on her office conference table, or in the Executive Team's conference room in exactly the same way, not needing to understand or know anything else ("press the button with my name on it next to the blinking green led").
Hide
Permalink
Carolyn Beeton added a comment - 2009-07-10 13:33
Code was submitted to main branch 15948.

Crubicle reviews at http://code.sipfoundry.org/cru/XECS-28, http://code.sipfoundry.org/cru/XECS-29, and http://code.sipfoundry.org/cru/XECS-31.

Some documentation can be found at http://wiki.sipfoundry.org/display/~cbeeton/Shared+Appearance+Agent
Show
Carolyn Beeton added a comment - 2009-07-10 13:33 Code was submitted to main branch 15948. Crubicle reviews at http://code.sipfoundry.org/cru/XECS-28, http://code.sipfoundry.org/cru/XECS-29, and http://code.sipfoundry.org/cru/XECS-31. Some documentation can be found at http://wiki.sipfoundry.org/display/~cbeeton/Shared+Appearance+Agent

People

  • Assignee:
    Unassigned
    Reporter:
    Lih-Shyng Tzeng
Vote (10)
Watch (8)

Dates

  • Created:
    2006-06-29 21:34
    Updated:
    2010-08-22 15:36
    Resolved:
    2009-07-10 13:33

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.