Enhanced information forwarding has been tested with several major carriers.
To find out if the capabilities work with your carrier, check with your account team for the latest information. If testing is not done to verify operation over the public networks involved with the preferred specific configuration, use private trunking between the nodes until successful testing is completed.
Any communication server that acts as tandem node must have priorities assigned to the Shared UUI features for non-QSIG trunk groups.
Even if this communication server does not create anything, the priorities must be set correctly to pass the information along.
The Send codeset 6/7 LAI trunk group field operates independently of the UUI IE Treatment trunk group field.
However, if you turn both the options on, you will send the same information twice and possibly exceed the maximum ISDN message size. The communication server provides a warning message when both options are administered. There are two ways to correct when the user data exceeds the maximum message size, either:
Leave the VDN Name and Other LAI Information fields blank on the Shared UUI Feature Priorities screen or
Disable the Send codeset 6/7 LAI field.
For non-QSIG or QSIG trunk groups to the communication server that require information forwarding, the UUI IE Treatment must be shared and the Send Codeset 6/7 LAI IE must be n.
Information transported using the Shared UUI does not work with non-Avaya switches unless the information adheres to the proprietary encoding.
