Typical Examples
The following table provides a summary of typical examples of Message Manipulation rules.
Message Manipulation Examples
|
Message |
Condition |
Action |
Action Type |
Action Value |
Description |
|---|---|---|---|---|---|
|
invite.request |
param.message.sdp.ip=='flowers.com' |
header.diversion |
Add |
'<sip:WeSellFlowers@p4.isp.com>;reason=time-of-day' |
In INVITE requests, add a Diversion header if the c line in the SDP is set to "flowers.com". |
|
info.response |
header.request-uri.methodtype=='488' |
header.request-uri.methodtype |
Modify |
'503' |
Change the Request-URI method type to 503 from 488 in INFO response messages |
|
info.response.180 |
|
header.request-uri.methodtype |
Modify |
'183' |
Change request type method to 183 in 180 response messages. |
|
invite.request |
header.expires.time < '88888' |
header.organisation |
Add |
'audiocodes' |
Check the time parameter in Expires headers. If it is less than 88888, add an organization header to the INVITE request message. |
|
register.request |
|
header.contact. |
Add |
'newValue' |
Add newParam with a value of newValue as a general header level param to REGISTER Contact headers |
|
subscribe.response |
|
header.remote-party-id.0.partytype |
Modify |
'2' |
In Subscribe response messages, change the party type to ‘called’ (note, 1="calling", 2= "called", 3="redirect") in the 1st Remote-Party-ID header. |
|
invite.response |
|
header.from.param.hello |
Remove |
|
Remove the param named "hello" from From headers in INVITE responses. |
|
any |
|
header.user-agent |
Modify |
'TelcoA' |
Change the User-Agent header to telcoA. |
|
any |
|
header.from.quotecontrol |
Modify |
'0' |
Removes quotation marks surrounding display name in From header. |
|
any |
|
header.user-to-user.param.purpose |
Add |
‘isdn-network’ |
Adds the parameter "purpose" with value "isdn-network' to the User-to-User header. |
|
any |
header.to.url.user num> '20' |
header.Result |
Add |
'user part is numerically greater than 20' |
If the user part in the To header is numerically greater than 20, the "Result" header is added to the message with the value "user part is numerically greater than 20". |