Starting with CCA 3.1, the preferred DTMF method is RFC 2833. For systems starting from factory default, CUE will be reconfigured with rtp-nte and this will be reflected on any dial-peers targeting CUE. Additionally, existing systems which update their SIP trunk will also be updated on both sides.
However, there is a known defect with CCA 3.1 (CSCtr84220). When making any changes from the Voicemail UI, CCA will unfortunately reconfigure only the CUE DTMF without updating the dial-peers. There is a plan to fix this in the very next release of CCA (existing configurations should be able to continue to use sip-notify). But after hitting this issue, you will need to either update CUE dial-peers from CLI (dtmf-relay rtp-nte) or from CCA by resetting the voicemail and/or auto attendant numbers to get those dial-peers updated.
dial-peer voice 2001 voip
description ** cue auto attendant number **
translation-profile outgoing PSTN_CallForwarding
session protocol sipv2
session target ipv4:10.1.10.1
voice-class sip outbound-proxy ipv4:10.1.10.1
dtmf-relay sip-notify ••ß Modify/Change this setting. New Value – dtmf-relay rtp-nte.
This will need to be done for all Dial-Peers accessing CUE. (AA, VM pilot, Prompt Management)
To emphasize what Richard has mentioned in the post, the workaround in CCA is to update the extension and/or PSTN numbers for any previously configured Voicemail / Auto Attendant.
ICan someone help me understand what does this mean specifically :
" update the extension and/or PSTN numbers for any previously configured Voicemail / Auto Attendant"
Is this beyond manually adjusting the dial peers?
Please describe an example of this workaround?
Do I change the AA Extension to something else and then change it back?
When is the updated CCA due out without this bug?
Yes, what we mean by "reset" the voicemail or auto attendant number from CCA is to change the extension to something else and then change it back. CCA will regenerate the dial-peers with the matching dtmf-relay method (rtp-nte).
Thank you Laura.
Sorry if it was obvious to everyone, but living on the other side of the Cisco Firewall shows me how important full and verbose communications are.
I hope you are doing well. Please say hi to everyone for me.
I don't believe this issue has been resolved for auto attendant as I've recreated my auto attendant with a different extension and set it back and it still has an issue where the voicemail box cuts off after 2 seconds. I'm using CCA 3.1.1 and changing the user extensions fixed their problems, but the auto attendant is not fixed by doing this.
Any help would be greatly appreciated!