I have a phone server that is connecting to an external SIP trunk and I have configured a static NAT entry just for the phone server to a dedicate IP on the external interface of the ASA. When I look at packet capture, the initial Register request shows that it is connecting to the SIP trunk and that the Request Options is showing that it is coming from the public IP on our ASA - exactly what we want. Yay!
Here is the problem, the Call-ID, Sent-By Address and Contact URL host all show the internal IP address of the phone server. I enabled SIP Inspection on our global service policy and the issue is still the same. Does anyone have ideas? Thanks!
... View more