Cisco Cisco Unified Contact Center Enterprise 9.0(2) Technical References

84 

 Post-Routing 

 

separated by spaces. Every 

#

 and 

*

 count as one digit each. The digit collection 

timeout must be between one (1) and 31, inclusively. 

The following example indicates that four digits are to be collected with a digit 
collection timeout of ten seconds: 

COLLECT 4 TIMEOUT 10 

The next example indicates that the digits 3, 2, 1 should precede the route 
selection: 

DIAL 321 

With proper configuration using translation routes, the 

DIAL

 syntax can allow 

you to provide the caller’s ANI (or any set of digits) to the Avaya and 
subsequently have it displayed on an agent’s console. 

The Trunk Access Code Peripheral Variable has the syntax: 

TAC 

TRUNK_ACCESS_CODE 

TAC

 is a keyword delimiter and must be specified as shown (case is not 

important). The 

TRUNK_ACCESS_CODE

 

field should specify a valid Trunk 

Access Code extension for the Peripheral. The TAC can also be  
pre-pended in the Label. All fields must be space separated. 

The following example indicates a Trunk Access Code of 111 for the route 
selection: 

TAC 111  

This is a null-terminated ASCII character string. The UUI data is stored in 
Peripheral Variable 5 for both the Route Request and Route Select messages 
only if the protocol format of the UUI data is C_UU_IA5. Therefore, unless 
modified, all UUI data received for a call will be included when sent to the calls’ 
destination. UUI data is limited to 40 bytes. 

Avaya PIM was designed to support the User-to-User information (UUI) up to 
32 bytes inline with the older switch version supportability, which was 32 bytes.  

Avaya CVLAN Server Release 8, and link version 4 and beyond, ASAI now 
supports UUI up to 96 bytes.  

With this enhancement Avaya PIM supports 40 bytes for the UUI field, but the 
CTIOS Agent Desktop takes a maximum of only 39 characters of a 40 character 
string for call variables.