Configuring Broadsoft's Shared Phone Line Call Appearance For Survivability - AudioCodes Mediant 4000 SBC User Manual

Session border controllers
Hide thumbs Also See for Mediant 4000 SBC:
Table of Contents

Advertisement

CHAPTER 28    Advanced SBC Features
The device saves the users in its registration database with their phone numbers and extensions,
enabling future routing to these destinations during survivability mode when communication with
the BroadWorks server is lost. When in survivability mode, the device routes the call to the Contact
associated with the dialed phone number or extension number in the registration database.
To enable the BroadWorks survivability feature:
1.
Open the SBC General Settings page (Setup menu > Signaling & Media tab > SBC folder >
SBC General Settings).
2.
From the 'BroadWorks Survivability Feature' drop-down list
(SBCExtensionsProvisioningMode), select Enable:
3.
Click Apply.
Configuring BroadSoft's Shared Phone Line Call Appearance for
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.
The 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
extensions 601 or 602 ring only at these specific extensions.
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.
Configuring SIP Forking Initiated by SIP
Proxy. Note that incoming calls specific to
- 613 -
Mediant 4000 SBC | User's Manual

Advertisement

Table of Contents
loading

Table of Contents