<div>yes I do have HA, that seems to be the root of what I am experiencing. I adjusted the group from 20 ports to 10 and sure enough it created twice as many ports. No big deal really just would have been nice to have read about it within the Cisco docs you know. When you have someone like myself trying to implement something and all they can do is go on the documentation provided you would hope it would be detailed and explain things. Here I was trying to follow documentation and work through things and this happens, so I stop because the result was not what you would expect you know? God knows how much time I wasted trying to determine why this was happening since the documentation did not explain it.
</div>
<div> </div>
<div>What can you do though? Just the way it is I guess.</div>
<div> </div>
<div><br> </div>
<div><span class="gmail_quote">On 10/19/06, <b class="gmail_sendername">Carter, Bill</b> <<a href="mailto:bcarter@sentinel.com">bcarter@sentinel.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div dir="ltr" align="left"><span><font face="Tahoma" color="#0000ff" size="2">Do you have High Availability?</font></span></div><br>
<div lang="en-us" dir="ltr" align="left">
<hr>
<font face="Tahoma" size="2"><span class="q"><b>From:</b> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:
<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Tech Guy<br></span><b>Sent:</b> Wednesday, October 18, 2006 11:23 AM
<br><b>To:</b> <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] JTAPI Call Control Group Configuration - IPCCExpress
<br></font><br> </div><span class="q">
<div></div>
<div>Well I got another one for you all. So I created my JTAPI call control group. For number of CTI ports I used "20", starting directory number "2600" and the device name prefix "CTIP".
</div>
<div> </div>
<div>It created the group and then displayed the list of CTI ports created. The question is why did it create 40 ports when I told it 20?</div>
<div> </div>
<div>My list of CTI Ports displayed are as follows:</div>
<div> </div>
<div>CTIP_2600,CTIP_2601,CTIP_2602,CTIP_2603,CTIP_2604,<br>CTIP_2605,CTIP_2606,CTIP_2607,CTIP_2608,CTIP_2609,<br>CTIP_2610,CTIP_2611,CTIP_2612,CTIP_2613,CTIP_2614,<br>CTIP_2615,CTIP_2616,CTIP_2617,CTIP_2618,CTIP_2619,<br>
CTIP_2620,CTIP_2621,CTIP_2622,CTIP_2623,CTIP_2624,<br>CTIP_2625,CTIP_2626,CTIP_2627,CTIP_2628,CTIP_2629,<br>CTIP_2630,CTIP_2631,CTIP_2632,CTIP_2633,CTIP_2634,<br>CTIP_2635,CTIP_2636,CTIP_2637,CTIP_2638,CTIP_2639,</div>
<div> </div>
<div> </div>
<div>I just don't get it? Am I just not understanding something or did it simply not work correctly?</div>
<div> </div>
<div>I must admit I also thought this was creating route points in callmanager, I guess I just thought "cti route ports and cti route points" were the same for some reason.</div>
<div> </div>
<div>Guess I am still not sure how Callmanager knows to send an extension IPCC but I am sure I will come to that soon enough.</div>
<div> </div>
<div>Any thoughts on why 40 ports got created despite the number of CTI ports being set to 20?</div>
<div> </div>
<div>Thanks!</div>
<div> </div>
<div> </div>
<div><br><br><br> </div></span>
<div><span class="q"><span class="gmail_quote">On 10/18/06, <b class="gmail_sendername">Ryan Ratliff</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com
</a>> wrote:</span> </span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><span class="q">Correct. The CTI ports are used by IPCC to terminate media for<br>playing prompts to callers, etc.
<br><br>-Ryan<br><br></span><span class="q">On Oct 17, 2006, at 5:47 PM, Tech Guy wrote:<br><br>The directory numbers used for the CTI Ports within the JTAPI call<br>control group are different and seperate from those of your agents
<br>right?<br><br>These numbers will only be used by CallManager and IPCC for <br>communication, no one would actually call these extensions or<br>anything right?<br><br>For example, I have 20 agents (IT stafff/helpdesk) each of them will
<br>have an extension setup seperate from their personal DID they already <br>have. This will be the extension utilized for the IPCC side of things.<br><br>Ideally I will be setting up a primary ext. that will be the helpdesk
<br>number. People will call it and it will prompt them to enter in say <br>1 for this, and 2 that. I will assign agents to resource groups and<br>skills, the groups and skills will be in a service queue right. And<br>
then the queue will basically be what the "press 1 or 2" thing will <br>send them to. This is very high level I know, but in essence that is<br>the idea right?<br><br>So, the CTI ports directory numbers are totally seperate from the
<br>agents numbers and the helpdesk number correct?<br>_______________________________________________ <br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net" target="_blank">
cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip </a>
<br></span></blockquote></div><br><pre>This email may contain proprietary and confidential information for the sole use of the intended recipient.
Any review, retransmission, dissemination, or other use of this information by persons or entities other than
the intended recipient is prohibited. If you are not the intended recipient, please contact the sender and
delete all copies. To the extent that opinions are expressed in this message, they are not necessarily the
opinions of Sentinel Technologies or any of its affiliates, employees, directors, officers or shareholders.
</pre></div></blockquote></div><br>