PDF(363.7 KB) View with Adobe Reader on a variety of devices
ePub(371.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(431.5 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 30, 2017
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes the steps to be followed to troubleshoot when Cisco Unified Border Element (CUBE) is not discovered as Border Element in Prime Collaboration Assurance (PCA).
Cisco recommends that you have knowledge of these topics:
Cisco Unified Communications Manager (CUCM)
The information in this document is based on Prime Collaboration Assurance.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Steps to be Followed if CUBE is Not Discovered as Border Element in PCA
For a CUBE to be identified as Border Element in PCA:
a. Non-CUCM deployment: These conditions should be satisfied:
Condition 2: The SIP-UA-MIB should return value other than noSuchObject / noSuchInstance for SipCfgPeerTable.
Condition 3: The device IP address must be associated with the SIP trunk of one of the CUCM.
For a device to be identified as CUBE SP, it should be first identified as CUBE and it should respond to CISCO_SESS_BORDER_CTRLR_CALL_STATS_MIB.csbSIPMthdCurrentStatsAdjName (18.104.22.168.22.214.171.124.7126.96.36.199.1)
If these conditions are met and still PCA does not identify the device as Border Element, then verify if the configuration on CUCM and Device.
The CUBE-Side of the CUCM-to-CUBE Integration
When you first set up a CUBE, you must enable the router in order to route calls like a CUBE. This image shows a basic Voice Service VoIP configuration on a CUBE:
Here are some important points about this configuration:
The first line of the configuration is mode border-element, which enables CUBE on a router. Some devices do not have this configuration when they operate as a CUBE.
Allow-connections sip to sip enables the CUBE to accept Session Initiation Protocol (SIP) calls and route them as SIP calls. There are options for H323 as well.
Fax protocol t38 is a default configuration for ISR G2 routers. It is not needed for CUBE configuration.
Early-offer forced allows CUBE to route calls in a Delayed Offer to Early Offer scenario. Almost all of the providers require Early Offer SIP calls. It is actually recommended to send Early Offer from CUCM in order to avoid early media cut-through issues.
Midcall-signaling passthru is only for SIP-to-SIP calls. It is required for some supplementary services to work.
G729 annexb-all is optimal in cases where CUBE negotiates with providers who do not follow the RFC format for G729r8 and G729br8 codecs.
Dial-Peer Configuration on CUBE
Dial-peers on CUBE are like other dial-peers on Cisco IOS gateways. The difference is that the calls route from one VoIP dial-peer to another VoIP dial-peer.
Notice that there are two dial-peers here: incoming and outgoing. CUBE always matches two dial-peers. Incoming dial-peers are from the CUBE perspective, either from the CUCM or from the SIP provider. Outgoing dial-peers are sent towards the CUCM or to the SIP Provider.
ICisco recommends that you perform most of the digit manipulation on CUCM through Significant Digits, External Phone Number Mask, and Translations.
IP addressing on CUBE is accomplished the same way as on other Cisco IOS devices, but it uses the routing table in order to determine from which interface the CUBE sources SIP traffic. The show ip route A.B.C.D command provides information about the interface the CUBE uses in order to source SIP traffic. This is important when calls are sent to CUCM and when calls are sent to an SIP provider. Static routes might be needed in order to make this work.
In some cases, you might have to bind SIP to a particular interface, such as a loopback interface on the CUBE. SIP binding can cause side effects, such as when the CUBE does not listen for SIP traffic on a particular interface. Cisco recommends that you not use bindings and let the routing table decide, but this is not always possible. You can apply SIP bindings under Voice Service VoIP > SIP, or on individual dial-peers. SIP bindings are explained more in the Configuring SIP Bind Features article.
Voice-Class Codecs on CUBE
Voice-class codecs are used for CUBE in order to offer multiple codecs when calls use a particular VoIP dial-peer. This is the same as it was on a Cisco IOS Voice Gateway, but when it is a CUBE, codecs are filtered from one VoIP call leg to the other. It uses codecs that are available on both the incoming dial-peer and the outgoing dial-peer. The codecs that match both are sent offers. When CUBE receives a SIP message with Session Description Protocol (SDP), it also matches this against the voice-class codecs. This allows CUBE to filter codecs based on what is received from the SIP message with SDP, the inbound dial-peer, and the outbound dial-peer. The other SIP User Agent (UA) then responds to the codecs offered.
The voice-class codec in the previous image contains three codecs, g729r8, g711ulaw, or g711alaw. The image shows them in the order in which the Cisco IOS gateway prioritizes how the codecs are offered to the far end. Voice-class codecs are applied to dial-peers.
The CUCM-Side of the CUCM-to-CUBE Integration
In order to add the trunk to the CUCM configuration, navigate to this location:
Select Add New and proceed to set up the Session Initiation Protocol (SIP) trunk as shown here:
Within the trunk configuration page, remember to select the proper device pool that allows calls inbound to the particular CUCM server that accepts calls.
Once the trunk is created, ensure that the route patterns access it correctly either through a SIP Route Pattern or a Route List / Route Group setup.
The Redirecting Diversion Header can be ticked for inbound or outbound calls.
When External Numbers are forwarded into the VoIP Network, SIP invite messages come with relayed diversion information into CUCM. It shows the originating calling party. For example, if a call flow is integrated with UC and goes into voicemail, UC uses the initial diversion source (external forwarded number) as the destination mailbox. So it is possible that they could get the default opening greeting instead of the subscribers mailbox as expected. It depends on the call flow and requirements of your topology whether this is going to be required for the configuration.
The SIP profile for Early Offer is often needed when you connect the CUBE to a provider. If the trunk connects to another Cisco device, then you might not want to select the Media Transport Protocol (MTP) insert, based on the far-end devices. This image shows the SIP profile location and where to select the box for Early Offer.
Early Offer often helps to resolve early media issues that arise when you integrate the CUCM server and CUBE to other third-party products. It is also recommended within the Solution Reference Network Design (SRND).
If the profile is going to be modified, it is always best to create a new profile to use instead of the default profile.
Note: This checkbox is used when end users do not want to have an MTP used on every call.
It might be necessary to change from TCP/UDP for the protocol within the SIP security profile based on the call flow. In order to make this change, navigate to SIP Trunk Security Profiles > Non Secure SIP Trunk Profile:
Calls will fail, and CUBE/CUCM traces are required in order to understand what happens at the time of the failure, but this feature can be modified in order to confirm that it is not the cause of the problem. However, once this is modified, you must reset/restart the trunk in order to make the change occur.
In some circumstances, the External Phone Mask on the phone configuration might need to be added in order for the call to proceed, because some Telcos do not allow the call to proceed without the expected mask. In order to make this modification, go to the Directory Number (DN) configuration page of the calling party phone, make the change necessary for the box, and reset/restart the phone after the changes are saved.
Once this configuration is made on CUCM, initiate the cluster discovery on PCA.
The device will now be discovered as Border Element on PCA.