7 User Configuration

User configuration is a required task. It is, in fact, the only way to assign an agent to a user. Complex VoIP deployments can derive additional benefits from the user database. Examples include contiguous dial strings being deployed across multiple PBXs, making it impossible to identify the target PBX by dial string alone.

When you need a user database, you configure entries for all source and destination numbers that you know require user database support. The user database effectively performs dial plan tasks on individual numbers. Such tasks include identifying a user’s agent and source context. These entries provide the Oracle Enterprise Communications Broker with shortcuts for determining this information.

A user often represents an actual account that exists within an enterprise’s dialing network. Examples of users include an extension, a subscriber or a phone number. Each user may have a source context, which translates into "Default” dialing rules for processing that user’s calls using the appropriate contextual transformation rules and the agent at which they are located.

You can configure this database manually. Alternatively, you can upload user information in a format pre-configured to translate into a user database.