I am facing one issue with CFA, I have one IP phone with DN 20XX and i have forwarded all calls to a mobile number (99XXXXXXXX), the issue is when i dial the DN 20XX internally i.e. from some other IP phone the calls gets forwarded to the mobile number, but when i dial the DID of my DN 20XX, instead of ringing on mobile, Phone with DN 20XX rings and CFA doesnt work.
Can any one please suggest what is the issue here?
Most likely the Telco is blocking the call because the calling ID is not a valid number assigned by your Telco. You can post here a debug isdn q931 to confirm this.
To fix it, you would have to implement translation rules on your VG to override the calling number to match a DID assigned by your Telco. Search in the form and you will find examples of how to implement this.
How is the DID configured to match up with extension 20XX? Is there a translation on the VGW? Or on call manager? Or is the phone set configured with 2 lines? one with the full DID and another with the internal extension? Have you done a DNA trace of the DID?
usually a telco wouldn't block the call like amine said, in my experience they just change the caller ID to the default number. If a telco was blocking the call you would probably be getting a busy tone. I think you're going to need a DNA trace of calling the DID.
On the gateway we are getting 6712XXX as a calling party number and we capturing the last 4 digits for extension so we made extensions with 20XX. No translation rules are configured in CUCM. and the PSTN gateway is MGCP.
Can you verify, on the gateway that deals with the forwarded call, what the setting is on OUTBOUND CALL>CALLING PARTY SELECTION. Is it set to Orginator? If so change to First or Last redirected number.
If Still no joy, kindly attach the cucm traces of a test call
============================= Please remember to rate useful posts, by clicking on the stars below.
Please remember to rate useful posts, by clicking on the stars below.
I have to agree with Brad here in that if your Telco were blocking the call, then you'd get a busy signal and your issue would be a bit more clear. In fact, you are describing a difference in behavior when calling a device from a different originating device. I have actually seen this behavior before but it was a low-level DB replication issue. That may or may not be the case here but its where I'd probably start. So, can you give the following:
How many nodes are in the CUCM cluster?
What protocol are you using for the PSTN gateway? MGCP or H323?
Take a look at the CUCM server registrations - i.e., what Subscriber is the target phone registered to vs. the originating device? Ex: Phone 1 and Phone 2 registered to same node - behaves as expected vs. Phone 1 registered to Sub 1 and Phone 2 (or Gateway) registered to Sub 2 - different behavior?
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...
[toc:faq]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 discusse...