Showing results for 
Search instead for 
Did you mean: 

DTMF Relay question between SIP and H323

Tommer Catlin

Im working on some CUBEs and they are working great with my provider, CUCM and phones.  But I have an issue coming across a GK site from a remote CUCM cluster via H323.   When the call goes from CUCM---GK---CUCM---CUBE----SIP Provider, my DTMFs are dead.  But if I go from my CUCM----CUBE---SIP Provider, DTFM is fine.

I have on my dial peer in CUBE:  DTMF-relay RTP-NTE.   Im wondering if I should either change this to dtmf-relay h245-alphanumeric or should I create a seperate dial-peer just for the inbound H323 calls from my remote GK clusters that will use dtmf-relay h245 and leave my CUCM SIP incoming on RTP-NTE?


3 Replies 3


You can have multiple dtmf-relay on dialpeer.  You could try dtfm-relay rtp-nte h245-alphanumeric h245-signal.

Yeah, that’s what I was going to do next.

So how would it look then? All my calls from CUCM look like this:

dial-peer voice 1 voip

description lan side dial peer

preference 2

session protocol sipv2

session target ipv4:x.x.x.x

incoming called-number 5000

voice-class codec 1

voice-class sip options-keepalive up-interval 100 down-interval 50 retry 6

voice-class sip bind control source-interface GigabitEthernet0/2

dtmf-relay rtp-nte

Do I create another dial-peer with alphanumeric then?


Just the change the dtmf-relay line to

dtfm-relay rtp-nte h245-alphanumeric h245-signal

Some times you have to change the rtp payload type  depends on what event Service provider supports.

We had to add these lines in the outbound/inbound dial-peers.

rtp payload-type nse 127

rtp payload-type nte 100

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers