AudioCodes Mediant 3000, User Manual

Page: 432 / 872

User's Manual 432 Document #: LTRT-89729
Mediant 3000
28.9.4 Survivability Mode Display on Aastra IP Phones
If the SBC device is deployed in an Enterprise network with Aastra IP phones and
connectivity with the WAN fails, the device provides call survivability by enabling
communication between IP phone users within the LAN enterprise. In such a scenario, the
device can be configured to notify the IP phones that it is currently operating in Survivability
mode. When this occurs, the Aastra IP phones display the message, "StandAlone Mode"
on their LCD screens. This feature is enabled by setting the
SBCEnableAASTRASurvivabilityNotice parameter to 1.
When this feature is enabled and the SBC device is in Survivability mode, it responds to
SIP REGISTER messages from the IP phones with a SIP 200 OK containing the following
XML body:
Content-Type: application/xml
<?xml version="1.0" encoding="utf-8"?>
<LMIDocument version="1.0">
<LocalModeStatus>
<LocalModeActive>true</LocalModeActive>
<LocalModeDisplay>StandAlone Mode</LocalModeDisplay>
</LocalModeStatus>
</LMIDocument>
28.10 Call Forking
This section describes various Call Forking features supported by the device.
28.10.1 Initiating SIP Call Forking
The SBC device supports call forking of an incoming call to multiple SBC users
(destinations). Call forking is supported by the device's capability of registering multiple SIP
client user phone contacts (mobile and fixed-line extensions) under the same Address of
Record (AOR) in its registration database. This feature can be implemented in the following
example scenarios:

An enterprise Help Desk, where incoming customer calls are simultaneously sent to
multiple customer service agent extensions.

An employee's phone devices, where the incoming call is simultaneously sent to
multiple devices (e.g., to the employee's office phone and mobile SIP phone).

An enterprise reception desk, where an incoming call is simultaneously sent to
multiple receptionists.
The device supports various modes of call forking. For example, in Parallel call forking
mode, the device sends the INVITE message simultaneously to all the users registered
under the same AOR, resulting in the ringing of all extensions; the first extension to pick up
the call receives the call, and all other extensions stop ringing. The Call Forking feature is
configured by creating a User-type IP Group and configuring the IP Group table's
parameter, 'SBC Client Forking Mode' (see Configuring IP Groups on page
281 ).
The device can also fork INVITE messages received for a Request-URI of a specific
contact (user) registered in the database to all other users located under the same AOR as
the specific contact. This is configured using the SBCSendInviteToAllContacts parameter.