Interoperability/PBX/Sylantro

From Snom User Wiki

Jump to: navigation, search

Contents

snom phone settings

Function keys

The following function key types can be used with Sylantro:


Extension/Destination

With a Sylantro system a programmable key mapped as 'Extension/ Destination' can also be used to pickup a call parked at a park orbit on the server. For picking up a call the park orbit extension must be specified with a star code *99. e.g. to pickup parked calls from an orbit 800@mysylantro.com on the server, the destination number of the programmable key on the phone must be set as *99800@mysylantro.com. Please contact your system administrator for further details.


Intercom

The intercom destination must be specified with a star code *96 e.g. in order to make an Intercom call to 800@mysylantro.com, the intercom number for the programmable key must be set as *96800@mysylantro.com. Please contact your system administrator for further details.


Park Orbit

The Park Orbit number must be specified with a star code *98 e.g. in order to Park a call at 800@mysylantro.com, the park orbit number for the programmable key must be set as *98800@mysylantro.com. Please contact your system administrator for further details.


Shared Line

The Bridged Line Appearance (BLA) feature allows subscribers to share SIP lines and also provides status monitoring of the shared line. The BLA feature is commonly offered in the IP Centrex services and IP-PBX offerings. When a user places an outgoing call using such an appearance, all members belonging to that particular BLA group are notified of this usage, and are blocked from using this line appearance until the line goes back to idle state or if the call is placed on hold. Similarly all members of the BLA group are notified of an incoming call and the call can be picked up on a line appearance associated with the BLA extension.

This Bridged/Shared Line Appearance (BLA) feature is also available on snom 360/320. The new feature allows subscribers to share the available SIP lines without running into deadlock situations. For visual indications, LEDs available on the snom phones indicate the status of the shared lines and also allow a BLA group member to pickup incoming calls to the BLA group. When the shared line is occupied by a BLA group member, other members of the group are blocked from using the line until its status goes back to idle thus indicating availability. The following screen shots indicate how Bridged Lines can be configured on snom phones.


Line Settings:

These settings reflect the basic SIP settings for registering the bridged line.


SIP Settings:

Note: The “Shared Line” setting MUST be turned on in order to enable the bridged line appearance feature for a SIP line.


Function Key Settings:

BLA members can monitor the status of the bridged line via the Function keys available on the snom phones. For monitoring the status of a bridged line, the function key must be configured as a “Shared Line” type. In addition, the “Number” must be set to the bridged line resource URI. Once the phone has registered and subscribed successfully for the BLA resource, the LED corresponding to the programmed function key indicates the status of the bridged line. LED “on” indicates the line is in use, while LED “off” indicates an idle status.


Bridged Line Subscription/Notification:

When a BLA member registers for the BLA resource, the State Agent sends a BLA subscription to the member. The BLA member sends its own status to the notification agent and also subscribes to the BLA resource itself for monitoring the status of the shared line. See the SIP Trace for more details.


Push2Talk

The 'Push2Talk' extension must be specified with a star code *96 e.g. in order to make an announcement call to 800@mysylantro.com, the 'Push2Talk' extension for the programmable key must be set as *96800@mysylantro.com. Please contact your system administrator for further details.


Personal tools
Interoperability