SharedUUI - UUI from application {0} [{1}] in invalid format for Call ID {2}
Event level
Warning event. No alarm is generated
Trigger component
Media Server SessionManager process
Problem description
{0} - The EPM name for the application.
{1} - The Shared UUI string that was set by the application.
{2} - The Call ID.
The AAI or UUI data set by an application has invalid format. When this error occurs, no AAI/UUI data can be sent in the SIP message. But functions such as a transfer can still be performed.
Proposed Solutions
When an application is configured with an Operation Mode set to Shared UUI, the data format of the UUI/AAI should be set to <ID1>,<Data1>;<ID2>,<Data2>. If the data is improperly formatted, the SessionManager cannot encode the data. The data cannot be sent in the SIP message.
Procedure
If the SessionManager should not be operating in the Shared UUI mode, do the following:
From the EPM, go to Applications.
Click the name of the application.
Click Advanced Parameters.
Verify that the Operation Mode field is set to Service Provider.
If the Operation Mode field is set to Service Provider, contact Avaya Technical Support.
If the SessionManager should be operating in the Shared UUI mode, do the following:
Verify that the data of the UUI/AAI set by the application has the format of <ID1>,<Data1>,<ID2>,<Data2>.
Review the trace messages in the SessionManager log files for additional information. If tracing for SessionManager was not enabled, reproduce the problem with SessionManager tracing set to Finest.
