The Routing screens provide administration of the Session Manager SIP routing rules. The management screens consist of configurable elements.
You can import a large number of the elements in System Manager by using XML files. You can export each of the elements or the entire routing configuration to XML files.
System Manager imports the Routing element data in the following order:
Domains
Locations
Adaptations
SIP Entities
Entity Links
Time Ranges
Routing Policies
Dial Patterns
Regular Expressions
Note:
The routing elements depend on each other. An import operation fails if the required elements do not already exist in the database or do not exist in the same import operation. For example, the import of a dial pattern with domain name avaya.com will fail if:
No such domain exists in the database.
An XML file containing this domain is not imported in the same import operation as the dial pattern.
System Manager Routing Import/Export supports:
Importing each element separately as a single XML file containing many entries.
Compressing the XML files using ZIP compression to decrease the size of the files that need to be uploaded to the System Manager server.
Note:
File compression is especially important when importing large files exceeding 10 MB or more.
Importing several elements or all the elements in a single ZIP file containing many XML files.
Exporting a single type of entity or all of the entities. When exporting all the entities, the exported files are contained in a single ZIP file.
The Import operation does not halt if one of the elements fails validation. The failed element is not added to the database, and the import operation continues with the next element.
An audit log provides details of the failed and successful import operations. The log is located at the following location:/var/log/Avaya/mgmt/nrp/nrpaudit.log. You can access the file through the System Manager command prompt.
If an imported element already exists in the System Manager database, the values in the new element will overwrite the older element.
For example, if a domain with the name avaya.com already exists in the database, the note, type, and default values are overwritten by the new element.
The Dial Pattern is an exception for this rule. You cannot import a dial pattern with elements such as <digitpattern>,<maxdigits>,<mindigits>,<sipdomainName> and <routingoriginationName> already present in the database. The import attempt will fail.
Important:
When adding subcomponents to an existing element, include all the parameters associated with the element in the import XML file. For example, if you add digit patterns to an adaptation, make sure the adaptation import includes all of the patterns and not just the patterns you are adding to the adaptation.
