Step 12. A call from one domain to another
Case: user A is registered in Domain_A and has number 101; user B is registered in Domain_B and has number 202. User A dials on their phone a number of the form feature_code+domain_number+subscriber_number_in_domain, for example 912202. The call arrives at user B’s device, which displays user A’s name and a number of the same form, for example 913101, which B can use to call user A.
Route lookup is performed on DC at the request of B2BUA. The number plan is configured using a set of routing rules: entities of type route and vectorrule. A number is bound to a sipuser account through its phonenumber attribute, with uniqueness required within the domain. First, among routes (route), by masks (From number, To number, direction) and schedule, the highest-priority matching route is found. Then, among the rules (vectorrule) belonging to the found route, by masks (From number, To number, and direction) and schedule, the highest-priority matching rule is found. The action of the found rule is taken as the basis. The action can specify a call prohibition, an internal direction, transfer of responsibility to another domain with From and To modifiers, and a number of other directions.
Before transferring responsibility to another domain, B2BUA modifies the From and To numbers. Then those numbers are used to look up a route in the new domain obtained as a result of the previous lookup iteration.
Routing rules in different domains are configured independently by the administrators of those domains through CRUD operations on route and vectorrule entities. For a call from Domain_A to Domain_B to occur, administrators in both domains create matching routing rules. In Domain_A, a rule is created for transitioning to Domain_B, and in Domain_B, a rule is created for receiving such a transition from Domain_A. Routing rules in different domains can differ significantly. But if a single end-to-end number plan is adopted across all domains, routing rules can be grouped and their number sharply reduced. An example of such an end-to-end number plan is classic 10-digit telephone numbering with area, city, and subscriber codes. To avoid configuring rules in every domain for transitioning to all other domains, multi-stage transfer of responsibility between domains is used. For example, routing from each domain only to immediate child domains and to the parent domain with corresponding number transformation. Or creating a special domain to provide full routing and assigning an administrator responsible for numbering there.
The subscriber receiving the call sees the caller’s name according to how it is set in the name field of the sipuser account. The subscriber initiating the call sees the callee's name only after the callee picks up. Constants and substitution fields can be used as name field values. For example, with name "Sokolov_\{D}", the system substitutes the From:DisplayName value from the SIP INVITE request received from the subscriber device in place of {D}. Thus you can configure the display of "Sokolov_Work" and "Sokolov_Home".
The initiator’s phone number for display to the callee is calculated using representation rules (the representative entity). This may be necessary due to complex cross-domain number transformation rules. For example, to reach another domain, a rule is configured for numbers of the form feature_code+domain_number+subscriber_number_in_domain. Thus, within the domain it is enough to dial only the_subscriber_number, while from other domains this may be insufficient due to the routing rules configured there. So that an arbitrary call leaves the correct caller number in the phone’s memory and the ability to call back with the REDIAL button, the administrator can create a representation rule, and B2BUA applies it when creating the SIP dialog of side B.
Representations can be configured flexibly and individually using masks on the initiator’s and recipient’s numbers and domains.
However, unlike routing rules, the system does not support long chains of responsibility transfer between domains for building a representation. This is always the responsibility of the recipient domain, which can be replaced by the sender domain’s responsibility to reduce the number of representation rules when configuring a single number plan.
| when a call is transferred to another domain, only route lookup, representation, and registration procedures are involved. Call servicing and traffic transfer continue on the same SG, B2B, and MG servers as for calls within a domain. When a call is transferred to a domain served on another site, DC proxies the lookup request to that site, but the result is applied in B2BUA on the initiator’s site. Thus, within the entire system, under no circumstances do long chains of SIP connections arise. |
| Term | Definition |
|---|---|
|
! |
|
! |
|
! |
|
! |
|
! |
|
! |
|
! |
|
! |
-
Next step: Step 13. Failure of one of the servers serving a call
-
Previous step: Step 11. The first call