Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » JTAPI » Tlink Down - When Call Redirected / Forwarded   XML
 
Author Message
Navid-



Joined: 09/09/2020 09:02:01
Messages: 2
Offline

A very peculiar issue is being observed, one that can not be replicated at will.

AES and JTAPI Details
AES: 8.1.3.0.0.25-0
JTAPI: ecsjtapia_8.1

AES was recently patched for a similar issue (Link Down) when invalid number dialed. (Attached screenshot)
Patch: AES_19767_813


Set-Up

  • 1.Agents login in via out CTI application.
    2.An Agent (A1) Places a call from hardphone (or softphone) to another agent's (A2) station.
    3.Agent A2 does not answer the call.
    4.After about 4 -5 rings the coverage path comes into play where the call is forwarded to a Voice Mail Hung- Group (7100 in this case).



  • Issue
    On the back end (JTAPI) AES Link drops between the CTI and AES.
    I have tried to replicate this by following the steps above but no luck in any of my attempts.


    [size=9]
    Error Snippet
    [size=9]2020-11-18 14:02:20,637 [DistributeCSTAEvent] INFO TSEventHandler - Handling CSTA_HELD for TSProvider[#1]@388cb8aa
    2020-11-18 14:02:20,638 [DistributeCSTAEvent] ERROR TSEventHandler - Event Distributor Exception - shutting down provider TSProvider[#1]@388cb8aa
    2020-11-18 14:02:20,638 [DistributeCSTAEvent] ERROR TSEventHandler -
    java.lang.NullPointerException
    at com.avaya.jtapi.tsapi.impl.core.TSEventHandler.doConnEvents(TSEventHandler.java:1034)
    at com.avaya.jtapi.tsapi.impl.core.TSEventHandler.cstaUnsolicited(TSEventHandler.java:302)
    at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventDistributor.handleEvent(TsapiEventDistributor.java:113)
    at com.avaya.jtapi.tsapi.tsapiInterface.TsapiEventQueue.run(TsapiEventQueue.java:104)
    2020-11-18 14:02:20,644 [GetEventThread] INFO TsapiSession - Received monitorCrossRefID 45 for TSProvider[#1]@388cb8aa
    2020-11-18 14:02:20,644 [DistributeCSTAEvent] INFO TSProviderImpl - TSProvider.shutdown - attempting shutdown
    2020-11-18 14:02:20,644 [GetEventThread] DEBUG TsapiSession - CSTATransferredEvent ::=
    2020-11-18 14:02:20,644 [DistributeCSTAEvent] INFO TSProviderImpl - TSProvider.shutdown - Starting

    [/size]



    Logs
    Attached logs JTAPI logs for 4 such calls.


    Please do let me know if any additional details are required.

    Thanks,


    [/size]
     Filename linkDown.zip [Disk] Download
     Description No description given
     Filesize 361 Kbytes
     Downloaded:  409 time(s)

    [Thumb - aesVersion.jpg]
     Filename aesVersion.jpg [Disk] Download
     Description No description given
     Filesize 185 Kbytes
     Downloaded:  556 time(s)

    MartinFlynn



    Joined: 30/11/2009 05:00:18
    Messages: 1783
    Online

    Your traces show the CSTAHeldEvent events the JTAPI client received from AE Services. For the cases where an exception is thrown, these events are malformed. For example the event at 2020-11-18 14:02:20,636 in jtapi-18Nov-call_ID-13060.txt:

    CSTAHeldEvent ::=
    {
    monitorCrossRefID 45
    heldConnection
    {
    callID 13060
    deviceID <null>
    devIDType 0 < STATIC_ID >
    }
    holdingDevice
    {
    deviceID <null>
    deviceIDType 30 < EXPLICIT_PUBLIC_UNKNOWN >
    deviceIDStatus 1 < ID_NOT_KNOWN >
    }
    localConnectionInfo 3 < CS_CONNECT >
    cause -1 < EC_NONE >
    }

    Note that the Held DeviceID and Holding DeviceID are both null. Also, there should be a TsapiPrivate data section at the event of the event. There is an example of a good event earlier in the same log file.

    Obviously, the JTAPI client expects this data to exist and is behaving badly when it does not. You will need to find out why this data is not being filled in. Most likely, AE Services is not receiving it from Communication Manager but it is also possible that AE Service is leaving out data for some reason.

    If this problem is occurring in a production environment, your customer should open a ticket with Avaya Services or their business partner for help. If this is occurring in your lab, then you can open a Devconnect Technical Support Ticket and one of my colleagues will try to help you investigate.

    Martin
    UmeshC



    Joined: 18/04/2011 23:19:21
    Messages: 68
    Offline

    Hi Navid,

    Did you find cause for this shutdown? We are facing same issue when we dial wrong number, we receive providerShutDown event?

    Thanks & Regards,
    Umesh
    [Email]
    Navid-



    Joined: 09/09/2020 09:02:01
    Messages: 2
    Offline

    Umesh-

    Our issue was resolved by applying a Hot Fix (AES_19767_813) on the AES 8.1.3.


    The Hot Fix can only be acquired from Avaya for AES 8.1.2 or higher


    https://downloads.avaya.com/css/P8/documents/101058326

    Known issues and workarounds in Application Enablement Services 8.1.x.x
    [i]
    ----AES-19767 ---"The JTAPI SDK crashed due to the CSTA_CONNECTION_CLEARED event after an invalid number was called."
    JTAPI crash with nullpointer exception."
    JTAPI crash due to ConnectionCleared event."


    Hope this helps
    UmeshC



    Joined: 18/04/2011 23:19:21
    Messages: 68
    Offline

    Thanks Navid for quick reply.
    Let me check with Avaya Vendor.

    Regards,
    Umesh
    [Email]
     
     
    Go to: