[cisco-voip] Busy Triggers and Max Calls for CTI ports

[Rasim Duric]

Thanks Jonathan. This is from the Cisco document ID: 59661

 

This problem occurs when the CRS issues the Consult Transfer request to
send a call from the CTI port to

the ICD device, it needs two sessions. One session is for holding the call
in queue and the other session is for

ringing the ICD device. In case the maximum number of calls is configured
as 1, the call transfer fails.

 

Rasim Duric

Network Analyst (CCS)

University of Guelph

Guelph, N1G 2W1, ON

519-824-4120x53146

rduric at uoguelph.ca

 

From: Jonathan Charles [mailto:jonvoip at gmail.com] 
Sent: September-04-08 12:14 PM
To: Rasim Duric
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Busy Triggers and Max Calls for CTI ports

 

Realistically, since JTAPI is going to control these ports directly, they
will never place a second call onto a CTI port in a JTAPI Call Control
Group, so this really is not an issue.


Jonathan

On Thu, Sep 4, 2008 at 10:53 AM, Rasim Duric <rduric at uoguelph.ca> wrote:

In my CCM 4.1(3) and IPCCX 4.0(5) environment CTI ports are being
generated automatically during a new JTAPI Call Control Group creation. By
default, the  Max Calls is set to 4 and Busy Triggers is set to 2 for
these CTI ports. Some Cisco documentation points out that the Busy
Triggers should be set to 1 and Max Calls should be set to 3 or more for
CTI ports. It appears that my CRS applications work OK with the default
settings but I'd like to have a consistent and correct configuration. 

 

Should I modify the Busy Trigger (from 2 to 1) for every CTI port? Thanks.

 

I do always set the Max Calls to 2 and Busy Triggers to 1 for my ICD
lines.

 

 

Rasim Duric

Network Analyst (CCS)

University of Guelph

Guelph, N1G 2W1, ON

519-824-4120x53146

rduric at uoguelph.ca

 


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080904/5496f9c9/attachment.html>