Call Forking; Initiating Sip Call Forking - AudioCodes Mediant 1000 User Manual

User's Manual
networks in France. For SPIROU, the device sets the value of the SIP Content-Type
header to "version=spirou; base=itu-t92+".

ITU-92, where the device sets the value of the SIP Content-Type header to
"version=itu-t92+; base=itu-t92+".
To configure interworking of SIP and SIP-I endpoints, using the 'ISUP Body Handling'
parameter (IpProfile_SBCISUPBodyHandling) in the IP Profile table (see ''Configuring IP
Profiles'' on page 393).
You can manipulate ISUP data, by configuring manipulation rules for the SIP Content-Type
and Content-Disposition header values in the Message Manipulations table (see
''Configuring SIP Message Manipulation'' on page 368). For a complete description of the
ISUP manipulation syntax, refer to the SIP Message Manipulation Reference Guide. In
addition, you can use AudioCodes proprietary SIP header X-AC-Action in Message
Manipulation rules to support the following call actions (e.g., SIP-I SUS and RES
messages) for the ISUP SPIROU variant:

Disconnect call (optionally, after a user-defined time): disconnect[;delay=<time in
ms>]

Resume previously suspended call: abort-disconnect

Reply to the message with a SIP response without forwarding the response to the
other side: reply[;response=<response code, e.g., 200>]

Switch IP Profile for the call (re-INVITE only), as defined in the IP Group: switch-profile
[;reason=<reason - PoorInVoiceQuality or PoorInVoiceQualityFailure >]
37.4

Call Forking

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

37.4.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 Groups table's
parameter, 'SBC Client Forking Mode' (see ''Configuring IP Groups'' on page 333).
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.
Version 7.2 707 Mediant 1000B Gateway & E-SBC
37. Advanced SBC Features