No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


SBC Encryption License Must Be Configured for Traversal Between Public and Private Networks in CloudEC6.X Networking

Publication Date:  2019-04-08 Views:  38 Downloads:  0
Issue Description

After the traversal between public and private networks is configured and interconnection is implemented in a CloudEC6.X delivery, some software clients occasionally fail to join conferences.

Alarm Information
Handling Process

1. Check the configuration of the SBC, USM, and ECS. It is found that the configuration is normal. Software clients in external networks cannot be connected only at a certain probability.
2. The customer is asked to check the network and firewall configurations for several times, and modifies the configurations as required.
3. Check the SBC license and find that no encryption license is configured.

Root Cause
The SBC is not configured with an encryption license. SIP signaling can be intercepted by the carrier during the calling process. Therefore, SIP signaling on the access side must be encrypted using TLS.
Add the SBC encryption license and configure TLS encryption.


The SBC encryption license must be configured for the traversal between public and private networks in CloudEC6.X.