Alphanumeric User Database and Call Routing Entries

The Oracle Enterprise Communications Broker (Communications Broker) allows you to enter alphanumeric entries in the User database and in the routing table because it can modify the request URI to use either alphanumeric or numeric entries, depending on the setting you choose for egress-URI-mode.

Egress-URI-mode

When the Communications Broker locates the home agent to which the call is routed, it uses one of the following configurable values from the egress-URI-mode parameter in the Agent configuration to determine whether or not to convert the request URI:

No-conversion (Default)—The Communications Broker adds only the IP address of the Home Agent in the outbound call.
Convert-to-aor— When the incoming URI is a number, the Communications Broker replaces it with the configured address of record in the outbound call.
Convert-to-number—When the incoming URI is an Address of Record, the Communications Broker replaces it with the configured number in the outbound call.

Example

Assume that the User database includes "aor1@oracle.com" for the AOR, "123@oracle.com" for the number, and the destination agent is named Agent123.

When a call comes in, the Communications Broker checks the value in the egress-URI-mode parameter for the destination agent Agent123 and does the following:

If the request URI in the incoming call is "aor1@oracle.com", and the egress-URI-mode for Agent123 is set to "convert-to-number", the Communications Broker modifies the request URI to 123@oracle.com.
If the request URI in the incoming call is "123@oracle.com", and the egress-URI-mode for Agent123 is set to "convert-to-aor", the Communications Broker modifies the request URI to "aor1@oracle.com."
If you set the egress-URI-mode for Agent123 to "no-conversion", the user part of the request URI remains unchanged. The Communications Broker changes only the host part of the request URI to use the IP address of Agent123.

Alphanumeric User Database Entries

In the User Entries configuration, both the Address of Record parameter and the Number or Pattern parameter can accept alphanumeric entries. Note that you can leave either the Address of Record or the Number or Pattern parameter empty, but not both at the same time. The user database supports the following combinations of entries:

Address of Record	Number or Pattern	Home Agent	Dialing Context
username1@company.com	1234567890@company.com	Agent1	region.country
username2@company.com	1234567890	Agent2	region.country
username3@company.com		Agent3	region.country
username1@1.1.1.1	1234567890	Agent3
	11234567890	Agent4
	12324567890	Agent4
	12345678[01-04]	Agent5
	xxxxxxxxx	Agent5

The user database does not support wild card entries in the Address of Record parameter, but the Number or Pattern parameter supports the following wild card patterns:

12345678xx@company.com
12345678xx@country1.company.com
12345678xx@country2.com
123456[01-20]@country.company.com

Example of a valid configuration

The following example shows the Address of Record and the Number or Pattern entered in the User database in a valid configuration, where the entries are properly formatted.

Address of Record	Number or Pattern	Home Agent	Dialing Context
username@company.com	1234567890@company.com	Agent1	region.country

With "convert-to-number" selected, the Communications Broker modifies the request URI to use the number 1234567890@company.com. With "convert-to-aor" selected, the Communications Broker modifies the request URI to use the Address of Record username@company.com.

Example of an invalid configuration

The following example shows an invalid user record which includes two different address of record entries for one user (rows 1 and 2), and duplicate address of records for two different numbers (rows 3 and 4).

Address of Record	Number or Pattern	Home Agent	Dialing Context
username@company.com	1234567890@company.com	Agent1	region.country
user@1.1.1.1	1234567890@company.com	Agent1	region.country
auser@company.com	5551234567@company.com	Agent1	region.country
auser@company.com	0005551234@company.com	Agent1	region.country

Routing Table Entries

The routing table supports the following syntax for alphanumeric entries in the Calling Number and Called Number parameters:

1234567890
123[000-999]
123[x]xxx
1234567890@company.com
user_name@company.com
user.name@1.1.1.1

Dial Plan Lookup

When the Communications Broker attempts a dial plan lookup, it first confirms that the user part of the request-uri is a valid phone number. For a valid number, the Communications Broker performs the dial plan lookup. When user part of request-uri is an alphanumeric string, the Communications Broker skips the dial plan lookup.

ENUM

When the Communications Broker uses a configured route to an ENUM server, it does not convert the request-uri as specified in the destination agent configuration. If the destination agent (returned by the ENUM server) is not reachable, and Communications Broker chooses a backup route from the user database, the Communications Broker converts the request-uri of the outgoing INVITE based on the egress-uri-mode parameter set for the destination agent in the user database.

LDAP

When a user database entry and an LDAP entry both exist, the Communications Broker gives priority to the entry in user database. Conversion of the request-uri is performed based on the configuration of the destination agent. If a user database entry does not exist, LDAP takes the precedence and the system does not convert the request-uri.