Friday 27 December 2013

How to Read the Cisco Traces -- H.323

This  is a very valueable documentation that has been created by TAC which is helpful in reading the traces -- follow this to isolate the issue further -- when it is related to traces issues :


https://supportforums.cisco.com/docs/DOC-11779

Also as a prelude to this -- try to follow the below mentioned document to enable traces :

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080094e89.shtml#calm



How to gather logs with RTMT :


Follow this link to get the step-by-step process to download the traces : 





Monday 9 December 2013

CTI Route Point or CTI Port Confused ???

I and a lot of people seem to be confused over the usage of the CTI Route Point and CTI Port.

Below are the differences :


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 ports are the number of licenses you have allowing you that many CTI connections.


CTI RP is the DN or number that is associated with your CM that will take phone calls or that is the number where you load your applications.


-=-=-=-==-=-=-=-=-=-=--=
A CTI Port is a virtual port. It is analogous to a trunk line in a traditional ACD or PBX setting. i.e The CTI Port allows access to the Post Routing capabilities of the IP-IVR.

A CTI Route Point is a virtual device that can receive multiple simultaneous calls for the purpose of application-controlled redirection. Once a CTI Route Point has been created, lines (directory numbers) can be added and configured. Applications that use CTI route points include the Cisco IP Interactive Voice Response (IP-IVR) system and Cisco JTAPI with ICM. Calls are directed to CTI Route Points, which subsequently route the call to an available CTI port, the front end of the application. A CTI Route Point is the number a caller dials to access the application. A CTI Route Point must be configured for each application.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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

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.
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


Note: If you configure multiple lines per CTI port, only one line per CTI port can be in use at a time. Media
can only be terminated per device, notCUCM Administrator >  Device > CTI Rou per line.

.-==-=-=-=-=-=-=-=-=-=-=-==-=-=-=

Device : Route Point.

Type of Device > CTI Port 
















Saturday 7 December 2013