Dial Pattern Configuration

A dial pattern defines the prefix and pattern that the Oracle Enterprise Communications Broker (Oracle Enterprise Communications Broker) receives and defines the transformation that the system performs.

Only one transformation type is valid for each prefix and pattern match. The system displays an error when you try to configure multiple transformation types. Transformation types include replacement prefix, replacement URI, and Go to context. The following table shows examples of patterns, the transformation types, and the results of the transformation.

Prefix and pattern	Transformation type	Result
8 - xxxx	Replacement prefix	Replace with configured digits, which in this case are suitable for an outside line.
911	Replacement URI	Insert the configured service URN for emergency services.
*123	Go to context	Present the prefix/pattern to another context. Matching occurs based on the target context's configured dial patterns.

Overlapping dial pattern matches in the same context that result in finding the same target number produce configuration errors. Such errors produce an ambiguity that the system cannot resolve, so it does not forward the message. You must configure patterns, especially those that use encoding characters, very carefully to avoid ambiguities that the system cannot resolve.

When overlapping patterns result in the same target number, the system forwards to that number without error. When the system finds overlapping patterns in different contexts, the system chooses the most specific context as a match. Child contexts are more specific than parent contexts. When configuring dial patterns, Oracle recommends keeping them unique even across contexts.