Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ICM 6.0. Calls do not act after DtAborts=2

IPCC 6.0

Periodically calls on operators cease to act, restart ICM helps only.

After reception DtAborts=1, DtAborts=2 calls do not act.

It can be necessary to increase AgentReserveTimeout, by default costs 7? (up to what value?)

Or something another?

21:34:28 pg1A-pim1 Trace: TelephonyDriver::ProcessReservedTimeout: No call arrived to match PreCall message. netTargID=5024 Ext=5012 AgentID=34 RTRCallKey=148113.41449207 DtAborts=1

21:34:28 pg1A-pim1 Trace: CSTA PRIVATE GEODeviceTargetAbortIndMSG: TelephonyDriver::SendDeviceTargetAbortInd: SENT TO OPC

CRSCallID_Date = 148113 CRSCallID_ID =41449207

NetworkTargetID = 5024 PeripheralCallKey = -1

21:34:43 pg1A-pim1 Trace: TelephonyDriver::ProcessReservedTimeout: No call arrived to match PreCall message. netTargID=5024 Ext=5012 AgentID=34 RTRCallKey=148113.41449208 DtAborts=2

21:34:43 pg1A-pim1 Trace: CSTA PRIVATE GEODeviceTargetAbortIndMSG: TelephonyDriver::SendDeviceTargetAbortInd: SENT TO OPC

CRSCallID_Date = 148113 CRSCallID_ID =41449208

NetworkTargetID = 5024 PeripheralCallKey = -1

21:34:43 pg1A-pim1 Trace: AGENT 34 on Ext:5012 MISSED 2 consecutive routed calls. FORCING TO NOT READY STATE.

I shall be grateful for the answer.

1 REPLY
New Member

Re: ICM 6.0. Calls do not act after DtAborts=2

Whether there will be an answer?

140
Views
0
Helpful
1
Replies
CreatePlease login to create content