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

Media gateway & enterprise session border controller (e-sbc)

Hide thumbs Also See for Mediant 800B:

Table of Contents

User's Manual

</phoneNumbers>

<alias>sip:bob@broadsoft.com</alias>

<alias>sip:rhughes@broadsoft.com</alias>

</extensions>

</BroadSoftDocument>

35.5.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 691. Note that incoming calls specific to extensions 601 or 602 ring only at

these specific extensions.

Figure 35-6: Call Survivability for BroadSoft's Shared Line Appearance

To configure this capability, you need to configure a shared-line, inbound manipulation rule

for registration requests to change the destination number of the secondary extension

numbers (e.g. 601 and 602) to the primary extension (e.g., 600). Call forking must also be

enabled. The following procedure describes the main configuration required.

Mediant 800B Gateway and E- SBC

35. Advanced SBC Features