We just turned up our first post-pilot call center last week on IPCC Express and when the admin changed them over to a live route point all they got was a busy signal. I went back through and somehow she managed to set the CTI Ports on the call control group to the same number as one of the JTAPI triggers - different partitions but same actual number.. Soon as we moved them over to their own numbers it started working. Not sure if that is your problem but might be worth looking at real quick - maybe your fifth port has the same number as something else?
<br><br><div><span class="gmail_quote">On 7/19/06, <b class="gmail_sendername">Jonathan Charles</b> <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
New install, CCM4.1(3)sr3b, IPCC 3.5(3)sr3...<br><br>CTI RP has maximum calls 5000 and the script application has 100<br>calls, yet after four calls in queue, the fifth call to the RP gets a<br>busy signal.<br><br>What am I missing?
<br><br><br><br><br>Jonathan<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">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br><br clear="all"><br>-- <br>Ed Leatherman<br>IP Telephony Coordinator<br>West Virginia University<br>Telecommunications and Network Operations