Interworking Call Hold; Call Survivability; Auto-Provisioning Of Subscriber-Specific Information For Broadworks Server For Survivability - AudioCodes Mediant 1000B User Manual

Analog & digital voip media gateway enterprise session border controller gateway & e-sbc
Hide thumbs Also See for Mediant 1000B:
Table of Contents

Advertisement

User's Manual

28.8.11 Interworking Call Hold

The device supports the interworking of call hold / retrieve requests between IP entities
supporting different call hold capabilities:
Interworking SDP call hold formats. This is configured by the IP Profile parameter,
'SBC Remote Hold Format'.
Interworking the play of the held tone for IP entities that cannot play held tones locally.
This is configured by the IP Profile parameter, 'SBC Play Held Tone'.
Interworking generation of held tone where the device generates the tone to the held
party instead of the call hold initiator. This is configured by the IP Profile parameter,
'SBC Reliable Held Tone Source'.
For configuring IP Profiles, see ''Configuring IP Profiles'' on page 302.
28.9

Call Survivability

This section describes various call survivability features supported by the SBC device.
28.9.1 Auto-Provisioning of Subscriber-Specific Information for
BroadWorks Server for Survivability
This feature enables SBC user registration for interoperability with BroadSoft BroadWorks
server to provide call survivability in case of connectivity failure with the BroadWorks
server, for example, due to a WAN failure. This feature enables local users to dial a local
extension (or any other configured alias) that identifies another local user, in survivability
mode. This feature is enabled using the SBCExtensionsProvisioningMode parameter.
In normal operation, when subscribers (such as IP phones) register to 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). The device forwards the 200 OK to the subscriber (without the
XML body).
Figure 28-9: Interoperability with BroadWorks Registration Process
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 in
survivability mode, the device routes the call to the Contact associated with the dialed
phone number or extension number in the registration database.
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>
Version 6.8
507
Mediant 1000B Gateway & SBC
28. SBC Overview

Advertisement

Table of Contents
loading

Table of Contents