I`ve been asked to investigate a stable Voice IOS for gateways using H323 using E1 circuit with Qsig. The gateways are only used for Voice with individual dial-peers to other GW`s though at a later gates to a central Gatekeeper -Any
Any recommandation for CVP 7 IOS? You may recall me having issue with dtmf when using 3 dtmf-types, it was fixed with chnaging the preference to use h245-alpha, however that does not work with sip on another deployment, so my only option is rtp-nte, which again causes some digit mis-interpretation. I am usong 12.4.15T8.
I don't work directly with CVP on a regular basis, but I do understand they require sticking strictly to the BOM and the last I checked I thought 12.4(15)T was the only approved train.
We have not had much in terms of RFC 2833 bugs on the gateway (some with CUBE), so it's possible that it's configuration or something else going on there. (You may want to try the 'voice service voip' command 'dtmf-interworking'). You may also want to make rtp-nte the last choice, which can affect some preferences.
I don't see the dtmf-interworking command as option, is this a hidden one or something?
What I had found with H323 is that when I had 3 dtmf types listed it would cause the issues, if I chnaged it to only list one it no longer misbehaved.
But now I am seeing the same issue with SIP even when only 1 type is listed (only tried nte-rtp) as the other ones are not working with SIP.
The issue is that I allow callers to enter 4 digits extensions at any time, and at times as soon as the first digit is collected to matches the menu option and routes the call immediately instead of waiting for additional digits.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.