CTI Port vs CTI Route Poin

Could someone plese describe the difference between a CTI Port and a CTI Route Point?
Thank you

The documentation for CTI RP has an explanation
A computer telephony integration (CTI) route point designates a virtual device that can receive multiple, simultaneous calls for application-controlled redirection.
For first-party call control, you can optionally add a CTI port for each active voice line (the CTI application determines this). Applications that use CTI route points and CTI ports include Cisco IP Softphone, Cisco Unified Communications Manager Auto-Attendant, and Cisco IP Interactive Voice Response System. After you add a CTI route point to Cisco Unified Communications Manager Administration, information from the RIS Data Collector service displays in the CTI Route Point Configuration window. When available, the IP address of the device and the name of the Cisco Unified Communications Manager with which the device registered display.
CTI Route Point Configuration
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/b06ctirp.html
HTH
java
if this helps, please rate

Similar Messages

Cti port and cti route port on CUCM

I always confuse the meaning and usage of cti port and cti route port, can somebody explain to me? thanks.

when i got the explanation on this the 1st time this is what they told me:
the CTI route point is a virtual device that is always available and handles the call until the JTAPI app (UCC, CUE, 3rd party VM, etc)
this is where the call is answered, where it's put on hold, etc.
the purpose of the CTI route point is to have a DN that can take all the calls. The CTI RP also communicates with the JTAPI app to let it know that it got a call and asks what to do with it. the JTAPI app at some point tells the CTI RP to send it to a CTI port
the CTI Port is just like a phone line, it takes the RTP stream and is where all the interaction takes place, you enter your ID, information, password, etc.
it can only take one call at a time and the number of CTI Ports an app has registered equals the max number of call it can take at any given time
HTH

UCCE 7.5.1 - CTI Route Point and CTI Ports not registering in UCM 7.1

We are in a middle of a new installation of UCCE 7.5.1. The customer will use it only for Outbound calls. The design is to have on PROGGER and one AW, with a cluster of two CallManagers. All the setup has finished regarding the UCCE. Also, the CallManagers have been configured, regarding the CTI Route Point and the CTI Ports. All of these are associated with the PG USER which is CTI Enabled. Configuration on UCCE has been done, including the DIALER, except for the agents and the campaigns.
The problem is that the CTI Route Point and the CTI Ports on CallManager are not registering. Is this normal, since the agents and the campaigns have not been configured yet or there is an error somewhere?

Looks fine.
Is the Dialer running? Maybe those 30VIP phones the Dialer uses as ports to dial from won't be registered until the Dialer starts.
But they should also be registered if you start dialogictest over the full set.
What's the "route point". Who asks for it? Is it a dialed number that runs a script?
Regards,
Geoff

CTI route point and CTI ports not registering - UCCX 10.5 and CUCM 10.5 - PARTIAL SERVICE

I'm trying to integrate CUCM 10.5 and UCCX 10.5.
For some reason CTI route point and CTI ports are not registering on the CUCM and the status of the UCCX is "PARTIAL SERVICE".
On the UCCX Cisco Unified CCX Engine is in status "PARTIAL SERVICE" and the Unified CM Telephony Subsystem shows status "OUT OF SERVICE".
I tried with completely new installation of UCCX twice and got the same result twice.
But when I tried integrating UCCX 10 with the same CUCM 10.5 from above everything works fine and all the ports are registering right away.
In all the cases I have done the same configuration.
The versions of CUCM is 10.5.2.10000-5.
The version of UCCX is 10.5.1.10000-24.
The version of UCCX 10 with which it works fine is 10.0.1.11001-37.
Does anyone have an idea what might be the problem?

No I haven't. Unfortunately I don't have a 32bit Excel at the moment to try.
Can you please tell me this: I'm installing a new BE6000 system that came with this problematic version of UCCX (10.5.1.10000-24). I have been testing during the weekend with 3 versions of UCCX:
-10.0.1.11001-37
-10.6.1.10000-39 and
-10.5.1.10000-24
I got the best results with version 10.0.
Can I install that version (10.0) in BE6000 instead of the one that came preinstalled (10.5.1)?
This is my first BE6000 installation and I'm not sure if this is OK?
I installed a newer version of CUCM than the one that came preinstalled because I hit bug CSCup60269 but I'm not sure If I can go to a lower version for CCX.

