Configure the SIP NAT which is homed in the core (trusted) realm.
Call-ID Contact f From=ip-ip-tgt i Join
m P-Asserted-Identity r Record-Route
Refer-To Referred-by Replaces Reply-To
Route t To=ip-ip-tgt v Via
last-modified-date 2010-07-16 19:14:41
realm-id - enter the core realm ID here. Parent topic: Net-Net 3000, Net-Net 4000 Series SBC - Remote User Deployment Scenario: Nat or No NAT
domain-suffix - enter a domain suffix (having core as part of the suffix allows core traffic to be easily identified in traces.
ext-proxy-address - enter the SIP server address, in this case it is the Lotus Sametime Unified Telephony sipsm IP address.
ext-proxy-port - sip port of the ext-proxy-address.
ext-address - SBC's core sip-interface IP address (facing Telephony Control Server).
home-address - must be set to a unique IP address in the same network as the access sip-interface (i.e., it should not be configured anywhere else within the SBC or outside of the SBC)
home-proxy-port - set to 5060.
Acme Packet cookies by default are added to the user part of the contact URI which can break features such as large conference. A workaround provided by Acme Packet is to move the cookie from the user part into a parameter. This can be accomplished by setting the use-url-parameter option to "all" and setting the parameter-name field to the name of the access realm.
The following are the default sip-nat headers that are added:
Call-ID, Contact, Join, P-Asserted-Identify, Record-Route, Referred-by Refer-To, Replaces, Reply-To, Route, Via. From and To headers need to be replaced as follows in the sip-nat context:
SolAcme3800A(sip-nat)# headers From=ip-ip-tgt
SolAcme3800A(sip-nat)# headers To=ip-ip-tgt
SolAcme3800A(sip-nat)# headers Referred-by
SolAcme3800A(sip-nat)# headers P-Asserted-Identity