AudioCodes Mediant 500 E-SBC User Manual page 488

Figure 28-11: SIP URI Manipulation in IP-to-IP Routing
You can also restrict source user identity in outgoing SIP dialogs in the Outbound
Manipulation table (using the column PrivacyRestrictionMode). The device identifies an
incoming user as restricted if one of the following exists:

From header user is 'anonymous'.

P-Asserted-Identity and Privacy headers contain the value 'id'.
All restriction logic is done after the user number has been manipulated.
Host name (source and destination) manipulations are simply host name substitutions with
the names defined for the source and destination IP Groups respectively (if any, in the IP
Group table).
Below is an example of a call flow and consequent SIP URI manipulations:

Incoming INVITE from LAN:
INVITE sip:1000@10.2.2.3;user=phone;x=y;z=a SIP/2.0
Via: SIP/2.0/UDP 10.2.2.6;branch=z9hGLLLLLan
From:<sip:7000@10.2.2.6;user=phone;x=y;z=a>;tag=OlLAN;paramer1
=abe
To: <sip:1000@10.2.2.3;user=phone>
Call-ID: USELLLAN@10.2.2.3
CSeq: 1 INVITE
Contact: <sip:7000@10.2.2.3>
Supported: em,100rel,timer,replaces
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK
User-Agent: Sip Message Generator V1.0.0.5
Content-Type: application/sdp
Content-Length: 155
v=0
o=SMG 791285 795617 IN IP4 10.2.2.6
s=Phone-Call
c=IN IP4 10.2.2.6
t=0 0
m=audio 6000 RTP/AVP 8
a=rtpmap:8 pcma/8000
a=sendrecv
a=ptime:20

Outgoing INVITE to WAN:
INVITE sip: 9721000@ITSP;user=phone;x=y;z=a SIP/2.0
Via: SIP/2.0/UDP 212.179.1.12;branch=z9hGWwan
From:
<sip:97000@IP_PBX;user=phone;x=y;z=a>;tag=OWan;paramer1=abe
To: <sip: 9721000@ ITSP;user=phone>
User's Manual 488
Mediant 500 E-SBC
Document #: LTRT-10427