Page History

...

• Ribbon SBC Core
• Ribbon SBC Core license
  • A valid license from Ribbon is required to enable functionality on Ribbon SBCs. Each SBC license provides a base set of capabilities to allow enabling and adding of additional features and capacity, as required.
• Public IP addresses
• TLS certificates for SBC Core

  • Refer to Managing Certificates.

• Cisco Control Hub and Domain
  • Cisco Control Hub Premier license for the users.
  • For more details, contact Cisco Webex Support.

...

...

To deploy a Ribbon SBC Core standalone instance, refer to SBC Core 10.1.x Documentation.

Ribbon SBC High Availability

To deploy Ribbon SBC Core in HA mode on different platforms, refer to SBC Core Software Installation and Upgrade Guide.

...

set system security pki certificate SBC_CERT type local-internal
commit

Command to generate CSR on SBC
request system security pki certificate SBC_CERT generateCSR csrSub /C=IN/ST=KA/L=Bangalore/O=Sonus/CN=<common_name_for_tenant1> keySize keySize2K

After generating the CSR for tenant 1 on Ribbon SBC, provide it to the Certificate Authority. CA would generally provide the following certificates:
	SBC Certificate
	CA's Root Certificate
	Intermediate Certificate

Upload the certificates to Ribbon SBC at /opt/sonus/external and convert them into SBC readable format using openssl
i.e. SBC certificate must be in .pem or .p12 format and root certificate in .cer or .der format

Converting .crt to .pem using openssl for SBC Certificate.
openssl x509 -in sbc_cert.crt -out sbc_cert.der -outform DER
openssl x509 -in sbc_cert.der -inform DER -out sbc_cert.pem -outform PEM

After generating sbc_cert.pem file, convert it to .p12 format using below command and provide the location of the certificate key
openssl pkcs12 -export -out sbc1_cert.p12 -in sbc_cert.pem -inkey /opt/sonus/company_san.key.temp

Converting .crt to .cer using openssl for CA's Root and Intermediate Certificates.
openssl x509 -in root_cert.crt -out root_cert.cer -outform DER

After converting all these certificates, upload them to Ribbon SBC at /opt/sonus/external location.

Add the required certificates on SBC.

...

• When call hold is initiated from Webex client with ICE enabled, the Re-INVITE for inactive is not sent to PSTN leg.
• There is one way audio observed after off hold. This issue doesn't appear when we disable ICE on SBC, hence as a workaround solution ICE has been disabled on SBC until upcoming the SBC 10.1.x fix release is deployed.
• This issue is fixed in SBC V10.01.04R000 build.

Attended Transfer issue with ICE enabled

• PSTN calls Webex client1 with ICE enabled and after call transfer from Webex client1 to Webex Client2, observed no audio.
• This issue doesn't appear when we disable ICE on SBC, hence as a work around solution ICE has been disabled on SBC until upcoming the SBC 10.1.x fix release is deployed.
• This issue is fixed in SBC V10.01.04R000 build.

No Ringback Tone with ICE enabled

• When Webex calls PSTN, PSTN responded back with the 18x with SDP followed by Remote Ringback media packets, but SBC is not relaying those media packets to the Webex as a STUN request is not received from Cisco Webex.
• Cisco Webex does not send a STUN request during the Ringback stage.
• This issue doesn't appear when we disable ICE on SBC. As a workaround solution, ICE has been disabled on SBC until a fix release is deployed.

DNS query issue while Switching from Public to Local DNS

• DNS query for OPTION SIP OPTIONS request does not happen when the DNS server is changed from a public to a local lab DNS server.
• This issue is not observed on a public DNS server.

...

• Webex Client calls PSTN followed by multiple SBC failovers, and initiates BYE from Webex client to PSTN. An intermittent issue observed as SBC did Sometimes SBC does not relay the BYE request to PSTN leg.
• This issue is observed only after multiple failovers. During ; however, for single failovers, this issue is not observed.

Blocklisting Blocking Cisco node when INVITE gets 503 failure response

• When PSTN calls Webex client and Cisco node sends 503 response, the INVITE goes to the next available Cisco node but SBC does not add the failed blacklist Cisco node to a blocklistIP.
• This issue does not have any impact on calls.

Core Dump observed during failover with vnic VNIC down on VMware host server

• During failover cases, vnic VNIC on VMware host server was disabled to trigger a failover of SBC. A coredump occurred and Standby SBC did not activate. This issue is only observed when disabling the vnicdisabling the VNIC.
• During For failovers using initiated through CLIs or physical interfaces, this issue is not observed and failover succeedsworks fine.

These issues will be Some of the above issues have been addressed by Ribbon in their upcoming releasesthe forthcoming releases and the rest would follow soon.

Support

For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:

...