Avaya Logo

Previous Topic

Next Topic

Book Contents

Book Index

Using the default.cfg file

The /vs/data/vxml/default.cfg file contains configuration data for the AvayaVXI process. Under most circumstances, you do not need to make changes to this file. However, there are a few situations in which you must open this file and edit the value of a configuration setting.

Note:
Any changes you make to the default.cfg file are not effective until the Avaya VXI process has been restarted. The easiest way to restart the Avaya VXI process is to stop the voice system (using the stop_vs command) and start it again (using the start_vs command). For more information on how to use these commands, see start_vs command and stop_vs command.

Increasing the loop count

The number of times that a VoiceXML application can loop through different form items is specified by the client.vxi.maxLoopIterations parameter in the default.cfg file. The default is 1000, which should be enough for most applications. However, if an application has a legitimate reason to have more loops, you can increase the value of this parameter.

Transfer configuration requirements

With VoiceXML you cannot do a blind transfer (<transfer bridge="false" ....>) over PRI. The call can come in over PRI, but you must set the outdial signaling group transfer parameter (client.tel.outdialgroup in the default.cfg file) to a signaling group that is line-side T1, or loop start. Note that the entire signaling group used for the transfer must be line-side T1 or loop start, since any available resource in the signaling group could be used for the transfer.

For bridge transfer (<transfer bridge="true" ....>), PRI is supported.

When using the <transfer> element, the destexpr attribute supports the tel URL scheme defined in the Internet standard RFC2806, "URLs for Telephone Calls." For more information, see http://www.ietf.org/rfc/rfc2806.txt.

Caching parameters

You can set the client.inet.cacheEntryExpTimeSec parameter in the default.cfg file to specify the number of seconds used to determine expiration time when no other expiration time is available for a cache entry. For example, this parameter would be used if the VoiceXML document does not provide metadata fields for Expires or Last-Modified in the header.

The default value for this parameter is 86400, which means that a page expires after one day.

Recognition timeout parameters

You can set the following recognition timeout parameter in the default.cfg file:

The value for each timeout paramenter should be specified in seconds, for example, timeout=10s. For more information about these timeout parameters, refer to the VoiceXML Specification.

� 2002 Avaya Inc. All Rights Reserved.