You need to define a separate distinct range/pool of dialed numbers/cti route points for the Translation Route. These numbers should only be used for Translation Routing. You'll need more than one depending upon call volume and IVR port sizing.
You have not completed your Transtion Route configuration... a Translation Route is a Name of an Entity that has 1 or many Peripheral Targets/DNISs. So if you open you need a CTIRP X on your Call Manager that is used as trigger for your IVR This CTIRP X will be one of your DNIS values . So if you go to Translation Route Explorer and see you can add Peripheral Targets to the Translation Route. Read the instructions on Translation Routes More..
as just the means for the Call to get inside the IVR.
Plus.. from both an CCM and IPIVR Application CTIRoutePoint Trigger configuration you can limit or expand how many times the entity may be used.. This is important to learn because if configured wrong you can bottel neck your system and only allow less number of calls than you have configured DNIS's or Triggers.. Media Group is the other place that has a config piece on the IVR for this..
but bottom line is a Dnis is not Tied up during the entire Call time .. Its used to Single the IVR to provide a CTIPort to receive the Call on ...
It means I can have just ONE DNIS for every translation route and limit the number of times it is used by changing the MaxNumberOfSessions in the "TranslationRoute apllication" in the IVR and secondly change the number of IVR ports per JTAPI trigger and limit the number of calls queued per dialed number
I can only briefly respond due to time constraints at the moment. While you can configure more than one translation route under certain scenarios below is a typical customer scenario.
Assume the customer has one IVR with 40 IVR ports for queuing and call treatment for the CallCenter. A general configuration would be a single ICM translation route. You would need to define more than one DNIS (CTI Route Point) for the translation route to account for timeouts and call arrival rate. Let's use an example of 10. These CTI Route points, used only for translation routing a call to the IVR, would need to associated on the CallManager with the IVR JTAPI user ONLY. They do not have to be associated with the ICM PG user. You would create one Translation Route application on the IVR. You would associate the 40 port CTI Port group with the application. Set sessions for the application to 40. Associate each CTI Route Point (JTAPI Trigger) to the application. Set the sessions for each JTAPI Trigger to a "theoretical" 40. You would manage calls queued in the ICM.
You could have 40 calls active on the IVR at one time and a maximum of 10 calls in route/timeout to the IVR.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...