We have a multi city environment where they dial 9 for local calls and 8 for LD.
If a person in City A puts 9+local cell phone in their call forward all and a person from City B calls them. The call will use the callers (City B) local trunks to send the call. Since 9 is for local the call will be directed to the local trunk in City B and the call will fail because the local truck does not allow LD. If instead the person in City A puts a 8 in front of the number then calls in the local Site at City A will fail.
What I have been trying to do is use the Call Forwarding CSS to correct this via TP with no luck.
Is there a way to predot the call based on the calling number and the destination and then I could just have the people us the 10 digit number for call forward all? Thoughts on another way to accomplish this?
Unfortunately that will not work because of the 8 vs 9 issue. What I have come up with it to separate the PT/CSS of the CFA and send all the calls out an LD circuit. Problem is I cannot differentiate the location of the caller location since the called persons CFA CSS is what the call is using. If I set the callers CSS to modify the predot then I am breaking the policy of making people dial an 8 for LD so that they know they will be billed for LD.
So the politics is that if someone forwards a call to there cell, it should be local only and TEHO should cause the call to be non-billable.
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...