To Next Page

To Previous Page

CHAPTER37 Advanced SBC Features

Mediant 1000 Gateway & E-SBC | User's Manual

In normal operation, when subscribers (such as IP phones) register with the BroadWorks server

through the device, the device includes the SIP Allow-Events header in the sent REGISTER

message. In response, the BroadWorks server sends the device a SIP 200 OK containing an XML

body with subscriber information such as extension number, phone number, and URIs (aliases), as

shown in the example below:

<?xml version="1.0" encoding="utf-8"?>

</phoneNumbers>

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

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

</aliases>

</extensions>

</BroadSoftDocument>

The device forwards the 200 OK to the subscriber (without the XML body). The call flow is shown

below:

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.

- 830 -

AudioCodes E-SBC User Manual

Questions and Answers: