PureEngage On-Premises

 View Only

Sign Up

TServer is not sending the correct agent status during stuck calls check

  • 1.  TServer is not sending the correct agent status during stuck calls check

    Posted 02-06-2017 21:23
    Hi,
      During the stuck calls check the TServer is not sending the correct agent status. Please refer the log below. It is attaching the reason code as well. We are using cisco call manager switch.

    02:56:41.533 Int 04543 Interaction message "EventAddressInfo" received from 65205 ("cisco_tserver")
    2017-02-06 02:56:41> Server: Switch 'Cisco_CUCM'->'EventAddressInfo'
        TimeStamp    '2017-02-06 02:56:41'
        ReferenceID    24670
        ThisDN '6106777'
        Info Type 'AddressInfoDNStatus'
        Agent LoginID '5203'
        Reasons
            'AgentStatCode'    'BREAK'
            'Reason Code'    'BREAK'
        Extensions
            'AgentStatus'    2
            'AgentStatusTimestamp'    1486361881
            'AgentStatusReliability'    0
            'AgentLoginTimestamp'    1486352064
            'AgentLoginReliability'    0
            'AgentSessionID'    '427BNHCRH501T2FJ04UE2RBLTK005620'
            'dnd'    0
            'conn-1'    '041a0298835f341d'
            'call-uuid-1'    '427BNHCRH501T2FJ04UE2RBLTK0056O7'
            'ct-1'    2
            'ps-1'    12
            'party-uuid-1'    '427BNHCRH501T2FJ04UE2RBLTK0056O9'
            'status'    1
    2017-02-06 02:56:41> Action: Extension '6106777@Cisco_CUCM'(CallInbound):
        [2017-02-05 01:18:14] [2017-02-05 01:18:15] Monitored
        [2017-02-05 22:34:24] [2017-02-05 22:34:24] LoggedIn
        [2017-02-06 01:18:01] [2017-02-06 01:18:01] WaitForNextCall
        [2017-02-06 02:40:29] [2017-02-06 02:40:30] OffHook
        [2017-02-06 02:40:29] [2017-02-06 02:40:30] CallInbound (ConnID 295551579608527901)