Call Forking; Initiating Sip Call Forking; Sip Forking Initiated By Sip Proxy Server - AudioCodes Mediant 3000 User Manual

User's Manual
The rest of the process is similar to emergency call routing in a Lync environment.
Configuration includes the following:

Enabling E9-1-1 by configuring the 'PSAP Mode' parameter to PSAP Server in the IP
Group table for the IP Group of the PSAP server (see ''Enabling the E9-1-1 Feature''
on page 302).

Configuring routing rules in the IP-to-IP Routing table for routing between the
emergency callers' IP Group and the PSAP server's IP Group. The only special
configuration is required on the rule for routing from emergency callers to the PSAP
server:
•
Configure the emergency number (e.g., 911) in the 'Destination Username Prefix'
field.
•
Assign the Call Setup rule, which you configured for obtaining the ELIN number
from the AD, in the 'Call Setup Rules Set ID' field (see ''Configuring SBC IP-to-IP
Routing Rule for E9-1-1'' on page 303).
36.3

Call Forking

This section describes various Call Forking features supported by the device.

36.3.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 343).
The device can also fork INVITE messages received for a Request-URI of a specific
contact (user), belonging to the destination IP Group User-type, registered in the database
to all other users located under the same AOR as the specific contact. This is configured
using the SBCSendInviteToAllContacts parameter.

36.3.2 SIP Forking Initiated by SIP Proxy Server

The device can handle the receipt of multiple SIP 18x responses as a result of SIP forking
initiated by a proxy server. This occurs when the device sends an INVITE, received from a
user agent (UA), to a proxy server and the proxy server then forks the INVITE request to
multiple UAs. Several UAs may answer and the device may therefore, receive several
replies (responses) for the single INVITE request. Each response has a different 'tag' value
in the SIP To header.
Version 7.0 645
36. Advanced SBC Features
Mediant 3000