User Community Feedback

We are running into several scenarios with customers who require certificate-based trunks but are unable to bypass the NAT requirements.

The current documentation does not provide support for NAT based Certificate Trunks, which technically should be possible.

This is most likely due to having to manipulate the SIP headers (By means of SIP Profiles) to re-write the Private to Public IP addressing.

Looking at the Microsoft Direct Connect CUBE implementation documentation you can see they allow (provide you with the SIP Profiles) for both NAT and Non-NAT based setups on the CUBE.

https://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/interoperability-portal/direct-routing-with-cube.pdf

Would be great to have the option, support, and documentation for Certificate Based Trunk behind NAT.