Currently, there is nothing in 3.2 or 3.3 for authentication codes. There are a couple of third party applications that use an IVR function to give you this. Last I heard from Cisco SE's, this is still something that they are looking at, but that it would not be here until CY2004.
I tried this workaround and it works find all you need is a little extra effort to defind different PIN but the problem is in the 7940 and 7960 phone. If you go to the directory - Placed Call - you can see the number dial by the user on the directory including the predot number that you enter. So it means that everytime you a user dial using the dialing pattern with PIN, you need to instruct the user to clear the history on the directory.
We have working the workaround from eight mounths ago, we have defined different PIN but it's vulnerable the problem is in the 7940 and 7960 phone. If you go to the directory - Placed Call - you can see the number dial by the user on the directory including the predot number that you enter. So it means that everytime you a user dial using the dialing pattern with PIN.
Now we need any software for to protect the Call(placed and new), Pls. Cisco can send me any answer?.
You can use CRS 3.X running on a separate server or co-located on CallManager. Basically you can configure all LongDistance or International calls to go to go to the IVR, you enter your pin which looks at a table in SQL and sends the call. Only number you will see in the Placed calls directory is the outbound number and not the PIN. Up until CM 3.0 the placed call directory would only show the number that was sent to the gateway. Unfortunately this functionality was lost and according Cisco has no chance of returning anytime soon. This feature has been requested via TAC though. Again, your only option is to use CRS/IVR to implement PIN Codes. Email me at firstname.lastname@example.org and I can send you the ivr scripts you need to make it work. All you have to do is by the server and the software.......
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...