Cti port , cti route point, and application user

Hello,
Can someone explain the reason why we use cti route point, cti port, application user for ucce. What is the function of each one when integrating with a ucce call center?
Thanks,

I guess you are using CVP as front end VRU, where CVP treats customer with prompts and when customer chooses to talk to agent, CVP delivers call to agent with the help of the ICM.
so you need to understand CVP call flow first,like how call traverse different application(VG,CVP,ICM,CUCM) in unified CVP environment(specifically comprehensive call flow model).
then you need to do configuration walkthrough in your environment like check the dial-peer on the VG and see how call comes in, what dial-peer it matches, how number gets translated using translation pattern and where it routes (CVP,CUPS,CUSP etc)
go to next device and once again check the configuration, this is how you can determine flow of your call.
below link may help to you:
https://supportforums.cisco.com/document/6131/detailed-sip-call-flow-cvp-comprehensive-model
Regards
Chintan

CSCts69270 - CCX CTI ports may stuck in out-of-service state when UCM Upgrade/Restart

Symptom:
CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.
Conditions:
During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .
This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;
The CUCM sate of down ports is "Registered".
The UCCX state of down ports is "Out of Service"
This was tested on following Release branch;
CUCM Version: 8.6.2.10000-30
UCCX Version: 8.5.1.11001-35
JTAPI Version: 8.6(2.10000)-2
CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.
UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.
Workaround:
After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.
Last Modified:
Aug 26,2013
Symptom:
CCX CTI ports (RP & IVR) may stuck in out-of-service state during CUCM upgrade or Restart.
Conditions:
During CUCM upgrade the The UCCX CTI ports (RoutePoint Triggers and few IVR ports) went into out-of-service state .
This condition may happen during CUCM upgrade process or CUCM nodes restart. When this happens;
The CUCM sate of down ports is "Registered".
The UCCX state of down ports is "Out of Service"
This was tested on following Release branch;
CUCM Version: 8.6.2.10000-30
UCCX Version: 8.5.1.11001-35
JTAPI Version: 8.6(2.10000)-2
CUCM is a 15 Nodes cluster over the LAN with 10 subscriber nodes.
UCCX is a 2 Nodes-HA Cluster, with one Route point, and 300 ICT IVR ports.
Workaround:
After Upgrade completes, restart of CTIManager service from the CUCM nodes serving the CCX.
Last Modified:
Aug 26,2013
Known Affected Releases:
(0)
Known Fixed Releases:
(0)

Hello r.mata, do you have a question about this bug? Regards, Wes

UCCX 8 and CTI ports in UCM

Hi! I try to configure UCCX.
First of all, how many CTI port shoul I setup in Call Controll Group? Is it anought to setup one CTI port for all 10 agents?

Hi
The system works like this:
1) Call hits a 'CTI route point', which is shown as a 'trigger' in UCCX. Think of that as a pilot number.
2) Before UCCX can do anything, it sends the call from CTI Route Point to a CTI Port.
3) On the CTI Port, the call is answered, and the scripts you define run. The call will stay on the CTI port until it is transferred out of the system OR to an agent, or the call ends.
4) When the call goes to an agent, the CTI port is no longer used.
So - typically you would have at least as many ports as agents. What the number of ports affects is the number of simultaneous calls that the system can have queueing or being prompted or held at once. How many you need depends on a lot of factors...
- If your agents take long calls, calls may come in several at once and queue for a long time
- If they have low staff periods (i.e. the big team lunch in the pub every day) calls will probably queue a lot
- If you have a lot of agents, and short call and queue times, you may not have a lot of calls queueing generally
- if you have a complex menu system or a lot of prompts before callers get to an agent, your CTI ports will be used for a longer time, and are therefore subject to more congestion
Generally you license the sytem per agent, and try to over provision the ports as it's difficult to predict what is needed. Consider the number of agents you have, and the number of possible inbound calls (i.e. number of inbound channels on the PSTN circuits used for the Contact Centre numbers), and the capabilities of whatever system you are replacing.
If you have 10 agents and a single PRI, and your license lets you add 20 or 30 ports, I would do it.
Sometimes customers get new licenses and add more agents, but they will never remember to set up more CTI ports... if they have more to start with, that's not problem.
Regards
Aaron
Please rate helpful posts...

