
How Call Addresses Are Processed
Page 75
CHAPTER 9
How Call Addresses Are Processed
The call addresses provided by the caller can be modified at different stages of the call processing within Diva
SIPcontrol. The reason for multiple manipulation is that it allows for modifying the address where it is needed,
which means that more complex environments can be configured with less effort, since data does not need to
be entered redundantly at different places. It also makes it easier to "team" SIP peers or PSTN interfaces with
different settings.
When using a dialplan, Diva SIPcontrol converts addresses automatically, without any intervention from the user.
This means that Diva SIPcontrol adds or removes a special prefix to a number with a known number type when
converting between a number and an address. The automatic conversions are done for calling numbers, called
numbers, and redirected numbers. See Common
Results on page 79 for a list of prefixes.
For complex conversions, you can configure an address map for Diva SIPcontrol to use when converting
addresses.
Possible Scenarios
• At a PSTN interface, a line access digit must be prepended in order to call to the public network, while another
PSTN interface is directly connected and does not need an access digit.
Solution: Add a regular expression to the outbound address map of the first interface.
• All calls to a number beginning with "9" shall be routed to one specific SIP peer while removing this digit.
Solution: Manipulate the called number in the route.This way the SIP peer can also receive calls to other
numbers (via other routes) without having to deal with different number formats.
• SIP peer "A" needs the dialed numbers to be formatted in E.164 format, while SIP peer "B”, which is in
load-balancing or fail-over partnership with "A", needs it in an extension-only format.
Solution: Define different number formats in the SIP peer settings.
• SIP peer "A" is located at a different location than SIP peer "B", e.g., London and Stuttgart. Therefore, both
need different location settings regarding country and area codes, etc.
Solution: Create different dialplans and assign each dialplan to one SIP peer.
How Addresses Are Manipulated
Diva SIPcontrol manipulates call addresses as follows:
Note: Each step is optional, depending on the configuration.
1. Saves the inbound call addresses as "A".
2. Applies the "address map inbound" of the endpoint assigned to the call setup request to "A", resulting in "B".
3. To check the first route: applies the number format settings of the route together with the dialplan of the
source endpoint to the call addresses "B", resulting in "C".
4. Checks the route against addresses "C". If the route does not match, Diva SIPcontrol discards the changes
and tries the next route with "B" again. For information about routes, see Routing
on page 41.
5. If the route matches, Diva SIPcontrol applies the route address map to the addresses "C", resulting in "D".
6. After selecting one of the destinations of the route, Diva SIPcontrol normalizes the addresses "D" using the
dialplan and number format of the destination endpoint, resulting in addresses "E".
7. Applies the outbound address map of the destination endpoint to "E", giving the effective call addresses "F"
sent to the destination.
8. If the call to the selected destination endpoint fails and there are other endpoints in a fail-over configuration,
Diva SIPcontrol starts with Step 6 again with the respective settings of the next endpoint.
Comentarios a estos manuales