Configuration data is supplied using a node TelURLLocale entry
in the configuration file. (usually default.cff).
The Secondary keywords of this configuration entry are used as follows:
- InternationalAccess
- The digits that should be inserted in place of the ‘+’ character
in a global URL, when dialing from the Blueworx Voice Response system. These digits that should
to be inserted depend on how the Blueworx Voice Response system is connected to the International
network (direct or through a PBX) and the country in which the Blueworx Voice Response system
is operating. For example if a Blueworx Voice Response system is connected directly to the network
in UK the InternationalAccess is 00. If the system is attached
to a PBX where you need to dial 9 for an external call the InternationalAccess is 900.
- LocalContext
- The digits that define the Local Area within the Network to which the Blueworx Voice Response system
is connected. For example if a Blueworx Voice Response system is connected to the Winchester
area of the UK network, the LocalContext is 01962.
- GlobalContext
- The digits that define the global area within which the Blueworx Voice Response system
is connected. For example +44 indicates that the Blueworx Voice Response system is connected
somewhere in the UK. Or +441962 indicates it is connected in the Winchester
area in the UK
Blueworx Voice Response relates these fields to the URL in the following ways:
- Global URLs
- If a global URL does not have a context specifier, Blueworx Voice Response simply replaces
the "+" character with the InternationalAccess digits. If the global
URL does have a context specifier (it is allowed but not mandatory for global
URLs) Blueworx Voice Response checks for a match between the global URL context specifier and
the digits in the GlobalContext field, and if they don’t match,
the global URL will be invalid.
- Local URLs
- Must have a context specifier (RFC 2806). Blueworx Voice Response checks
that the context specifier of a local URL exists, otherwise the URL will be
invalid. If the context specifier exists it MUST match the digits of the LocalContext or GlobalContext field otherwise the URL will
be invalid.
A Local URL can have more than one context specifier.