Well it is definatly a dial-peer issue. There is a call-forward pattern under the srst config, maybe that pattern is targeting things with a # at the end specifically. Something like .T# if it is, just change it to .T ;) . Also paste the running config!
Yeah, that's I'm trying now. I made the following changes yesterday before reading this.
no transfer pattern ..........
no call-forward pattern ..........
call-forward pattern .T
I'm having the end users test call forwarding to internal numbers and external numbers (internal just happen to have a 10 digit dialplan (yuck)), so I should know soon whether or not they still need a # to complete the string.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...