<p>"<strong>Hi, I've a wiered issue with CCM 6.1.<br />
In normal scenario, every 4 digit extension has its own DID and it appears perfect when making outbound calls from any extension. But if i enable call forwarding on any extension. The DID that comes to mobile screen ( after call forwarding ) isn't as it should be.<br />
Example scenario for one extension:<br />
For Extension 2156 .......DID is 4455856 and this appears same when i make outbound calls from 2156. Now if i enable call forwarding to my mobile number, the DID that appears on my mobile screen ( after call forwarding) is 4455899 whereas it should be 4455856. Now the more wiered thing is that for somee other extensions this call forwarding DID changes to 4455898.<br />
I've multiple sites having its own PRI gateway but with centralized CCM. and the above mentioned behaviour is occuring for all the sites. <br />
Just to tell you, For PRI CALL ROUTING INFORMATION- OUT BOUND CALLS: calling party selection = " ORIGINATOR"<br />
<p>I got a reply, to change the calling pary selection from Originator to Redirector.</p>
<p>Now i did replace this parameter with " First Redirect Number ( External)" and the result is quite surprising. Now if a user from inside calls to my extension ( with call forwarding to my mobile) the DID number that appears on mobile screen is always 4455800......Whereas if an outside users dials my extension the DID number on my mobile screen is the required one i.e. my own DID.</p>
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...