Avaya SBC reuses the TLS connection from IP Office for SIP signaling towards the IP Office. The routing profile towards the Remote Branch Office must use a routing entry that matches the server configuration for the Remote Branch Office. For Remote Branch Office routing entries, the transport must be TLS and the Port field must be empty.
Avaya SBC rejects the incoming TLS connection from IP Office if the:
Required TLS Client Certificate is not configured in IP Office.
Self-Signed Certificate is presented by IP Office during TLS handshake.
Peer Verification fails in Avaya SBC with the TLS Client Certificate presented by IP Office.
If the TLS connection from the Remote Branch Office drops, Avaya SBC rejects calls originating from the enterprise until the connection is reestablished. Meanwhile, Avaya SBC displays a 500 server internal error message.
Note:
You can provide custom route entries with the IP Office listen port if you administer DNAT rules in the Firewall or the NAT router.
