Sip Calling Name Manipulations; Sip Message Manipulation - AudioCodes Mediant 3000 User Manual

SIP User's Manual

18.3.8 SIP Calling Name Manipulations

You can configure manipulation rules for manipulating the calling name (i.e., caller ID) in
the SIP message. This can include modifying or removing the calling name. SIP calling
name manipulation is applicable to Tel-to-IP and IP-to-Tel calls.
For example, assume that an incoming SIP INVITE message includes the following
header:
P-Asserted-Identity: "company:john" sip:6666@78.97.79.104
Using the IP-to-Tel calling name manipulation, the text, "company" can be changed to
"worker" in the outgoing INVITE, as shown below:
P-Asserted-Identity: "worker:john" sip:996666@10.13.83.10
To manipulate the calling name received in the SIP message, use the following
patrameters:

For IP-to-Tel calls, use the CallingNameMapIp2Tel ini file parameter

For Tel-to-IP calls, use the CallingNameMapTel2Ip ini file parameter

18.3.9 SIP Message Manipulation

You can manipulate SIP messages using the Message Manipulations table. This can be
configured using the MessageManipulations ini file parameter. This manipulation includes
insertion, removal, and/or modification of SIP headers. Multiple manipulation rules can be
configured for the same SIP message.
Once you have defined SIP message manipulation rules (Manipulation Set ID), you can
assign them to inbound and outbound SIP messages:

For manipulation on all inbound SIP INVITE messages, the Manipulation Set ID is
selected (and enabled) using the "global" parameter, GWInboundManipulationSet.

For manipulation on outbound SIP INVITE messages, the Manipulation Set ID is
selected (and enabled) using the following logic:
a. According to the settings of the Outbound Message Manipulation Set parameter
of the destination IP Group table. In other words, manipulation can be done per
destination IP Group. If this parameter is not configured, see b below.
b. According to the settings of the "global" parameter,
GWOutboundManipulationSet. If this parameter is also not configured, no
manipulation is done.
Notes:
Version 6.4
•
Each message can be manipulated twice - once for the source leg
manipulation rules and once in the destination leg (source and
destination IP Groups).
•
Unknown SIP parts can only be added or removed.
•
SIP manipulations do not allow you to remove or add mandatory SIP
headers. They can only be modified and only on requests that initiate
new dialogs. Mandatory SIP headers include To, From, Via, CSeq, Call-
Id, and Max-Forwards.
•
Manipulation of SDP body is currently not supported.
•
For the IP-to-IP application, the outgoing message is re-created and
thus, SIP headers not relevant to the outgoing SIP session (e.g.,
Referred-By) are not included in the outgoing message. Therefore, if
required, manipulations on such headers should be handled in inbound
manipulation.
295
18. GW and IP to IP
November 2011