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

[Jonathan Charles]

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/24be689a/attachment.html>