The following diagram shows example extension numbers for the medium to large enterprise model that must be reachable. The key characteristic for this model is the overlap of dial patterns, called contexts, across branch locations.

In this example, specific dial patterns are configured for the acme context that each child context inherits. These dial patterns provide the Oracle Enterprise Communications Broker with the means of distinguishing between branches, even though the extension patterns still begin with the same number.

Dial Patterns Configured for the acme Context

Each child context inherits these dial patterns from the acme context, providing you with a means of hierarchically assigning context.

In contrast to the small enterprise model, note the use of dial patterns specific to each branch. These contexts work in conjunction with the parent context's parents, delivering signaling with the enterprise's own prefixes to the branch's PBX.

Dial patterns configured for the acme.bedford context

Dial Patterns Configured for the acme.madrid Context

Dial Patterns Configured for the acme.berlin Context

Applicable user database entries

In contrast to the small enterprise model, note the use of dial patterns specific to each branch.

This configuration provides the results shown in the following table.