Sip Profiles

[mspdog22]

I have a cisco 2911 voice router set up for sip trunk to provider. 

I am running this behind a nat device and trying to get sip profile to rewrite the private ip to the public ip. 

I have set this up with applying the sip profile to my dial peer. The provider still says i am send the private ip address to them in the sdp header and the sip header 

any help would be great. 

voice class sip-profiles 100
request ANY sip-header Replaces modify "192.168.90.2" "216.5.81.21"
response ANY sip-header Replaces modify "192.168.90.2" "216.5.81.21"
request INVITE sip-header Remote-Party-ID modify "192.168.90.2" "216.5.81.21"
request INVITE sip-header Contact modify "192.168.90.2" "216.5.81.21"
request ANY sip-header Contact modify "192.168.90.2" "216.5.81.21"
request ANY sip-header Remote-Party-ID modify "192.168.90.2" "216.5.81.21"
response ANY sip-header Remote-Party-ID modify "192.168.90.2" "216.5.81.21"
response ANY sip-header Contact modify "192.168.90.2" "216.5.81.21"
request ANY sdp-header Connection-Info modify "192.168.90.2" "216.5.81.21"
request ANY sdp-header Session-Owner modify "192.168.90.2" "216.5.81.21"
response ANY sdp-header Connection-Info modify "192.168.90.2" "216.5.81.21"
response ANY sdp-header Session-Owner modify "192.168.90.2" "216.5.81.21"
response ANY sdp-header Audio-Connection-Info modify "192.168.90.2" "216.5.81.21"
response ANY sdp-header Audio-Attribute modify "sendonly" "sendrecv"
request ANY sdp-header Audio-Attribute modify "sendonly" "sendrecv"
request ANY sdp-header Audio-Media modify "192.168.90.2" "216.5.81.21"
request ANY sdp-header Audio-Connection-Info modify "192.168.90.2" "216.5.81.21"

[R0g22]

First thing, this needs to be done by an ALG. Second, you should use the SIP Profile Test tool to test your profiles against the SIP message -
https://cway.cisco.com/tools/SipProfileTest/

[mspdog22]

Do you mean sip alg from my firewall or from my router?

Thanks

[Jonathan Schulenberg]

Whatever the NAT device is, presumably a firewall. It needs to support SIP protocol inspection and rewriting (aka ALG). I do not believe a SIP Profile will be sufficient to get this done on the CUBE router itself, though you could perform NAT natively on that router instead of an external box.