Emergency LRT

The Oracle Communications Unified Session Manager needs to be configured with an emergency LRT to route emergency calls to their destination.

As stated in the previous section, when searching an emergency LRT, any user defined parameter within a Location String may be used as the key to look up next-hop routing information.

LRT files support <user type = string> which enables the Oracle Communications Unified Session Manager to perform searches on free form attributes that may appear in the returned location-string. The <user type = string> value for an entry in the emergency LRT should be set to a part or whole value returned in the CLF’s location string. For example:

<?xml version="1.0" encoding="UTF-8" ?>
<localRoutes>
	<route>
		<user type="string">1234</user>
		<next type="regex">!^.*$!sip:911@192.168.200.140:5060!</next>
	</route>
	<route>
		<user type="string">loc=xxx;noc=yyyy;line-code=zzzz</user>
		<next type="regex">!^.*$!sip:911@192.168.1.139:5060!</next>
	</route>
</localRoutes>

Note:

Given that the Location String is not a well-defined string, care should be taken when defining and configuring the LRT tables.

LRTs must be individually uploaded to both the active and standby systems in an HA node; LRTs are not automatically replicated across nodes.