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!
Hello,FYI, we have posted on our website configuration instructions for integration of the CIsco Unified Border Element (CUBE) with TransNexus ClearIP software.We also have provided a high-level integration overview on our website to explain how the integ...
AI is going to change many tasks and, as a result, many jobs.
In this podcast on artificialintelligence in the workplace, we explore how jobs may change--and what companies can do to keep workers ahead of the shift:
Check out the podcast:...
Join this featured IT Admin Control Hub session where you’ll hear about the improved Meeting diagnostics capability in Control Hub which provides IT Admins richer insights about their meetings, the participants and the quality of service. See metrics to h...