Genesys Cloud - Main

 View Only

Discussion Thread View
Expand all | Collapse all

Parsing UUI data coming from Avaya to Genesys Cloud

  • 1.  Parsing UUI data coming from Avaya to Genesys Cloud

    NEW MEMBER
    Posted 27 days ago
    Edited by Khurshid Ali 27 days ago

    Hello Members,

    we are trying to get UUI data from Avaya system to Gensys cloud. Through SIP trunking between them. Calls are coming properly on a dummy number, we are getting the UUI header as well, but Genesys is not able to parse the UUI data.

    I am facing difficulty in parsing the initial characters. I believe, because of which Genesy is not able to parse the whole thing.

    Below is the call flow with other related data. 

    What shows under those attributes on Genesys:

    HEX received with stripping protocol Discriminator:(ONLY the green highlighted parts are UUI)
    C82E323036383938373836397c31323334357c597c313235307c544553547c323032342d31312d30375432323a31375a

    ASCII parsing on notepad++:
    È.2068987869|12345|Y|1250|TEST|2024-11-07T22:17Z (ONLY the green highlighted parts are UUI)

    On the .pcap for that call:

    Any help is greatly appreciated. 


    #ArchitectureandDesign
    #SIP/VoIP
    #Telephony

    ------------------------------
    Khurshid Ali
    Senior Service Engineer
    ------------------------------



  • 2.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    GENESYS
    Posted 27 days ago

    Hello Khurshid,

    Welcome to the Community! I believe you will need to raise a case with our Customer Care team to check what is happening to the UUI data in the Edge logs. Please let us know what you are able to find.



    ------------------------------
    Jason Kleitz
    Online Community Manager/Moderator
    ------------------------------



  • 3.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    NEW MEMBER
    Posted 26 days ago

    Thanks for your response Jason, I have raised a care ticket. 
    While chatting with one of the care team member, the suggested to substring the initial characters, I had already tested that but we need UUI userdata in the system variable Call.UUIData. So, substring couldn't help in retaining the Call.UUIData.

    Also, if we create another variable with right HEX encoded UUI data, is there a way that we can convert that to ASCII on the Participant attribute? or parse the data for further usage on the call flow?



    ------------------------------
    Khurshid Ali
    Senior Service Engineer
    ------------------------------



  • 4.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    Posted 25 days ago

    Hi!!

    AAre you able to change the encoding on the trunk side, to ASCII??

    If it doesn't work, you should use something into your flow, to convert from hex to ASCII, using a datatable conversion mapping, and make a loop to change the hole UUI



    ------------------------------
    David Fradejas Tomás
    Genesys Senior Consultant
    ------------------------------



  • 5.  RE: Parsing UUI data coming from Avaya to Genesys Cloud
    Best Answer

    Posted 25 days ago

    David,

    Avaya sending the UUI to the SIP Trunk in the HEX format (max 96 positions).

    But You get the "Call.UUIData" variable in ASCI format.

    Try to save "Call.UUIData" variable to the "Participant Data" and check it.

    Of course, You can try to change the "Trunk" definitions,  but from my experience, it changes nothing

    Admin->Telephony->Trunks->Trunk Name->Protocol->User to User Information (UUI)->Encoding Format

    If You have some additional questions, You can send them directly to me



    ------------------------------
    Best regards,

    Yvgeni Liberman
    ITNAV-Pro Ltd.
    ------------------------------



  • 6.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    Posted 25 days ago

    Yes, I know,

    That's why I said to Kurdish If it doesn't work,  should use something into your flow, to convert from hex to ASCII, using a datatable conversion mapping, and make a loop to change the hole UUI step by step making a loop, and after that, parse the information 



    ------------------------------
    David Fradejas Tomás
    Genesys Senior Consultant
    ------------------------------



  • 7.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    Top 25 Contributor
    Posted 24 days ago

    Change the encoding-format of the User-to-User from Hex to Ascii on the Trunk settings, and then check it again. Also make sure you select the correct User-to-User protocol discriminator.

    If I remember correctly, a few years ago we had similar issue, the data was hex and we have to receive it as Ascii on the trunk, then we get what we want on the Architect Call.UUIData. We had to add a discriminator of 00 at the start of the UUI



    ------------------------------
    Vineet Kakroo
    Senior Technical Consultant
    ------------------------------



  • 8.  RE: Parsing UUI data coming from Avaya to Genesys Cloud

    NEW MEMBER
    Posted 24 days ago

    Hi Yv,

    I did tested it, but it was still not parsing the data. IT was still throwing same HEX characters.



    ------------------------------
    Khurshid Ali
    Senior Service Engineer
    ------------------------------



  • 9.  RE: Parsing UUI data coming from Avaya to Genesys Cloud