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?
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
You control that in your dial-peers. There isn't really an extra trick unique to SIP here. The IOS gateway will need to select an outbound dial-peer for any given call. The dial-peers will determine which path/circuit is selected, presumably based on the destination-pattern command.
