This document was generated from CDN thread
Created by: Abdul Rasheed on 27-01-2011 04:45:16 AM
Hi,
Our application server is monitoring 70 Cisco IP phone extensions of a call centre. TSP version is 6.1 and CUCM version is 6.1 . it was noticed that , after running the application for 3 days continously , and monitoring all these 70 extensions,the monitor will not be responding and application will be in a freeze condition. Please find the errors in the logs for TSP collected from the application server.
01/20/2011 23:57:56.578 CiscoTSP001.tsp| CQBEHelperBase:
roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>
01/20/2011 23:57:56.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/20/2011 23:59:00.593 CiscoTSP001.tsp| CQBEHelperBase:roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>
01/20/2011 23:59:00.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:00:08.593 CiscoTSP001.tsp| CQBEHelperBase:roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>
01/21/2011 00:00:08.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:01:02.593 CiscoTSP001.tsp| CQBEHelperBase:roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>
01/21/2011 00:01:02.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:01:46.546 CiscoTSP001.tsp| CSelsiusTSPLink::Connect() *ERROR* Failed to connect to CTI Manager: error=10061|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall() *ERROR* Caught ArrayException! Error ID = 7, Index = 1000, Description: access out of bounds|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::NewCallEvent() line Id=0x00000368 *ERROR* Unable to allocate call. Closing line.|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::CallStateEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::CallPartyInfoChangedEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.187 CiscoTSP001.tsp| CSelsiusTSPLine::CallStateEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall() *ERROR* Caught ArrayException! Error ID = 7, Index = 1000, Description: access out of bounds|<LVL::Error><MASK::0001>
01/21/2011 07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPLine::NewCallEvent() line Id=0x00000374 *ERROR* Unable to allocate call. Closing line.|<LVL::Error><MASK::0001>
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jehad Kalboneh on 29-01-2011 08:25:50 AM
did you use dialer.exe to check if the dialer get the line correctly or not,
you can also use Tapi-Brower to simulate the Tapi Api
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 30-01-2011 04:16:52 AM
Hi Jehad,
When this issue is coming up, the dialer application also will not initiate. i didnt try the TAPI Browser, from where i can download this application? i doubt the issue is due to some user privilages. Have you ever faced such an issue with TAPI?
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 12-02-2011 12:21:10 AM
Dear All,
I noticed that the error is coming up on the 1000th call on a line. On recieving the 1000th call , the Array out of bound exception will be triggered and line get closed by itself with the following errors in the TSP traces.
01/21/2011
07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall()
*ERROR*
Caught
ArrayException! Error ID = 7, Index = 1000, Description: access out
of
bounds|<LVL::Error><MASK::0001>
Our application is only monitoring the extensions and
collecting the call information. I am wondering if this is a known TSP
bug? Our TSP version is 6.1(2.4) and CUCM version is also
6.1 . I request some body to kindly assist us in sorting out the
issue. Its affecting some of our important deployments now.
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jun Xue on 15-02-2011 02:05:16 AM
What is your application? Does your application always send LineDeAllocateCall when call goes IDLE? Besides, how many TAPI applications running on the server? or how many of your application threads running on your server?
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 15-02-2011 08:27:05 AM
Dear Jun,
We were not calling lineDeallocateCall from our application before. But today we tried calling this , but still the same error is coming after 1000th Call.
Thanks and Regards
Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 15-02-2011 08:33:49 AM
Hi ,
we have 2 applications running parallel. One application running from PC1 will do make call between two extensions 1040 and 1045 . The other application runnning in PC2 is monitoring the extensions 1040 and 1045. Today we tried linedeallocate call in application running in PC2 but the error was repeating again . Should we do that in application running in PC1 also?
Thanks and Regards
Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jun Xue on 15-02-2011 01:46:40 PM
How TAPI layer works is... if you multiple TAPI application registers with TAPI and monitoring the line/call, all applications need to send LineDeAllocateCall to TAPI, so that TAPI decrease its reference counter and finally send LineCloseCall to CiscoTSP. Please check whether there are multiple TAPI application register with TAPI on your TAPI client server, and you should do this on all server. Otherwise, in your case, PC1 will definitely hit the problem.
Created by: Abdul Rasheed on 27-01-2011 04:45:16 AM
Hi,
Our application server is monitoring 70 Cisco IP phone extensions of a call centre. TSP version is 6.1 and CUCM version is 6.1 . it was noticed that , after running the application for 3 days continously , and monitoring all these 70 extensions,the monitor will not be responding and application will be in a freeze condition. Please find the errors in the logs for TSP collected from the application server.
01/20/2011 23:57:56.578 CiscoTSP001.tsp| CQBEHelperBase:
roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>01/20/2011 23:57:56.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/20/2011 23:59:00.593 CiscoTSP001.tsp| CQBEHelperBase:
roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>01/20/2011 23:59:00.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:00:08.593 CiscoTSP001.tsp| CQBEHelperBase:
roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>01/21/2011 00:00:08.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:01:02.593 CiscoTSP001.tsp| CQBEHelperBase:
roviderOpen() *ERROR* TSP Timed out waiting for synchronous message. Check the Provider Open Completed Timeout and the Synchronous Message Timeout in TSP configuration.|<LVL::Error><MASK::0001>01/21/2011 00:01:02.593 CiscoTSP001.tsp| CSelsiusTSPLink::getMessage() *ERROR* Receive() failed with error 10038.|<LVL::Error><MASK::0001>
01/21/2011 00:01:46.546 CiscoTSP001.tsp| CSelsiusTSPLink::Connect() *ERROR* Failed to connect to CTI Manager: error=10061|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall() *ERROR* Caught ArrayException! Error ID = 7, Index = 1000, Description: access out of bounds|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::NewCallEvent() line Id=0x00000368 *ERROR* Unable to allocate call. Closing line.|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::CallStateEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.171 CiscoTSP001.tsp| CSelsiusTSPLine::CallPartyInfoChangedEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 05:18:09.187 CiscoTSP001.tsp| CSelsiusTSPLine::CallStateEvent() LineId:[0x00000368] *ERROR* Did not find call id 0x02882BB2|<LVL::Error><MASK::0001>
01/21/2011 07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall() *ERROR* Caught ArrayException! Error ID = 7, Index = 1000, Description: access out of bounds|<LVL::Error><MASK::0001>
01/21/2011 07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPLine::NewCallEvent() line Id=0x00000374 *ERROR* Unable to allocate call. Closing line.|<LVL::Error><MASK::0001>
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jehad Kalboneh on 29-01-2011 08:25:50 AM
did you use dialer.exe to check if the dialer get the line correctly or not,
you can also use Tapi-Brower to simulate the Tapi Api
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 30-01-2011 04:16:52 AM
Hi Jehad,
When this issue is coming up, the dialer application also will not initiate. i didnt try the TAPI Browser, from where i can download this application? i doubt the issue is due to some user privilages. Have you ever faced such an issue with TAPI?
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 12-02-2011 12:21:10 AM
Dear All,
I noticed that the error is coming up on the 1000th call on a line. On recieving the 1000th call , the Array out of bound exception will be triggered and line get closed by itself with the following errors in the TSP traces.
01/21/2011
07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall()
*ERROR*
Caught
ArrayException! Error ID = 7, Index = 1000, Description: access out
of
bounds|<LVL::Error><MASK::0001>
Our application is only monitoring the extensions and
collecting the call information. I am wondering if this is a known TSP
bug? Our TSP version is 6.1(2.4) and CUCM version is also
6.1 . I request some body to kindly assist us in sorting out the
issue. Its affecting some of our important deployments now.
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jun Xue on 15-02-2011 02:05:16 AM
What is your application? Does your application always send LineDeAllocateCall when call goes IDLE? Besides, how many TAPI applications running on the server? or how many of your application threads running on your server?
Dear All,
I noticed that the error is coming up on the 1000th call on a line. On recieving the 1000th call , the Array out of bound exception will be triggered and line get closed by itself with the following errors in the TSP traces.
01/21/2011
07:07:14.343 CiscoTSP001.tsp| CSelsiusTSPCallList::GetNewCall()
*ERROR*
Caught
ArrayException! Error ID = 7, Index = 1000, Description: access out
of
bounds|<LVL::Error><MASK::0001>
Our application is only monitoring the extensions and
collecting the call information. I am wondering if this is a known TSP
bug? Our TSP version is 6.1(2.4) and CUCM version is also
6.1 . I request some body to kindly assist us in sorting out the
issue. Its affecting some of our important deployments now.
Thanks and Regards
Abdul Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 15-02-2011 08:27:05 AM
Dear Jun,
We were not calling lineDeallocateCall from our application before. But today we tried calling this , but still the same error is coming after 1000th Call.
Thanks and Regards
Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Abdul Rasheed on 15-02-2011 08:33:49 AM
Hi ,
we have 2 applications running parallel. One application running from PC1 will do make call between two extensions 1040 and 1045 . The other application runnning in PC2 is monitoring the extensions 1040 and 1045. Today we tried linedeallocate call in application running in PC2 but the error was repeating again . Should we do that in application running in PC1 also?
Thanks and Regards
Rasheed
Subject: RE: TSP Error after running application for 3 days continously
Replied by: Jun Xue on 15-02-2011 01:46:40 PM
How TAPI layer works is... if you multiple TAPI application registers with TAPI and monitoring the line/call, all applications need to send LineDeAllocateCall to TAPI, so that TAPI decrease its reference counter and finally send LineCloseCall to CiscoTSP. Please check whether there are multiple TAPI application register with TAPI on your TAPI client server, and you should do this on all server. Otherwise, in your case, PC1 will definitely hit the problem.