<div dir="ltr">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.<br><br><br>Jonathan<br>
<br><div class="gmail_quote">On Thu, Sep 4, 2008 at 10:53 AM, Rasim Duric <span dir="ltr"><<a href="mailto:rduric@uoguelph.ca">rduric@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-CA">
<div>
<p>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. </p>
<p> </p>
<p>Should I modify the Busy Trigger (from 2 to 1) for every CTI
port? Thanks.</p>
<p> </p>
<p>I do always set the Max Calls to 2 and Busy Triggers to 1 for
my ICD lines.</p>
<p> </p>
<p> </p>
<p>Rasim Duric</p>
<p>Network Analyst (CCS)</p>
<p>University of Guelph</p>
<p>Guelph, N1G 2W1, ON</p>
<p>519-824-4120x53146</p>
<p><a href="mailto:rduric@uoguelph.ca" target="_blank">rduric@uoguelph.ca</a></p>
<p> </p>
</div>
</div>
<br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>