Preview Tool

Cisco Bug: CSCui94087 - SIP Binding on CUBE is documented incorrectly

Last Modified

Mar 07, 2018

Products (1)

  • Cisco Unified Customer Voice Portal

Known Affected Releases

8.5(1) 9.0(1)

Description (partial)

SRND is not reflecting the correct setup for CUBE binding.  SRND says: 

"When configuring the gateway, it is best to bind the H.323 or SIP signaling to the virtual loopback interface, as illustrated in the following configuration examples:
This configuration allows call signaling to operate independent of the physical interfaces. In this  way, if one interface fails, the other interface can handle the traffic. Each gateway interface should  be connected to a different physical switch to provide redundancy in the event that one switch or  interface fails. Each interface on the gateway is configured with an IP address on a different subnet.  The IP Router(s) for the network is then configured with redundant routes to the Loopback address  through the use of static routes or a routing protocol. If a routing protocol is used, pay careful  attention to the number of routes being exchanged with the gateway, and consider using filters to  limit the routing updates so that the gateway is only advertising the loopback address and not  receiving routes." 

The correect setup should be:

"CUBE supports bind at the dial-peer level and would recommend that instead of the global bind under voice service voip. With dial-peer level bind it is possible to setup separate binds for the SIP trunk side and one for the internal network."

Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.