<div dir="ltr">OK, but here's the thing...<br><br>Since IPCC 4/5/6/7 all directly control and create the CTI Ports and route points, any change you make to the ports would get overridden by IPCC anyway during the next resync.<br>
<br>And, since there is no option to edit the max calls and busy trigger on the JTAPI Call Control Group config, I wouldn't touch it.<br><br><br><br>Jonathan<br><br><div class="gmail_quote">On Thu, Sep 4, 2008 at 11:40 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 style=""><span style="font-size: 11pt; color: rgb(31, 73, 125);">Thanks Jonathan. This is from
the Cisco document ID: 59661</span></p>
<p style=""><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p style=""><span style="font-size: 11pt;">This
problem occurs when the CRS issues the <b>Consult Transfer </b>request to send
a call from the CTI port to</span></p>
<p style=""><span style="font-size: 11pt;">the
ICD device, it needs two sessions. One session is for holding the call in queue
and the other session is for</span></p>
<p><span style="font-size: 11pt;">ringing the ICD device. In
case the maximum number of calls is configured as 1, the call transfer fails.</span><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p><div class="Ih2E3d">
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Rasim Duric</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Network Analyst (CCS)</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">University of Guelph</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Guelph, N1G 2W1, ON</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">519-824-4120x53146</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"><a href="mailto:rduric@uoguelph.ca" target="_blank">rduric@uoguelph.ca</a></span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
</div><div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0cm 0cm;">
<p><b><span style="font-size: 10pt;" lang="EN-US">From:</span></b><span style="font-size: 10pt;" lang="EN-US"> Jonathan Charles [mailto:<a href="mailto:jonvoip@gmail.com" target="_blank">jonvoip@gmail.com</a>]
<br>
<b>Sent:</b> September-04-08 12:14 PM<br>
<b>To:</b> Rasim Duric<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Busy Triggers and Max Calls for CTI ports</span></p>
</div><div><div></div><div class="Wj3C7c">
<p> </p>
<div>
<p style="margin-bottom: 12pt;">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</p>
<div>
<p>On Thu, Sep 4, 2008 at 10:53 AM, Rasim Duric <<a href="mailto:rduric@uoguelph.ca" target="_blank">rduric@uoguelph.ca</a>> wrote:</p>
<div>
<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>
<p style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">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></p>
</div>
<p> </p>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>