Tuesday, April 22, 2014

Cisco CUBE and Broadview SIP trunks

I was tasked with turning up a SIP trunk from Broadview with little information from the customer or provider.  There is also no interoperability guide for Cisco CUBE and Broadview SIP trunks that I could find. The only reference on their website is to the now defunct Small Business UC500 product line.  With that, I blew a bunch of time trying figure out from the tech on the phone who didn't have access to the Broadview switch nor any information himself re: registration or authentication requirements, and from hunt, peck and debug techniques how to make a poor phone call work.

Short story regarding where I was side tracked: they don't want you to register with them, but only provide the authenticating credentials when presenting a call to them. No registrar required.  Also seemed I had to bind media and control to individual dial-peers.

With that, here's the critical pieces I found successful.

voice service voip
 ip address trusted list
  ipv4 XXX.XXX.XXX.XXX (CUCM server)
  ipv4 XXX.XXX.XXX.XXX (Broadview SBC)
  ipv4 XXX.XXX.XXX.XXX (CUBE LAN Interface)
  ipv4 XXX.XXX.XXX.XXX (Phone device network, probably unneeded)
 mode border-element
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 no supplementary-service sip moved-temporarily
 no supplementary-service sip refer
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
  registrar server
  early-offer forced
  midcall-signaling passthru
  sip-profiles 1000
voice class sip-profiles 1000
 request ANY sdp-header Connection-Info remove
 response ANY sdp-header Connection-Info remove

 credentials username TheUserNameThatTookTooLongToGetFromThem password TheAssociatedPassword realm aURLtheyThoughtMightWork.broadviewnet.net
 keepalive target ipv4:XXX.XXX.XXX.XXX:5060 (the Broadview SBC address)
 authentication username TheUserNameThatTookTooLongToGetFromThem password TheAssociatedPassword
 no remote-party-id
 retry invite 2
 retry response 3
 retry bye 3
 retry cancel 3
 retry register 10
 timers trying 1000
 timers connect 100
 timers keepalive active 100
 sip-server ipv4:XXX.XXX.XXX.XXX (the Broadview SBC address)


  1. Anonymous10:20 AM

    you are a life saver if you got this to work. do you suppose you could post the complete config.

  2. I don't have a config copy or access to the system any longer but if you have access to an old UC500 system, check out http://www.cisco.com/c/en/us/products/cloud-systems-management/configuration-assistant-cca/index.html. It's the administrative application for that product line and had a preset configuration designed to work with Broadview SIP trunks. It's where I gleaned what Broadview, at least at one time, was looking for from a Cisco configuration.

    If I get super motivated, I'll pump out a sample configuration for you.

  3. Fantastic articles is post by you in this blog. You give a nice thing. Thank you for such a nice article. Every word of this blog helps me to give detail to me.
    Visit: Voip Business Phone System