Large Enterprise Model - v2
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
| Prefix | Pattern | Country Code | Replace Prefix | Replace URI | Go To Context |
|---|---|---|---|---|---|
| 101 | acme.bedford | ||||
| 102 | acme.madrid | ||||
| 103 | acme.madrid | ||||
| 555 | helpdesk@acme.com |
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
| Prefix | Pattern | Country Code | Replace Prefix | Replace URI | Go To Context |
|---|---|---|---|---|---|
| 4xxx | 781555 |
Dial Patterns Configured for the
acme.madrid Context
| Prefix | Pattern | Country Code | Replace Prefix | Replace URI | Go To Context |
|---|---|---|---|---|---|
| 4xxx | 91555 |
Dial Patterns Configured for the
acme.berlin Context
| Prefix | Pattern | Country Code | Replace Prefix | Replace URI | Go To Context |
|---|---|---|---|---|---|
| 4xxxxx | 555 | ||||
| 111 | berlinhelpdesk@acme.com |
Applicable user database entries
| Number | Dialing Context | Agent |
|---|---|---|
| +17815551xxx | PBX-BED | |
| +34915552xxx | PBX-MAD | |
| +4955553xxxxx | PBX-BER |
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.
| From | Dial String | Transformation | Result |
|---|---|---|---|
| acme.bedford | 4321 | +17815554321 | Call is directed to PBX-BED as e.164 |
| acme.bedford | 1024322 | +34915554322 | Call is directed to PBX-MAD as e.164 |
| acme.bedford | 103432356 | +495555432356 | Call is directed to PBX-BER as e.164 |
| acme.madrid | 4322 | +34915554322 | Call is directed to PBX-MAD as e.164 |
| acme.madrid | 1014321 | +17815554321 | Call is directed to PBX-BED as e.164 |
| acme.madrid | 103432356 | +495555432356 | Call is directed to PBX-BER as e.164 |
| acme.berlin | 432356 | +495555432356 | Call is directed to PBX-BER as e.164 |
| acme.berlin | 1014321 | +17815554321 | Call is directed to PBX-BED as e.164 |
| acme.berlin | 1024322 | +34915554322 | Call is directed to PBX-MAD as e.164 |