Broadsoft's Shared Phone Line Call Appearance For Sbc Survivability - AudioCodes Mediant 3000 User Manual

Voip media gateway
Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

Below is an example of an XML body received from the BroadWorks server:
<?xml version="1.0" encoding="utf-8"?>
<BroadsoftDocument version="1.0" content="subscriberData">
<phoneNumbers>
<phoneNumber>2403645317</phoneNumber>
<phoneNumber>4482541321</phoneNumber>
</phoneNumbers>
<aliases>
<alias>sip:bob@broadsoft.com</alias>
<alias>sip:rhughes@broadsoft.com</alias>
</aliases>
<extensions>
<extension>5317</extension>
<extension>1321</extension>
</extensions>
</BroadSoftDocument>
19.1.11.2
BroadSoft's Shared Phone Line Call Appearance for SBC
Survivability
The device can provide redundancy for BroadSoft's Shared Call Appearance feature.
When the BroadSoft application server switch (AS) fails or does not respond, or when the
network connection between the device and the BroadSoft AS is down, the device
manages the Shared Call Appearance feature for the SIP clients.
This feature is supported by configuring a primary extension and associating it with
secondary extensions (i.e., shared lines) so that incoming calls to the primary extension
also ring at the secondary extensions. The call is established with the first extension to
answer the call, and consequently, the ringing at the other extensions stop. For example,
assume primary extension number 600 is shared with secondary extensions 601 and 602.
In the case of an incoming call to 600, all three phone extensions ring simultaneously
(using the device's call forking feature as described in 'SIP Forking Initiated by SIP Proxy
Server' on page 389). Note that incoming calls specific to extensions 601 or 602 ring only
at these specific extensions.
Figure 19-7: Call Survivability for BroadSoft's Shared Line Appearance
SIP User's Manual
384
Mediant 3000
Document #: LTRT-89712

Advertisement

Table of Contents
loading

Table of Contents