Cisco TSP error - Caught ArrayException! Error ID = 7, Index = 1000
Our TAPI application monitors a set of Call Manager RoutePoints. At high call volumees (50-100 calls/min), over a period of time, the RoutePoint gives a fast-busy tone and all the new and old calls are dropped. There are no TAPI events on the RoutePoint after this. The TSP shows the following error when this happens:
14:33:18.122 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall() *ERROR* Caught ArrayException! Error ID = 7, Index = 1000, Description: access out of bounds
09/08/2003 14:33:18.122 CiscoTSP001.tsp| CSelsiusTSPLine::NewCallEvent() line Id=0x000009FE *ERROR* Unable to allocate call. Closing line.
This seems like a bug in the TSP? Is this a known error? Are there any fixes to it?
This has happened over an over in our testbeds.
We are using CCM 3.3 on a 1125 MHZ, 528 MB RAM machine. The TSP machine is 1 GHZ dual CPU with 1 GB Ram. All the tests are ran under lab environment with less than 10 phones connected.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...