Randy Wu is a senior customer support engineer in the Multiservice Voice team at Cisco in Sydney. He has vast experience and knowledge configuring, troubleshooting, and designing Cisco UBE, gateways, and gatekeepers, working with H323, MGCP, and SIP protocols. He joined Cisco as a systems engineer in 1999. He holds CCIE certification (#8550) in Service Provider, Routing, and Switching and Voice.
The related Ask The Expert sessions is available here - Cisco Unified Border Element for PSTN SIP Trunks.
Click the Snapshots to view the Complete Recording of this live Webcast.
Configuring Cisco Unified Border Element for PSTN SIP trunks
A: If you only have one UC or CUCME, then you may not want to have cube unless you have other features like security. But if you have mutiple UC or CUCME sites, but have only one SIP Provider. Then CUBE can be part of your network.
A: CUCM 4.x has very limited support. CUCM Sip trunk integration with CUBE become more richer with CUCM version 5.x and 6.x. CUCM 8.5 version onwards Sip stack was developed more matured. It is recommended to use CUCM latest version to integrate with the Cisco CUBE.
A: Yes you can download from this link,
A: There is the Cisco Configuration Professional CCP 2.3 version which has the Graphical tool to configure CUBE.
A: Yes, Cisco UBE can do the early offer even if receives call from CUCM with delayed offer.
A: Both kind of Integration is supported. It will be based on the previous design of your network. If you already have SIP based fax server connected to CUCM its better to retain the configuration and dialplan, then you can integrate the CUCM trunk to CUBE.
A: Cisco CUBE can do the Delayed offer to Early offer convertion. In CUBE there is a parameter under dial-peer called codec offer-all. so even if you got delayed offer from CUCM without SDP, on the other side CUBE can handle and send the codecs as early offer with SDP.
A: Minimizing the transcoding resource usage is another reason to use G711 with CUBE.
A: CUBE is not able to use xcoer registered to CUCM, however you can configure DSP resource on CUBE itself and register to itself, hence CUBE will have available xcoder resource.
A: With new features & command, it will allow user to configure CUBE pointing to different SIP service providers for redundancy.
A: Cisco CUBE is an Integrated application with Cisco IOS software. CUBE functionality is supported in ISR 3800 series, ISR G2 series 3900 and 2900 series, AS5400, AS5400XM universal gateways and the Service Provider Gateways ASR1000 series.
A: Yes. If you select the MTP checkbox in the CUCM SIP trunk setting, and in the MTP configuration there is DTMF RFC2833 supported then in the SDP message DTMF payload type will be included.
A: CUBE SP edition is mainly used in the Service Provider network or large Enterprise network facing Service Provider to handle more voice sessions and high CPS ,for Enterprise Standard edition it will handle less of the sessions and low CPS. For SP level ASR CUBE supports up to 68000 sessions and 350 CPS in the high end box, for enterprise level it supports less sessions around 15000 and 50-150 CPS depending on the platform. In addition, the concept and configuration of CUBE SP edition is different than the Enterprise edition, please check ASR SBC 1000 series on CCO for more information of CUBE SP edition.
A: From CUCM 8.5 onwards , In CUCM SIP Trunk profile there is an option to enable the Early Offer and you dont even need to have the MTP resource. But in Pre-CUCM 8.5 versions you need to check the MTP box and make sure the Media resource is allocated in CUCM, then you can do the Early offer from CUCM to CUBE.
A: Refer the Best practises for using Cisco CUBE in the presentation link attached. From later CUCM 6.x onwards its recommended to use SIP for CUCM and Cisco CUBE. From choosing the Service Providers point of view, if the Provider can support SIP it will be better, but some providers only support H.323. In such case you have to use H.323 for integration.
A: Yes, you can convert to SIP trunk. You need to make sure provider can have all the functionalities like DID number etc. CUBE has no problem migrating to it.
A: If SIP provider requires regisration, then there is limitation. But if CUBE's limit is number of session for simultenous call. and number of call is limited depending platform you'll use
A: CUBE does support managing MTP resources inside the box.
A: CUBE does support authentication of invite from SP with latest feature.
A: If you have any existing Cisco Gateway then you can download the Cisco IOS supported version for running CUBE on your Gateway. Also you need to buy license for the no. of sessions in CUBE for different platform. Say for an example if you want to have a CUBE supporting 500 sessions , you need to buy the license for this amount.
A: With latest CUBE 8.8 version, It can pass through most of the messages
A: SIP-H323 interworking only support voice, not video yet.
A: CUBE voice call sessions are based on IP, the number of digital trunks depends on the performance of the CUBE platform, it can be up to 15000 sessions or even 68000 sessions in ASR platform
A: Yes. CUBE is in IOS based platform hence it can handle both Voice and Data traffic.
A: Yes. CUBE can work with TCL IVR script and Voice Xml application to provide IVR capability to IP calls.
A: Supplementary service , connection address c=0.0.0.0 or send for hold, privacy, ANI etc couple of things you can look for. Also, 180 or 183, reinvite, session refresh causes some issue.
A: It is depend on whether we are configuring media flow around or flow through, if it flow around then max session come up to 1000+ for flow through it may up to around 500 with cpu usage of 80%. (for ISR G2 platform, not including ASR platform)
A: Authentication has to be globally enabled. It will be under the global voice service configuration. Both registration and authentication can be defined under the voice services.
A: CUBE is just a functionality on GW, if you have normal GW connects to SIP Provider and then goes to another IP Leg like CVP or CUCM, it its the CUBE funcationality. You can use ISR or other GW with CUBE functionality IOS.
A: Not Necessary. It depends on the voice traffic you want to route using CUBE. For large enterprise its recommended to use standalone device for CUBE functionality. If the traffic is not high you can run other services along with the CUBE application for voice on the same platform simultaneously.
A: It is depend on whether you would like to install FXO on the router to turn it to a TDM gateway at the same time, you can install number of FXO ports based on whether there is enough DSP and slots.