UCCX CTI PORT

Hi Team,
CTI ports are register with the CUCM ip instead of UCCX . There should be UCCX IP , Whts wrong ?
Regards,

try deleting the Call Control group from CCX.then, from Call manager, delete these CTI ports which would go in UNKNOWN state.
do not delete Trigger /Route point.
now, re-create Call control group in express with same CTI port range and associate same Trigger.
regds,
aman

When do the CTI ports between CUCM and UCCX get created

Hi All,
I am trying to work out when the CTI ports between CUCM and UCCX get created.
Do they get created during the post installtion wizzard when you selectthe number of HR licenses or do you need to manually create the CTI ports after the post installation wizzard.
Many thanks for any help
Regards

In new versions (since 4.x) UCCX creates the CTI route points on Call Manager when a trigger is added on UCCX side.
When you add a Call Control Group on UCCX side, that process creates all the CTI ports in CUCM automatically or updates the existing ones if you change settings for the call control group.

Problems to registering CTI ports

Hi to all,
I'm trying to do a upgrade from CUE 2.3 to CUE 8.6. The installation was ok, but the CTI ports and route point isn't registering in the CUCM server, this server is a 8.5 version.
Before we had a CCM 4.2 and CUE 2.3 with the same configuration and the all was working fine, but when we did the upgrade all is working but the CTI port isn't registering. The GW and the CUCM are in two diferents subnet and have open access for all ports....
Any idea??
Thanks..
P.D.: Sorry but my english is very bad,

Hi David,
You english is perfect my friend so, no worries
When you move past CUCM 5.x the integration with CUE changes as well, did you
follow the steps in this good doc?
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configuration_example09186a0080289ef0.shtml#cm5andlater
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen

UCCX CTI Ports - range suggestions?

We used CTI ports starting with a 9 and we
put the CTI ports and route points
in a separate partition so they are not in the same partition as what the customer would dial out to the PSTN,
so that there would not be a conflict with 9.X route patterns. This works.
Is there any standard practice on what ranges
CTI ports should be in? I keep seeing in 4 digit
dial plan the least used is 9XXX.
and if Cisco recommends avoiding
certain DN ranges like 9XXX
for UCCX CTI ports

Well, everyone will have their own methods and reasons for choosing said method. Cisco won't have a specific recommendation nor should they really. My approach in North America is pretty straight forward. If the customer has a pre-conceived notion or existing design I will take that into consideration. People get used to doing things a certain way and if there are no conflicts I choose not to pick a fight. Mainly because I have plenty of other design points that are more important.
If the customer has no opinion or their proposal is not workable, then I typically default to using a 7-digit plan with a leading "1" in the 7th digit. This is because the NANP excludes 0 and 1 in the NPA and NXX portion of the phone number. Meaning, you will not see an area code or exchange that starts with a 0 or a 1. I try to incorporate that fact into my dialplan. Particularly for "software" or "application" numbers. So, Unity ports, UCCX CTI RP/CTI Ports, etc.
I used to be more stubborn about these aspects of the dial plan but now I have loosened up some. What I like to do (in NANP) is to lay out a 10-digit solution using the customer's DID and a private numbering standard using the leading "0" or "1" digit approach. I find that most customers already have a range of numbers they reserve for private numbering. I try to tap into that and expand it if I can.
All that being said, personally I would stay away from using a digit that is also known as the "steering" or trunk access digit (typically "9", but I have also seen "8" used). The reason I steer clear of this assignment is because I have been pulled into customer issues where they lost secondary dial-tone. Which typically means they assigned a "9" (or other as applicable) as a leading digit to an extension, mml, or UCCX port. For some strange reason it always falls into one of those three buckets. Now, it should be said that if your dialplan approach has a hierarchy built-in then using a "9" is non-issue. Sounds like you have worked that out. So, not sure you need to tweak it.
HTH.
Regards,
Bill
Please remember to rate helpful posts.

