11-22-2018 07:08 AM - edited 03-17-2019 01:45 PM
I already have a H.323 gateway configured on my CUCM with E1 PRI but now I want to also bring in SIP but I don’t want to do any SIP trunk configuration on the CUCM i want to make sure that any configuration am going to do will be on the voice GW. How do I go about the configuration?
Solved! Go to Solution.
11-25-2018 11:28 PM
11-22-2018 09:50 AM - edited 11-22-2018 09:52 AM
This is a bad idea. You’re forcing a protocol translation unnecessarily which frequently leads to corner case interop issues (eg DTMF, early media, etc). I recommend converting the H.323 gateway to a SIP trunk instead; it’s perfectly normal to have ISDN circuits with a SIP trunk into CUCM from the IOS gateway. There are years of threads on this topic here on the forums but it’s essentially only a few config changes to your CUCM-facing VOIP dial peers to use SIP instead of H323 and update the DTMF relay options.
dial-peer voice 10 voip
session protocol sipv2
session target dns:hostname.domain.tld:5060
session transport tcp
voice-class sip options-keepalive profile 1 ! Omitted from example
voice-class sip bind control source-interface Loopback0
voice-class sip bind media source-interface Loopback0
dtmf-relay rtp-nte sip-kpml
codec g711ulaw
ip qos dscp cs3 signaling
no vad
For the new SIP trunk toward the carrier, here are a few working config examples to get you started:
https://www.cisco.com/c/en/us/solutions/enterprise/interoperability-portal/networking_solutions_products_genericcontent0900aecd805bd13d.html
The infamous CUBE config guide:
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-cube-overview.html
11-22-2018 11:58 PM
11-23-2018 05:42 AM
11-25-2018 12:33 PM
11-25-2018 11:28 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide