Customizing Recorded Sip Messages Sent To Srs - AudioCodes Mediant 4000 SBC User Manual

CHAPTER 16 Services
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:
●
●

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
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
Index
Name
Manipulation Set ID
Message Type
Condition
Action Subject
Action Type
Action Value
Index
Name
Manipulation Set ID
Message Type
Condition
Action Subject
Action Type
Action Value
'UUI Format' in the IP Groups table - enables Avaya support.
'Network Node ID' - defines the Network Node Identifier of the device for Avaya
UCID.
0
Store My-header in var.session
11
Any
Header.My-header exists And Header.My-header != ''
Var.Session.0
Modify
Header.My-header
1
Send My-header to SRS
12
Invite.Request
Var.Session.0 != ''
Header.My-header
Add
Var.Session.0
on page 478) to add them to these INVITE messages.
Value
- 205 -
Mediant 4000 SBC | User's Manual