12-11-2010 09:34 AM
hi all
our manger wants to Trunk Updating Huwaii it Present Sip Trunk , ihave already use 2811 after 1 mounth everything working well FAX ,DID, DOD, DTMF
!!!! suddenly DTMF Down im checking with Huwaii Tech Support he said must be Configure
dial-peer voice 101 voip
destination-pattern [15]...
voice-class sip dtmf-relay force rtp-nte
session protocol sipv2
session target ipv4:10.10.10.2
dtmf-relay rtp-nte
codec g711ulaw
but when im try configure DTMF yallow ican't find this mood
>>>>please what is way to configure this mood and what is the IOS Series and version support it >>
note my IOS is SP Services 12.4
thanks
Solved! Go to Solution.
12-14-2010 08:57 AM
You don't need to force the RTP-NTE. Just configure 'dtmf-relay rtp-nte' on the peers pointing this device. You can omit all the h245 and sip notify stuff like a previous poster had mentioned.
And also add an incoming dial-peer, since you need to advertise RTP-NTE capabilities on a call in from that device to this one:
dial-peer voice 1117 voip
description incoming SIP peer
incoming called-number /
session protocol sipv2
session transport udp
dtmf-relay rtp-nte
codec g711alaw
no vad
If you still have issues after this, collect the following for a failure where DTMF was pressed mid-call:
debug voip ccapi inout
debug ccsip all
debug voip rtp session name
12-14-2010 09:04 AM
Regarding the dtmf-relay force command. That's a hidden command. It's only neccessary if the other side doesn't advertise rtp-nte. Assuming your other peer is adverstising rtp-nte (which you can verify in the 'ccsip all' debug) you should be fine without it.
CSCek41147
CME does not offer RFC2833 back when it is configured on dial-peer
CSCsg30101
CME: dtmf-relay force rtp-nte CLI does not work
12-12-2010 09:13 AM
I found this command related to CME only.
IOS versions used in examples are 12.4(11)XJ or IOS 12.4(6th)T.
I've a question.
What type of DTMF relay are supported by your Huawei gateway?
The command "dtmf-relay rtp-nte" sets RFC2833.
Try with sip-notify also or use a combination of two:
dtmf-relay rtp-nte sip-notify
Cisco supports many methods:
voice-gateway(config-dial-peer)#dtmf-relay ?
cisco-rtp Cisco Proprietary RTP
h245-alphanumeric DTMF Relay via H245 Alphanumeric IE
h245-signal DTMF Relay via H245 Signal IE
rtp-nte RTP Named Telephone Event RFC 2833
sip-kpml DTMF Relay via KPML over SIP SUBCRIBE/NOTIFY
sip-notify DTMF Relay via SIP NOTIFY messages
RFC2833 method can be adjusted with these additional options:
voice-gateway(config-dial-peer)#dtmf-relay rtp-nte ?
digit-drop Digits to be passed out-of-band and in-band digits dropped
voice-gateway(config-dial-peer)#dtmf-interworking ?
rtp-nte Digit-begin and digit-end events of RTP NTE packets are sent separately
12-12-2010 11:38 PM
12-13-2010 11:47 AM
In the file attachment are present many SIP dial-peers and are configured all dtmf relay methods.
Try to remove h245-alphanumeric and h245-signal. This methods are used in H.323 dial-peers and are not supported by all SIP gateway.
Regards.
12-13-2010 11:30 PM
hi
im try to remove h245-alphanumeric h245-signal but still the same thing
so my Qustion there one guy in Huwaii told me configure this DTNF mode voice-class sip dtmf-relay force rtp-nte
please advise me
12-14-2010 08:57 AM
You don't need to force the RTP-NTE. Just configure 'dtmf-relay rtp-nte' on the peers pointing this device. You can omit all the h245 and sip notify stuff like a previous poster had mentioned.
And also add an incoming dial-peer, since you need to advertise RTP-NTE capabilities on a call in from that device to this one:
dial-peer voice 1117 voip
description incoming SIP peer
incoming called-number /
session protocol sipv2
session transport udp
dtmf-relay rtp-nte
codec g711alaw
no vad
If you still have issues after this, collect the following for a failure where DTMF was pressed mid-call:
debug voip ccapi inout
debug ccsip all
debug voip rtp session name
12-16-2010 02:31 AM
thanks alot
the problem has been solved
12-14-2010 09:04 AM
Regarding the dtmf-relay force command. That's a hidden command. It's only neccessary if the other side doesn't advertise rtp-nte. Assuming your other peer is adverstising rtp-nte (which you can verify in the 'ccsip all' debug) you should be fine without it.
CSCek41147
CME does not offer RFC2833 back when it is configured on dial-peer
CSCsg30101
CME: dtmf-relay force rtp-nte CLI does not work
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