When I receive a direct call to my DN the call shows under the Missed Calls or Received Calls with the 9 prefix.
Now, when the call is received by another peer, attendant console or the caller dial my extension from the main greeting (which is handle by Unity) the prefix do not appear; therefore, I can't dial back using the Dial softkey option but instead I have to write down the number and dial out.
Has anyone experienced this issue? If so, could you tell me how to resolve it?
If this is accomplished with a translation pattern as described in the following link, it's possible that calls to the attendant console or Unity are not hitting the translation patter. Make sure that there is a pattern in place for these numbers.
Mike, I am aware of that workaround but I would like to know the behind the scenes configuration.
Bbuffin, That link won't apply to my system. As i said before, when the caller dial a Directory Number their number (the caller) shows up with the prefix 9. This problem is only when the call is transferred from an internal extension.
If I do what the document says then the person that can be reached directly from the outside will see the caller's number with two 9s instead of one; therefore, they won't be able to call out using that number.
I posted the link to ask if that was the way you currently have it setup to work with calls directly to your DN. You mentioned in your post that this scenario works properly. Is the procedure in the link the way you have this setup?
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...