CER 7.x CTI Ports don't register

I know I must be missing something but can anybody think of a reason why CTI Ports configured for CER won't register? The CTI Route Points do register and both the route points and ports are associated with the same cti enabled end user account.. Running CER version 7.x and cucm version 7.1.3
thank you...

I have a mac mini (A1283) with OS 10.7.4. Upon upgrading to 10.7.5 it did not start up again. Instead, the light was on and the hard drive did not start up. The light on the connected USB mouse was not lit.
My solution:
Cold start with Command-v pressed.
This should start Verbose mode (see http://support.apple.com/kb/HT1492 ).
What happened on my mac mini was that the grey startup screen with the Apple logo appeared for a long while before the login screen came.
Maybe Cmd-v set open firmware params and fixed some corruption.
Anyway: my mac mini works again.

UCCX8 Is there a log or report that shows IVR/CTI port availability over time

Question:
Is there a log or report that shows IVR/CTI port availability over time?
Objective:
We are trying to determine if, when doing a Call Redirect step, the IVR/CTI port stays the same or the port is made available by the first script and the second script, where the Call Redirect is redirecting to, has to reserve its own IVR/CTI port.
What we have done already:
We limited the Call Control Group to 1 CTI port and ran the scripts that do the Call Redirect step and it worked fine, so we are assuming that there is not a point where the transfer takes up two IVR/CTI ports at the same time.
-Lauren

Hi,
if it's UCCE, then if I remember that correctly, there is a webview report that would tell you Network Trunk Group utilization. Or, actually, you can extract this information yourself from the HDS table named Trunk_Group_Half_Hour.
G.

Can't import CTI Ports in CUE 3.1

Hi Everyone,
I have recently migrated CallManager 4.1 to CUCM 7.1. Everything is working fine but CUE is not able to integrate with CUCM 7.1
I have provided the new credentials for Admin User and JTAPI user in CUE 3.1 and also made a new application user in CUCM 7.1.
When I verify CallManager Admin User in CUE web interface it shows Admin login successful, JTAPI login successful.
But when I try to search and import CTI Ports from CallManager, it shows me the error IOException: No such attribute.
Can anyone please help me with this issue?
Thanks,
Amit.

Hi
See this compatibility chart:
http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/compatibility/cuecomp.htm#CUCM
To run CM7.1, you need to be running 3.2.1 of CUE as a minimum.
Regards
Aaron
Please rate helpful posts...

Synchronization problem MoH in CTI port

Hi
I have a problem with the synchronization of User Hold Audio Source and Network Hold Audio Source in the CTI Ports. The callmanager cluster is 6.0.1.2121-1 and UCCX 5 versio.
After doing a Data Resync the result is User Hold Audio Source-- UUID changed from {AC0250B0-6F23-4D91-A73B-A733B011C5CE} to {31E8EA9C-57832-43F7-8384-4C6351A97110}.
Attached is a picture about the result of Data Resync process.
Thanks in advance.
Regards.

MOH issues can be tricky, but let's start with a couple of assumptions:
1. You are running a single CCM cluster
2. The callers coming into the UCCX system are all using the same MRGL
3. If you're using Multicast for MOH, then you have multicast properly set up.
4. You have the MOH audio source files loaded on all the servers where it needs to be (must be loaded on each MOH server individually, these do NOT replicate).
I make the above statements because if any of the above are not true, you can have issues, and while they may manifest on UCCX, they are not UCCX problems.
If you have the data resync/check coming up clean, and it's still misbehaving, open up the call control groups and make some small modification to them...change the description or something so that it will delete all the ports and then rebuild them. Make sure you open up the more info and confirm the settings are where you want them to be. The existing ports will get deleted and then rebuilt. This will resolve any issue where someone modified something directly on CCM that could potentially cause your issue.

CTI Port vs CTI Route Poin

Similar Messages

Maybe you are looking for