Hi ,

We are having a issue with UUI , in CM we had set the UUI length as 128 and in experience portal also set as 128. Now the issue is


1) when the UUI length is greater than 99 and less than 126 bytes, there is no error in Session manager and there is no UUI message in Jtapi (returning null in Jtapi AES trace log)

2) when the UUI length is greater than 126 and less than 128 , we are getting error in session manager , saying UUI length is invalid.

3) When the UUI length is less than 99, there is no error in session manager and we are getting the UUI in the Jtapi.


CM Version : 5.0
Experience Portal Version : 7.0.1
AES version & Jtapi : 6.3


Why this behavior happens ? where can be the problem ? Session manager,AES or CM ? the OD application is not able to utilize whole 128 bytes of UUI allocated.

how we can identify where is the problem ?


thanks
bala.

Is this SIP based or H323? Are you configured for Shared mode or Service Provider mode at the trunk level? Shared mode will convert the incoming to hex as well as pack protocol discriminators and formatting into the UUI. Service Provider will not perform the conversion.

Do you have a log of the raw UUI when it comes in?

At trunk level , it is Shared mode. At Experience portal too it is shared mode. We are using SIP based. Which log info do are you looking for

OD IVR application trace log ? Session Manager log ? CM log ? Raw UUI in hex format or String format ? We are sending the UUI in hex format.


This is OD trace log ,

<transfer name="ErrorTransfer" dest="tel:<vdn>" type="blind" connecttimeout="0s" maxtime="0s" aai="PD,00;C8,3230303436243224242424242424242424242424242424242424242424242424242424242424242424242424242424242424244e242424242424242424244e242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424242424">
8:<prompt bargein="true" bargeintype="speech" timeout="8000ms">
9:Please Hold..
10:</prompt>

Thanks
bala.

For issue 2) you have to take into account that it embeds the protocol discriminator and formatting PD:00;C8, so it makes sense that anything above 126 will generate an error as that adds up to 129 and above.

For issue 1) I believe EP is trying to embed the UCID into the UUI data. If you look at the help for Max UUI Length on EP, it mentions that it tries to add UCID and if too large, it will leave the UUI blank if it can't determine what to leave out. This appears to be happening when you are in that range slightly below 128. I would bring this issue to EP support to have them verify for sure if that is what is going on in this size range. They will be able to tell you which of their logs will give details on the problem as this is more a platform issue than an OD issue.

Maximum UUI
Length
The maximum length of the UUI data that can be passed in the SIP
header. If this length is exceeded and Voice Portal generated a UCID
for the call, the UCID is removed from the UUI data. If the result still
exceeds this value, or if the UCID was passed to Voice Portal by the
application, Voice Portal does not send any UUI data. Instead, it
leaves the entire field blank because it has no way to determine what
can be left out.

so when the UUI Max length is 128 bytes,

how is allocated to the application , if PD:00;C8, takes some bytes and i assume if UCID is trying to append from experience portal , how much will be the application can utilize.

UCID length is 20 , where there is FA identifier for UCID and 128-20 .. 108 ..for these identifiers i dont know exactly how much it will take.

In our experience portal , the UCID is not generated .The UCID is generated at CM. how to make sure that UCID is not appended in UUI.

1) How much length of UUI will be available for application to send data , if the max is 128 ?
2) UCID will be appended in UUI by always , when we do a transfer from Exp portal to CM ?
3) what other data in UUI will be appended (including identifiers) ?





thanks
bala.

You will have to ask EP support about that. It's all taking place on the platform.

can you please direct me to right forum ?

They don't have an active forum. You are better off calling into Avaya customer support.

Avaya support is already looking in this issue. it seems i found the issue what is happening ..

This is the UUI coming from one IVR to another application .

PD,00;C8,20046$2$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$N$$$$$$$$$$N$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$;FA,000134265592DBB1

The total length of this UUI is 128. The Experience portal is appending ;FA,000134265592DBB1 (UCID) at the end of UUI, irrespective of yes or no Transport UCID in Shared Mode.

apart from these i have these PD,00;C8, ..so all i do have is length of 99 for the application.

How to disable appending UCID in UUI ?

Thanks
bala.

You will have to ask EP support how to disable appending the UCID. You can try service provider mode. I don't think it will append it in that mode, but ask them first as it might be an easy resolution before trying another mode.