Require - AudioCodes Mediant 3000 User Manual

Below are header manipulation examples:
Example 1 Rule:
Result:
Example 2 Rule:
Result:
Example 3 Rule:
Result:
C.2.24 Require
An example of the header is shown below:
Require: 100rel
The header properties are shown in the table below:
Header Level Action
Operations Supported
Keyword
Capabilities
Below are header manipulation examples:
Example 1 Rule:
Result:
Example 2 Rule:
Result:
Example 3 Rule:
SIP User's Manual
Test the Request-URI transport type. If 1 (TCP), then modify the URL
portion of the From header:
MessageManipulations 1 = 1, Invite.request,
"header.REQUEST-URI.url.user == '101'",
header.REMOTE-PARTY-ID.url, 2,
'sip:3200@110.18.5.41;tusunami=0', 0;
Remote-Party-ID:
<sip:3200@110.18.5.41;tusunami=0>;party=calling;npi=
0;ton=0
If the method type is 5 (INVITE), then modify the Remote-Party-Id header:
MessageManipulations 2 = 1, Invite.request,
"header.REQUEST-URI.methodtype == '5'",
header.REMOTE-PARTY-ID.url, 2,
'sip:3200@110.18.5.41;tusunami=0', 0;
Remote-Party-ID:
<sip:3200@110.18.5.41;tusunami=0>;party=calling;npi=
0;ton=0
For all request URI's whose method types are 488, modify the message
type to a 486:
MessageManipulations 1 = 1, , header.request-
uri.methodtype=='488', header.request-
uri.methodtype, 2, '486', 0;
SIP/2.0 486 Busy Here
Add
Yes
SIPCapabilities Struct
Add a Require header to all messages:
MessageManipulations 1 = 1, , ,header.require, 0,
"'early-session,em,replaces'", 0;
Require: em,replaces,early-session
If a Require header exists, then delete it:
MessageManipulations 2 = 1, Invite, "header.require
exists" ,header.require, 1, "''", 0;
The Require header is deleted.
Set the early media options tag in the header:
Delete Modify
Yes Yes
Sub Types
Read/Write
792
Mediant 3000
List Entries
N/A
Attributes
Document #: LTRT-89712