telephony/NumbersDomains
A collection of master domain defining external number bindings to cluster domains.
Case: the system is connected to a PSTN provider. One account, one multilink connection, a pool of external numbers. The pool of numbers is distributed across the child domains of the cluster. Billing is connected.
Objective 1: When communicating with billing (for PSTN leveraged calls), pass as the client domain the specific cluster worker domain that has been allocated the appropriate number. Goal 2: optimize the setup by eliminating copying and enumerating numbers in multiple routing rules and presentation rules in different domains, reducing the number of entities (routing rules and presentation rules) to a primitive minimum.
Storage Type: category.
| Field | Description |
|---|---|
|
Identifier |
|
Domain name in the cluster |
|
List of external numbers allocated from the pool to the specified domain. Each item is either a specific external number or a range (specified as "/dia/<NOMER>+N", where <NOMER> is the external number and N is the number of additional numbers in sequence, so +10 specifies a range of 11 numbers). |
|
The primary number used as the source number in outgoing calls from the domain through a single connection. If no number is specified, the first number from the property is assigned as the main number 'numbers'. Applies representation rule when routing a call from a domain to another domain serving a connection to the PSTN. To apply the call initiator number as a modifier, you must set the macro "{nd}". |
Mechanism of operation
The service executed within the role mware generates the table by expanding all numbers with respect to ranges. For each number it allows you to find out the domain, and for each domain it allows you to find out the main number.
-
When communicating with the billing system, the system determines the associated work domain by the local number in the PSTN arm, and passes it as the client domain to RADIUS. By default, the domain in which the corresponding ISP account is configured.
-
In routing rules in a domain with an ISP account, you can specify the macro "{nd}" as a modifier for a rule with the action type 'To another domain'. In this case, if the destination number received by the rule filter is stored in the NumbersDomains collection, the corresponding domain will be substituted. If the number does not match any domain, or no domain is found, the next rule or rejection will be applied. This allows you to reduce customization by not multiplying either rules or tables with numbers, but to manage with one single primitive rule.
-
You can use the macro prefix "/nd/…" (for example, "/nd/7XXXXXXXXXXXXXX") in the mask-filtering numbers in the routing rules of working domains (for example, "/nd/7XXXXXXXXXXXXXXXXXX") - the system will first filter and then check this number against the domain in the NumbersDomains collection. It helps to differentiate the directions: local external numbers are accepted for service within the domain, and other external numbers are directed to the domain with connection to PSTN. This reduces the configuration, eliminates the need to create several rules in each of the working domains listing the numbers allocated to the domain, and to make do with one primitive rule in each working domain.
-
In normalization rules, you can specify the "{nd}" macro as the source number modifier. Then when crossdomain calls are made from work domains to a domain with PSTN connection, the NumbersDomains collection will be searched for the source domain and the corresponding mainNumber will be substituted. Reduces customization by eliminating copying and enumerating numbers for each domain. A single primitive representation rule in a domain with a connection to the PSTN.
In total, it is enough to specify each of the external numbers allocated in the pool only in the NumbersDomains collection in binding to any child domain of any level, and not to use and copy them anywhere else in the routing and presentation rules.