CTI warning: The request failed because the timeout limit was exceeded.

Question

hi,
For a perticular IP Phone extension when agent is going to login using CTI agent toolkit then CTI generatin this msg "CTI warning: The request failed because the timeout limit was exceeded". but the other ph is working fine. I have deleted this phone and add againg. And the ph re-associate with PG and JTapi user. but still have the prob. For more plz see the find attached.

Answer 1

Your first troubleshooting step here should be to check what JTAPI Gateway thinks is the state of that extension, you can easily check that through procmon. Here's an example from my lab.
C:\Documents and Settings\Administrator>procmon ipcc pg1a jgw1
>>>>jdi 2000
>>>>
Addr: 2000      ActiveLines: 0          RegistrationState: IN_SERVICE
        m_CurrentInvokeID = 0
        m_elapsedTPServicesRequestSeconds = 0
        queuedDTMFDigits = null
        sendingDTMFInProgress: N
        sendQueuedMsgAddCallObserverResponse: Y
        monitoredVirtualDialerPort: N
        virtualDialerPort: N
        loggedInAgent: N
        DeviceStatus : UnmonitoredDevice
        addressDeviceType : GWMSG.DEVICE_TYPE_DEVICE
        observeredTypeString : logged Out Agent Device
        isAddressRestricted: N
        addressDeviceProtocol : PROTOCOL_SCCP
        silentMonitorStatus : 0
        silentMonitoredCallID : -1
        TerminalName : SEP001BD52C547F
The RegistrationState should be IN_SERVICE for a phone that is registered with CUCM. If you can see that the phone is registered with CUCM in it's adminsitration pages, made sure that it's in the list of associated devices, made sure you're running the correct version of the jtapi plugin and still see it as OUT_OF_SERVICE, you're probably looking at a CTI Manager defect. CSCti07947 and CSCti11651 spring to mind but there are probably a couple more.
Most of these defects should be fixed in releases like CUCM 7.1(5), 8.0(x) and up. If the issue persists, you're probably best off opening a TAC Service Request to identify the exact cause. The PG (JTAPI Gateway) only shows you what it gets from CTI Manager, so as you can see from my above observations, you'd want to focus your troubleshooting on the CUCM end.