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
------------------------------

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.

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
------------------------------

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?

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.

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
------------------------------

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

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?

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.

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
------------------------------

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

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

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?

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.

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
------------------------------

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

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

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?

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.

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
------------------------------

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

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

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?

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.

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
------------------------------

Hi Yv,

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

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

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

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?

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.

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
------------------------------

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

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?

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.

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
------------------------------

Hi David,

Thanks, the later part worked with using data table and converting it into ASCII manually. I was wondering, if Avaya could send us just the User Data instead of initial characters. 

BTW, is it not that trunk side settings ONLY applies to outbound calls and not to inbound. 

Inbound call should be automatically be parsed by Genesys using system variable Call.UUIData

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

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?

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.

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
------------------------------

Hi David,

Thanks, the later part worked with using data table and converting it into ASCII manually. I was wondering, if Avaya could send us just the User Data instead of initial characters. 

BTW, is it not that trunk side settings ONLY applies to outbound calls and not to inbound. 

Inbound call should be automatically be parsed by Genesys using system variable Call.UUIData

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

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?

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.

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
------------------------------

Khurshid,

I also have the SIP Trunk from AVAYA SBC to the "cloud"

Avaya has a limitation of 96 characters in the UUI.

Please see the UUI definition that I made (it's working fine)

It is "more than simple" :)

Hi David,

Thanks, the later part worked with using data table and converting it into ASCII manually. I was wondering, if Avaya could send us just the User Data instead of initial characters. 

BTW, is it not that trunk side settings ONLY applies to outbound calls and not to inbound. 

Inbound call should be automatically be parsed by Genesys using system variable Call.UUIData

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

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?

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.

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
------------------------------

Hi Yvgeni,
If you change the Encoding Format from Hex to Ascii, what does it do the UUI data in Architect once it is received from Avaya.

We also used to get a 00 delimited UUI data from Avaya and the Encoding Format we have setup is still Ascii.

Khurshid,

I also have the SIP Trunk from AVAYA SBC to the "cloud"

Avaya has a limitation of 96 characters in the UUI.

Please see the UUI definition that I made (it's working fine)

It is "more than simple" :)

Hi David,

Thanks, the later part worked with using data table and converting it into ASCII manually. I was wondering, if Avaya could send us just the User Data instead of initial characters. 

BTW, is it not that trunk side settings ONLY applies to outbound calls and not to inbound. 

Inbound call should be automatically be parsed by Genesys using system variable Call.UUIData

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

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?

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.

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
------------------------------