Avaya Administering Aura Session Manager Release 6.1 Manual de usuario descargar pdf (Pagina 240)

100

101

g. Routing Policies

h. Dial Patterns

i. Regular Expressions

The order is decided by analyzing the files internal structure (it must be a well formed

XML as described in this guide). Any file name can be used as long as its extension is

“xml”.

• The Import operation does not halt if one of the elements fails validation. The failed

element will not be added to the database, and the operation will continue to the next

one.

• An audit log provides details on the failed and successful import operations.

• If an imported element already exists in the System Manager database, which means that

there is an element with the same unique identifiers, then the values in the new element

will overwrite the old element.

- For example: if a domain named “avaya.com” already exist in the database, then the

note, type and default values will be overwritten by the new element.

- Dial Pattern is an exception for this rule. It is not possible to import a dial pattern with

elements such as <digitpattern>,<maxdigits>,<mindigits>,<sipdomainName> and

<routingoriginationName> already present in the database. Such an attempt will

fail.

• Every operation in the Routing application is logged to an audit log including the import

operation. A log entry is added for each element that is imported, even if the operation

succeeds or fails. The log is located at the following file:/var/log/Avaya/mgmt/nrp/

nrpaudit.log. The file is accessible through the System Manager Linux Shell.

Note:

The Routing elements depend on each other. An import operation will fail if the needed

elements do not already exist in the database or exist in the same import operation. For

example import of a Dial Pattern with domain name avaya.com will fail if there is no such

domain in the database, or if an XML file containing this domain is not imported in the same

import operation as the Dial Pattern.

Exporting Routing element data

Procedure

1. On the System Manager console, under Elements, click Routing.

2. Click Routing > <Any Routing element>.

3. From the Routing Entity screen, click More Actions > Export <Routing

Element>.

Managing Session Manager routing

240 Administering Avaya Aura

Session Manager November 2010

Comments? [email protected]

1 2 ... 235 236 237 238 239 240 241 242 243 244 245 ... 531 532

Comentarios a estos manuales

Sin comentarios

Avaya Administering Aura Session Manager Release 6.1 Manual de usuario Pagina 240

Comentarios a estos manuales

Relacionado con productos y manuales para Software Avaya Administering Aura Session Manager Release 6.1