CM:UUI data not getting translated from Hex to IA5 correctly.

Doc ID		SOLN292574
Version:		4.0
Status:		Published
Published date:		14 Jun 2019
Created Date:		08 Jul 2016

Author:

Samuel Jones

Details

CM 6.3.0.124.0-22899

Problem Clarification

UUI data received in the SIP INVITE is passed directly to the ASAI notify in HEX format and is passed directly to the ASAI message without modification. The result is that the far end application UUI data contains invalid characters.

Cause

This is because the incoming INVITE contains characters that are not valid for the IA5 protocol.

Solution

Set the CM trunk group form to "shared" in the field "UUI IE Treatment:"

Additional Relevant Phrases

CM:UUI data not getting translated from Hex to IA5 correctly. Unwanted UUI data coming from PSTN ISDN cannot be completely removed from CM

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy