http://docwiki.cisco.com/w/index.php?title=Cisco_Unified_MeetingPlace_Release_6.1_--_About_Translation_Tables&feed=atom&action=historyCisco Unified MeetingPlace Release 6.1 -- About Translation Tables - Revision history2017-03-26T08:05:44ZRevision history for this page on the wikiMediaWiki 1.16.0http://docwiki.cisco.com/w/index.php?title=Cisco_Unified_MeetingPlace_Release_6.1_--_About_Translation_Tables&diff=39158&oldid=prevMeetingPlace Moderator: 1 revision2011-03-28T21:11:29Z<p>1 revision</p>
<table style="background-color: white; color:black;">
<tr valign='top'>
<td colspan='1' style="background-color: white; color:black;">← Older revision</td>
<td colspan='1' style="background-color: white; color:black;">Revision as of 21:11, 28 March 2011</td>
</tr></table>MeetingPlace Moderatorhttp://docwiki.cisco.com/w/index.php?title=Cisco_Unified_MeetingPlace_Release_6.1_--_About_Translation_Tables&diff=39157&oldid=prevMeetingPlace Moderator: Created page with "Cisco Unified MeetingPlace Release 6.1 > [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Unified MeetingPlace Audio Server, Release 6.1|Cisco Unified MeetingPlace A..."2011-01-28T18:15:12Z<p>Created page with "<a href="/wiki/Cisco_Unified_MeetingPlace_Release_6.1" title="Cisco Unified MeetingPlace Release 6.1">Cisco Unified MeetingPlace Release 6.1</a> > [[Cisco Unified MeetingPlace Release 6.1 -- Cisco Unified MeetingPlace Audio Server, Release 6.1|Cisco Unified MeetingPlace A..."</p>
<p><b>New page</b></p><div>[[Cisco Unified MeetingPlace Release 6.1]] > <br />
[[Cisco Unified MeetingPlace Release 6.1 -- Cisco Unified MeetingPlace Audio Server, Release 6.1|Cisco Unified MeetingPlace Audio Server]] <br />
> [[Cisco Unified MeetingPlace Release 6.1 -- Configuring the Audio Server|Configuring]]<br />
> [[Cisco Unified MeetingPlace Release 6.1 -- Configuring Translation Tables|Translation Tables]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
A translation table contains rows of expressions that define how a string that is dialed out should be translated. The expressions are made up of characters.<br />
<br />
<br />
Cisco Unified MeetingPlace supports 16 different translation tables and 32 different port groups. You can assign different translation tables to different users to customize the translations available to specific users.<br />
<br />
<br />
<br />
== Dialing String Characters ==<br />
<br />
<br />
Cisco Unified MeetingPlace MeetingTime validates all characters entered into a translation table whenever an outdial is requested. Cisco Unified MeetingPlace does a similar validation of all characters it receives for outdial. Invalid characters in the dialing string abort the outdial process.<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Valid Characters|Valid Characters]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Control Characters|Control Characters]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Formatting Characters|Formatting Characters]]<br />
<br />
<br />
=== Valid Characters ===<br />
<br />
<br />
The following table lists valid characters in the dialing string.<br />
<br />
<br />
'''Note: ''' The fact that a character is valid does not mean that the system always accepts it. Accepting a character string depends on the translation table and the entries in that table.:<br />
<br />
{| border = 1 <br />
|-<br />
!Character<br />
!Description<br />
|-<br />
|<br />
<br />
0 - 9<br />
|<br />
<br />
Dial a DTMF/rotary digit 0 - 9<br />
|-<br />
|<br />
<br />
A<br />
|<br />
<br />
Dial a DTMF digit A<br />
|-<br />
|<br />
<br />
B<br />
|<br />
<br />
Dial a DTMF digit B<br />
|-<br />
|<br />
<br />
C<br />
|<br />
<br />
Dial a DTMF digit C<br />
|-<br />
|<br />
<br />
D<br />
|<br />
<br />
Dial a DTMF digit D<br />
|-<br />
|<br />
<br />
<nowiki>*</nowiki><br />
|<br />
<br />
Dial a DTMF digit *<br />
|-<br />
|<br />
<br />
<nowiki>#</nowiki><br />
|<br />
<br />
Dial a DTMF digit #<br />
|}<br />
<br />
<br />
<br />
=== Control Characters ===<br />
<br />
<br />
The following table lists control characters, which are characters that are not dialed.<br />
<br />
{| border = 1 <br />
|-<br />
!Character<br />
!Description<br />
|-<br />
|<br />
<br />
,<br />
|<br />
<br />
Wait 2 seconds before processing the next character in the string.<br />
|-<br />
|<br />
<br />
R<br />
|<br />
<br />
Wait for answer supervision from the far end. See the [[Cisco Unified MeetingPlace Release 6.1 -- Working with Translation Tables#About Answer Supervision|About Answer Supervision]] for more information.<br />
|}<br />
<br />
<br />
<br />
<br />
=== Formatting Characters ===<br />
<br />
<br />
The following table lists formatting characters, which are characters that are ignored.<br />
<br />
{| border = 1 <br />
|-<br />
!Character<br />
!Description<br />
|-<br />
|<br />
<br />
(<br />
|<br />
<br />
Open parenthesis<br />
|-<br />
|<br />
<br />
)<br />
|<br />
<br />
Close parentheses<br />
|-<br />
|<br />
<br />
-<br />
|<br />
<br />
Dash<br />
|-<br />
|<br />
<br />
<space><br />
|<br />
<br />
Space<br />
|}<br />
<br />
<br />
<br />
<br />
== Regular Expressions ==<br />
<br />
<br />
Regular expressions are formal descriptions of text (character) strings that allow for flexible and powerful matching operations. Regular expression matching lets you test whether a string fits into a specific syntactic shape and also lets you search a string for a substring that fits a pattern. Cisco Unified MeetingPlace supports all UNIX regular expression operators, which allows for very powerful matching and string substitutions.<br />
<br />
<br />
The simplest regular expression describes a particular string, for example "210". The string "210", when considered as a regular expression, matches only the string "210".<br />
<br />
<br />
Non-trivial regular expressions allow special characters to match more than one string. The operator "\|" describes the "or" operation and the operators "[" and "]" describe a set of characters. For example, the regular expression "210\|212" matches either the string "210" or the string "212". The regular expression "21[0-2]" matches the strings with last digit between 0 and 2; that is, "210", "211", and "212".<br />
<br />
<br />
The following table lists the most common regular expression operators.<br />
<br />
{| border = 1 <br />
|-<br />
!Operator<br />
!Description<br />
|-<br />
|<br />
<br />
.<br />
|<br />
<br />
Dot, matches any single character.<br />
|-<br />
|<br />
<br />
<nowiki>*</nowiki><br />
|<br />
<br />
Suffix, match 0 or more occurrences of the previous regular expression.<br />
|-<br />
|<br />
<br />
+<br />
|<br />
<br />
Like *, but matches 1 or more occurrences <br />
|-<br />
|<br />
<br />
?<br />
|<br />
<br />
Like *, but matches 0 or 1 of the preceding character.<br />
|-<br />
|<br />
<br />
[ ... ]<br />
|<br />
<br />
Encloses a character set.<br />
|-<br />
|<br />
<br />
\<br />
|<br />
<br />
Quotes a regular expression operator, or introduces special constructs.<br />
|-<br />
|<br />
<br />
\( ... \)<br />
|<br />
<br />
Grouping construct, lets you match a sub-string for future reference.<br />
|-<br />
|<br />
<br />
\|<br />
|<br />
<br />
Or operator, select either regular expressions.<br />
|}<br />
<br />
<br />
<br />
Grouping of expressions can be done by using "\". For example, "\0" refers to the complete expression, and "\1" refers to the first group construct.<br />
<br />
<br />
The following examples should help understand how regular expressions are used in Cisco Unified MeetingPlace. Under the "Match" column (which corresponds to the "From" column) are the regular expression strings against which the input string will be matched. If the input string does not match the regular expression string, an attempt is made to match the regular expression string on the next line. If the input string does match, then it will be transformed by the string under the "Substitute for" column (which corresponds to the "To" column).<br />
<br />
{| border = 1 <br />
|-<br />
!Match<br />
!Substitute for<br />
!Explanation<br />
|-<br />
|<br />
<br />
0<br />
|<br />
<br />
200<br />
|<br />
<br />
Substitute string 0 for 200. That is, when dialing "0" for the operator, dial extension "200"<br />
|-<br />
|<br />
<br />
2..<br />
|<br />
<br />
\0<br />
|<br />
<br />
When dialing any extension in the 200 through 299 range, do no translation.<br />
|-<br />
|<br />
<br />
976.......<br />
|<br />
<br />
0<br />
|<br />
<br />
When dialing any number that starts with 976 and follows with any other 7 digits, dial 0 instead. (This is a type of blocking.)<br />
|-<br />
|<br />
<br />
803111<br />
|<br />
<br />
-<br />
|<br />
<br />
When dialing 803111, go offhook on the port and dial no digits (only seize the port).<br />
|}<br />
<br />
<br />
<br />
<br />
The advantage of regular expressions is that they are very flexible and can translate virtually anything into anything.<br />
<br />
<br />
The disadvantages of regular expressions are that they are complex, hard to understand, not user friendly, and they may require lots of entries to be able to completely cover all cases, especially to guarantee that all calls that should be blocked are actually blocked.<br />
<br />
<br />
<br />
== Translation Tables without Regular Expressions ==<br />
<br />
''NOTE: This content only applies for Cisco Unified MeetingPlace Release 6.0 Maintenance Release 5 (MR5) and later.''<br />
<br />
<br />
Translation tables that do not use regular expressions are similar to tables with regular expressions. The main difference is in the way that patterns are specified in the From: and To: columns. Translation tables without regular expressions, called NOREGEXP, use more simplified patterns.<br />
<br />
<br />
Translation tables without regular expressions use two kinds of patterns: blocking and non-blocking. <br />
<br />
<br />
<br />
=== Blocking Patterns ===<br />
<br />
Blocking patterns are used to block outdials to certain regions while non-blocking patterns allow outdials and can be used for translations of source numbers. Blocking patterns allow only digits and dots and match any string that starts with that pattern. For example, the blocking pattern "800" matches the strings 800, 8001, 800123R and so on. The blocking pattern "800.." matches any five or more digit strings that start with 800.<br />
<br />
An entry in the table is considered blocking if the port group is set to “BLOCK”. In this case, we recommend setting the To: column to 0. <br />
<br />
Examples:<br />
<br />
{| border = 1 <br />
|-<br />
!<nowiki>#</nowiki> From<br />
!To<br />
!Group<br />
!DestType<br />
!Comment<br />
|-<br />
|<br />
800<br />
|<br />
0<br />
|<br />
BLOCK<br />
|<br />
GENERIC<br />
|<br />
Block 800 calls<br />
|-<br />
|<br />
1800<br />
|<br />
0<br />
|<br />
BLOCK<br />
|<br />
GENERIC<br />
|<br />
Block 800 calls<br />
|}<br />
<br />
<br />
<br />
<br />
=== Non-Blocking Patterns ===<br />
<br />
Non-blocking patterns allow digits, dots, and the letter "R" for answer supervision (but only at the end of the pattern). Non-blocking patterns require an exact match. For example, the pattern "800" matches only string 800, pattern "800.." matches only five digit strings that start with 800, and the pattern "800..R" matches five digit strings that start with 800 and end with the letter "R". <br />
<br />
For non-blocking patterns, the To: column specifies how translations are performed. The rules are basically the same as for regular expression-based tables. The difference is that "\0" is the only escape sequence allowed and is used to specify that the complete source string should be copied. <br />
<br />
Examples:<br />
<br />
<br />
{| border = 1 <br />
|-<br />
!<nowiki>#</nowiki> From<br />
!To<br />
!Group<br />
!DestType<br />
!Comment<br />
|-<br />
|<br />
........<br />
|<br />
\0<br />
|<br />
3<br />
|<br />
GENERIC<br />
|<br />
No translation for 8 digits<br />
|-<br />
|<br />
........R<br />
|<br />
\0<br />
|<br />
3<br />
|<br />
GENERIC<br />
|<br />
No translation for 8 digits<br />
|-<br />
|<br />
44.........<br />
|<br />
9011\0<br />
|<br />
3<br />
|<br />
GENERIC<br />
|<br />
Add 9011 for 11 digit dialing UK<br />
|-<br />
|<br />
44.........R<br />
|<br />
9011\0<br />
|<br />
3<br />
|<br />
GENERIC<br />
|<br />
Add 9011 for 11 digit dialing UK<br />
|}<br />
<br />
<br />
=== "ALL" Pattern ===<br />
<br />
There is one special pattern that is used to match any string: "ALL". It should be used only at the end of the list to specify what to do with the source number if it does not match any of the previous patterns. <br />
<br />
Examples:<br />
<br />
{| border = 1 <br />
|-<br />
!<nowiki>#</nowiki> From<br />
!To<br />
!Group<br />
!DestType<br />
!Comment<br />
|-<br />
|<br />
ALL<br />
|<br />
0<br />
|<br />
BLOCK<br />
|<br />
GENERIC<br />
|<br />
Block all other calls<br />
|}<br />
<br />
or<br />
<br />
{| border = 1 <br />
|-<br />
!<nowiki>#</nowiki> From<br />
!To<br />
!Group<br />
!DestType<br />
!Comment<br />
|-<br />
|<br />
ALL<br />
|<br />
\0<br />
|<br />
3<br />
|<br />
GENERIC<br />
|<br />
No translation<br />
|}<br />
<br />
<br />
=== Order of Table Entries ===<br />
<br />
The general rule for the order of table entries is similar to tables with regular expressions. The search always starts from the first entry in the table until a match is found. You should first specify blocking patterns and then follow with translation patterns. The "ALL" pattern comes at the end.<br />
<br />
<br />
Users can specify a maximum of 256 entries in one translation table. To specify that a translation table does not use regular expressions, you must add the string "NOREGEXP" as a comment in the first line of the file used to initialize the table, as follows:<br />
<br />
<nowiki># NOREGEXP</nowiki><br />
<br />
Note the space between # and NOREGEXP.<br />
<br />
<br />
If the xlinit utility recognizes that the file does not use regular expressions, it will print the following:<br />
<br />
''This translation table does not use regular expressions.'' <br />
<br />
If this line is not printed, the table uses regular expressions.<br />
<br />
<br />
Translation tables can use either regular or non-regular expressions, but any one table cannot use both at the same time.<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Format of the Translation Table Input File ==<br />
<br />
<br />
There are 16 active Cisco Unified MeetingPlace digit translation tables, numbered from 0 to 15, at any time in Cisco Unified MeetingPlace. The default configuration for a translation table is no translation (which means that the converted string is identical to the input string).<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Comments|Comments]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Columns|Columns]]<br />
<br />
<br />
=== Comments ===<br />
<br />
<br />
All lines that start with a "#" are considered comments and are skipped. Lines that start with the new line character or a space are also skipped.<br />
<br />
<br />
=== Columns ===<br />
<br />
<br />
Each entry in a translation table corresponds to a single row, composed of five columns, separated by at least one blank space or tab. The five columns are:<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#From Column|From Column]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#To Column|To Column]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Port Group Column|Port Group Column]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Destination Type Column|Destination Type Column]]<br />
* [[Cisco Unified MeetingPlace Release 6.1 -- About Translation Tables#Comment Column|Comment Column]]<br />
<br />
<br />
==== From Column ====<br />
<br />
<br />
Corresponds to the expression to be matched. This column contains regular expressions against which the input string is checked for a match. If there is no match, then the next line is checked for a match. If there is a match, then the "To" column is utilized. A maximum of 40 characters can be used in this field.<br />
<br />
<br />
==== To Column ====<br />
<br />
<br />
Corresponds to what the expression should be translated to. If the input string matches the regular expression in column 1 (the "From" column), the input string is string-substituted based on the entry in this column (the "To" column). The converted string will be a string of DTMF digits and dialing commands that Cisco Unified MeetingPlace outdials when placing the call. To seize a port and dial no digits, enter a "-" in this column. A maximum of 40 characters can be used in this field.<br />
<br />
<br />
==== Port Group Column ====<br />
<br />
<br />
Corresponds to the port group to which ports must belong in order to be selected when placing the call. The valid port groups are between 0 and 15. For an entry that can be used by ports belonging to any port group, use the string "ANYGROUP".<br />
<br />
<br />
==== Destination Type Column ====<br />
<br />
<br />
Contains the type of telephony device that is expected to answer the outdial. The valid destination device types are:<br />
* GENERIC-Typical (Plain Old Telephone Service [POTS]) type of device, where Cisco Unified MeetingPlace will play prompts.<br />
* AUTOANSWER-Auto answer device, where no user is expected to press digits.<br />
* MEETINGPLACE-Used for simple networking, where another Cisco Unified MeetingPlace system is expected to answer the outdial. Basically the same as an Auto Answer device, except that a "*" DTMF tone is dialed at the end of the string to get back into the meeting.<br />
<br />
<br />
==== Comment Column ====<br />
<br />
<br />
Contains a comment describing the purpose of the substitution and is useful for the person modifying or analyzing the digit translation table. A maximum of 40 characters can be used in this field.<br />
<br />
<br />
<br />
== Order of Entries and Route Optimization ==<br />
<br />
<br />
The ordering of the rows in the translation table file is very important because it specifies which translation will take place first. It allows you to block calls and to do some simple route optimization based on port groups.<br />
<br />
<br />
=== Simple Route Optimization ===<br />
<br />
<br />
Although in general CBXs (Computer-Controlled Branch Exchanges) and PBXs (Private Branch Exchanges) have sophisticated and flexible route optimization capabilities, the translation tables allow for a simple route optimization mechanism. For example, if the following two lines are in the digit translation file:<br />
<br />
{| border = 1 <br />
|-<br />
!From<br />
!To<br />
!PortGroup<br />
!DestType<br />
!Comment<br />
|-<br />
|<br />
<br />
2..<br />
|<br />
<br />
8247\0<br />
|<br />
<br />
0<br />
|<br />
<br />
GENERIC<br />
|<br />
<br />
Use company-internal tie trunks and port group 0.<br />
|-<br />
|<br />
<br />
2..<br />
|<br />
<br />
94089887\0<br />
|<br />
<br />
1<br />
|<br />
<br />
GENERIC<br />
|<br />
<br />
Use the PSTN and port group 1.<br />
|}<br />
<br />
<br />
<br />
the first entry is always used first. Only if all ports in group 0 are busy would the system use the next entry in the translation table, in this case port group 1. If all the ports in group 1 are busy, the system rejects the outdial request.<br />
<br />
<br />
In the preceding example, the system first selects what is probably the cheapest route (company internal tie trunks) before placing a call over the public network.<br />
<br />
<br />
When a number can be dialed using more than one port group, the key to route optimization is to include the digit translation entry for the preferred group first.<br />
<br />
<br />
[[Category: Unified MeetingPlace Release 6.1]]</div>MeetingPlace Moderator