Uri To Telephone Number Translation Table - Avaya S6200 Administration And Maintenance

Configuring the System

URI to telephone number translation table

S6x00 implements call branding by allowing different participants dialing into the system to be
routed to different call flows. The routing is determined by entries in the UriToTelnum.tab file,
which is stored in the /usr/ipcb/config directory.
This file is similar in structure to the TelnumToUri.tab file. The file contains one or more
comments followed by one or more lines containing data. Each data line contains three pieces
of information: TelnumPattern, TelnumConversion, and Comment.
data.
Table 10: elnumToUri.tab file
Entry
TelnumPattern
TelnumConversion
Comment
The last entry in the file is always an asterisk (*), followed by an ampersand (@), and then
another asterisk. This value is the default used for call routing when the call comes into the
system via a URI that is not defined in the file.
Note:
Specify an operator dial in string in the URI to Telnum conversion table by using
Note:
this format for operator dial in strings:
op<number>x<operator Channel number>@<ip address>
42 Administration and Maintenance of the S6200/S6800 Servers
Description
The IP address of the line that the call dialed in. This entry
always begins with the characters "sip:" followed by the dial
out attendant number, the ampersand character (@), and
ends with the IP address of the IP phone, proxy server, or
media gateway.
Since the attendant number may not be known, this entry
usually contains wildcards for pattern matching. For
example, *@10.221.10.11, matches any call delivered via
that IP address.
The system replaces the TelnumPattern with this entry and
then routes it to the corresponding call flow.
Any text that identifies the DTMF. Some examples are:
"bridge", "media gateway", or "proxy server."
Table 10 describes these