AudioCodes Mediant 4000 SBC - Customizing Recorded SIP Messages Sent to SRS

CHAPTER16 Services
Mediant 4000 SBC | User's Manual
xml metadata:
<ac:AvayaUCID xmlns="urn:ietf:params:xml:ns:Avaya">
FA080019001038F725B3</ac:AvayaUCID>
For calls sent from the device to Avaya equipment, the device can generate the Avaya
UCID, if required. To configure this support, use the following parameters:
● 'UUI Format' in the IP Groups table - enables Avaya support.
● 'Network Node ID' - defines the Network Node Identifier of the device for Avaya
UCID.
Customizing Recorded SIP Messages Sent to SRS
The original SIP headers of recorded legs are not included in the INVITE messages that the device
sends to the SRS. If you need to include SIP headers, you can use Message Manipulation rules
(see Configuring SIP Message Manipulation on page478) to add them to these INVITE messages.
The following examples describe how to configure this using Message Manipulation rules:
■ Example 1 - Adding a specific SIP header called "My-header" to the INVITE that is sent to the
SRS:
a. The example uses two Message Manipulation rules - one for storing the header by using
manipulation syntax for session variables, and one for adding the header to the INVITE.
Parameter Value
Index 0
Name Store My-header in var.session
Manipulation Set ID 11
Message Type Any
Condition Header.My-header exists And Header.My-header != ''
Action Subject Var.Session.0
Action Type Modify
Action Value Header.My-header
Index 1
Name Send My-header to SRS
Manipulation Set ID 12
Message Type Invite.Request
Condition Var.Session.0 != ''
Action Subject Header.My-header
Action Type Add
Action Value Var.Session.0
- 205 -