The following CSV file fields must be specified to import a CSV file that is used to build XML route tables:

• operation—Add or delete operations for routes in a route set
• public identifier (pub-id)—A public identifier in the form of a telephone number or prefix (for example, NPA-NXX) used in LRT lookup. It is referred to in the LRT XML as object “user” of type “E164”. The Pub Id (or the Pub Id formula and the associated fields required to generate Pub Id): identified in the LRT XML as the object “next” of type “regex”. The Pub Id can be a string value if the route set’s Pub Id type is set to string. Pub Id can be directly imported or edited or it could be the result of the record’s formula. The regex in the LRT file is the URI scheme used by the network attribute to route the call.
• Range Start — A Numerical value in the format of E164 that specifies the start value for a contiguous range of DID telephone numbers. Range start can be directly imported or edited.
• Range End — A Numerical value in the format of E164 that specifies the end value for a contiguous range of DID telephone numbers. Range End can be directly imported or edited.
• Session establishment data (SED or the SED formula and the associated fields required to generate SED)—Identified in the LRT XML as the object “next” of type regex. SED can be directly imported or edited or it could be the result of the record’s formula. The regex in the LRT file is the URI scheme used by the network attribute to route the call.

  Note:

  The Range start and Range End parameters are required when you select the Route set pubid type as Range. PubId and PubId formula Attributes are not valid for a Route set of type Range.

  Note:

  Any other combination of fields can be empty, unless they are included in the formula field of the record for which an error should be reported in the import log. A formula specified in Oracle Communications Route Manager during import is applied globally and stored with each record during the import operation. A value supplied in the formula field of a record has precedence over the formula specified in Oracle Communications Route Manager during the import process. The order and preference determines the order of the numbers in the XML file. The lowest number appears first.

The Oracle Communications Route Manager application creates an LRT file by first importing individual routes from a CSV file. These routes are stored in the database and grouped into a route set. The database also contains a list of devices that the LRT file resides upon. This list is used when an update task refreshes the LRT information for a specific route set. The LRT file is gzipped and placed at a specified location on the device. Once the file has been successfully transferred to a device, an action can be issued to each device to load the file. The LRT file location on the device is /code/lrt. You can also import an LRT file from a device into Oracle Communications Route Manager. See the View LRT Files section for more information.

<?xml version="1.0" encoding="UTF-8"?>
<localRoutes>
 <route>
<user type="E164">9999999</user>
 		<next type="regex">!^.*$!sip:04580090001@192.168.202.34:5060!</next>
 	</route>
 	<route>
<user type="E164">98888888</user>
 		<next type="regex">!^.*$!h323:\7777777@172.16.202.33:1720!</next>
 </route>
 <route>
<user type="E164">7777777</user>
 		<next type="regex">!^.*$!sip:8888888@192.168.202.34:9001!</next>
        <next type="regex">!^.*$!sip:8888888@192.168.202.35:9001!</next>
        <next type="regex">!^.*$!sip:8888888@192.168.202.36:9001!</next>
 </route>
 <route>
<user type="E164">7817654321</user>
 		<next type="regex">!^.*$!sip:7817654321@192.168.200.223:5060!</next>
 </route>
<route>
<user type="E164">9817654321</user>
 		<next type="regex">!^.*$!sip:9817654321@172.16.0.223:5060!</next>
 </route>
<route>
<user type="E164">10061</user>
 		<next type="regex">!^.*$!sip:10061@172.16.0.198:5060!</next>
 </route>
       </localRoutes>

<?xml version="1.0" encoding="UTF-8" ?> 
<localRoutes> 
<route format="weighted"> 
<description>testsample</description> 
<user type="E164">11</user> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
<next prio="1" weight="30" type="regex">!^.*$!sip:\0@SAG-Mediafone!</next> 
</route> 
</localRoutes> 

<?xml version="1.0" encoding="UTF-8"?>

-<localRoutes type="range">


-<route>

<user type="range" rangeEnd="558900" rangeStart="558855"/>

<next type="regex">!(^.*$)!sip:134454410.199.197.260;ild=1!21</next>

<next type="regex">!(^.*$)!sip:1988954210.199.190.261;ild=1!212</next>

<next type="regex">!(^.*$)!sip:19889509210.189.197.269;ild=1!988</next>

</route>


-<route format="weighted">

<user type="range" rangeEnd="9889123" rangeStart="8990997"/>

<next type="regex" weight="90" prio="10">!(^.*$)!sip:134454410.199.190.261!12</next>

<next type="regex" weight="70" prio="100">!(^.*$)!sip:1988954210.189.197.269!250</next>

<next type="regex" weight="70" prio="80">!(^.*$)!sip:134454410.189.197.87!21</next>

</route>


-<emsVersion>

<routeSetType>SBC</routeSetType>

<version>1</version>

<dateUpdated>2000-12-10 06:05:22</dateUpdated>

</emsVersion>

</localRoutes>

The following table contains a list of route entries and a description of each that can be imported from a CSV file or entered through the GUI.