When describing outgoing routes, it is allowed to use the same phone number template.

If several routes are used with the same template, the PBX will try to make a call on each of the routes until the call is accepted.

This functionality is not always necessary and there may be a need to disable it.

At the moment, this can only be done through the customization of the PBX.

1. Go to the provider's settings and copy its ID in the browser's address bar:

1. Go to the section "System file customization"

1. Go to the editing section of the extensions.conf file.

1. Add the following context to the end of the file:

[SIP-1687941868-outgoing-after-dial-custom]
exten => _X!,1,Hangup()
	same => n,return

Save the changes. Now all calls via routes associated with the provider will occur without taking into account the backup provider. It will work out only the first of the outgoing routes.

1. Go to the Routing → Outbound routes section.

1. Adding a new rule

1. Fill in the parameters as in the screenshot below:

1. You direct calls to emergency numbers through an arbitrary provider. The provider must support dialing emergency numbers. The priority of this rule should be the highest, i.e. it should be described first in the list of created outgoing routes.

1. Go to System → System file customization

1. Open the extensions.conf configuration file for editing.

1. Set the "Add to end of file" mode. In the black window, add the following code snippet:

[internal](+)
exten => _1XX,1,Goto(outgoing,${EXTEN},1)	

In the above code snippet, we described the rules for all three-digit numbers starting with 1. If you need to specify specific emergency numbers, then instead of the above code, you need to insert the following lines:

[internal](+)
exten => 112,1,Goto(outgoing,${EXTEN},1)
exten => 101,1,Goto(outgoing,${EXTEN},1)
exten => 102,1,Goto(outgoing,${EXTEN},1)
exten => 103,1,Goto(outgoing,${EXTEN},1)

1. Go to Routing → Outbound Routing

1. Create a new outbound routing rule:

1. Fill in the parameters according to the template below:

1. Go to the System file customization section

1. Open modules.conf for editing

1. Add the following code to the end of the file:

load => func_global.so

1. Open the extensions.conf file for editing

1. Add the following code to the end of the file:

[all-outgoing-custom]
exten => _X!,1,NoOp()
    same => n,Set(NEED_RETURN=0)
    ; We describe the list of providers
    same => n,Set(PUSH(rrItem)=SIP-1601534775)
    same => n,Set(PUSH(rrItem)=SIP-1611151795)    
    same => n,Set(PUSH(rrItem)=SIP-1681205343)
    ; Maximum number of simultaneous calls over the line
    same => n,Set(busyLevel=50)
    
    ; Checking if there is a provider in the list.
    same => n,ExecIf($[ "${FIELDNUM(rrItem,\,,${PROVIDER_ID})}" == "0" ]?return)
    ; If the ID of the priority provider is determined, then immediately proceed to verification.
    same => n,GotoIf($[ "${rrElement}x" != "x" ]?check)
    ; Initializing an array
    same => n,Set(rrArray=${EMPTY})
    same => n,Set(i=${SHIFT(rrItem)})
    same => n,While(1)
    same => n,ExecIf($[ "${i}x" == "x" ]?ExitWhile())
    same => n,ExecIf($[ "${rrArray}x" != "x" ]?Set(rrArray=${rrArray},))
    same => n,ExecIf($[ "${GLOBAL(${i})}x" == "x" ]?Set(GLOBAL(${i})=0))
    same => n,Set(rrArray=${rrArray}${i}:${GLOBAL(${i})})
    same => n,Set(i=${SHIFT(rrItem)})
    same => n,EndWhile
    ; Finding an item with a lower weight
    same => n,Set(rrArray=${SORT(${rrArray})})
    same => n,Set(rrElement=${SHIFT(rrArray)})
    same => n,While(1)
    same => n,ExecIf($[ $[${GROUP_COUNT(${rrElement})} < ${busyLevel}] ]?ExitWhile())
    same => n,ExecIf($[ "${rrElement}x" == "x" ]?ExitWhile())
    same => n,NoOp( ${rrElement} - is busy)
    same => n,Set(rrElement=${SHIFT(rrArray)})
    same => n,EndWhile
    same => n,NoOp(--- ${rrElement} ---)
    
    ; Checking whether the provider matches
    same => n(check),ExecIf($[ "${PROVIDER_ID}x" != "${rrElement}x" ]?Set(NEED_RETURN=1))
    same => n,ExecIf($[ "${PROVIDER_ID}x" != "${rrElement}x" ]?return)
    ; Increasing the counter
    same => n,Set(GLOBAL(${rrElement})=$[${GLOBAL(${rrElement})} + 1])
    ; The counter of active calls through the provider
    same => n,Set(GROUP()=${rrElement})
    same => n,return

Let's say there is a certain number +371 (2) 637‑23‑33, by calling to which and dialing an extension you can get to a specific employee. This can be extremely convenient, especially if the extension number is longer than 3 characters. Next, we describe an example of the implementation of the task.

1. To solve the problem, additional contexts should be described through the Customization of System Files menu.

1. We will edit the extensions.conf file.

1. Add the following text to the end of the file:

[z-outgoing]
exten => _X!,1,Ringing()
  same => n,Gosub(${ISTRANSFER}dial,${EXTEN},1)
  same => n,Dial(PJSIP/${EXTEN}@${ZPROVIDERID},600,${DOPTIONS}TKU(z-dial-answer)b(dial_create_chan,s,1))
  same => n,ExecIf($["${ISTRANSFER}x" != "x"]?Gosub(${ISTRANSFER}dial_hangup,${EXTEN},1))
  same => n,Set(pt1c_UNIQUEID=${EMPTY_VALUE})
  same => n,ExecIf($["${BLINDTRANSFER}x" != "x"]?AGI(check_redirect.php,${BLINDTRANSFER}))
  same => n,Hangup()

[z-dial-answer]
exten => s,1,NoOp(Answered send DTMF...)
  same => n,Gosub(dial_answer,${EXTEN},1)
  same => n,SendDTMF(${ZDTMF})
  same => n,return

1. Next, it is necessary to describe the Applications of dialplans

1. Select "Type of code" - "Asterisk Dialplan"

1. Let's say you need to "dial" the number 3542331, set this value to "Number to call the application"

1. Go to the "Programme Code" tab and insert the template:

1,Set(_ZDTMF=${EXTEN})
n,Set(_ZDST=37126372333)
n,Set(_ZPROVIDERID=SIP-1601534775)
n,Goto(z-outgoing,${ZDST},1)

• If you specify the 9XXXX template in the "Application call number" field, it will be possible to "dial" any five-digit numbers starting with the digit "9"

• In the application, assign the variable "ZDST" the number to which the call should be made In the "ZDTMF" variable, specify the number for the additional set

• In the "ZPROVIDERID" variable, specify the ID of the provider through which the outgoing call should be made. ID can be peeped in the browser address bar when editing the provider

The task is to remove the area codes 6017, 6095, 6096, or 6099 and retain the 7-digit number. For example, numbers 60172293042 and 60956382584 should be transformed to 2293042 and 6382584, respectively.

1. Navigate to the "Routing" → "Outbound Routes" section.

   Click "Add New Rule."
2. Create the pattern as shown in the image:

1. Click "Save."

The task is to add the prefix "1" to a number. For example, numbers 4952293042 and 4996382584 should be transformed into 14952293042 and 14996382584, respectively.

1. Navigate to the "Routing" → "Outbound Routes" section.

   Click "Add New Rule."
2. Create the pattern as shown in the image:

1. Click "Save."

It is necessary to replace the number prefixes +345 with 347. For example, the number +3454952293042 should be converted to the number 3474952293042.

1. Go to "Routing" → "Outbound Routing"

Click "Add a new rule"

1. Create a template as shown in the image:

Click "Save settings"

Problem Statement

In MikoPBX (Telephony → Employees), the following employee accounts are configured:

In MikoPBX, there are two providers configured (Routing → Telephony Providers):

The requirement is that:

1. The phone connected to account 201 should only make calls through the first provider PT.

2. The phone connected to account 202 should only make calls through the second provider Zadarma(Novofon).

Outbound calls to the external world (to a city) through both providers are implemented using the same outgoing rule: it's a ten-digit number starting with 7. This task can be schematically represented as follows:

Solution

Routing calls through a specific provider can be achieved using outbound dial plan prefixes.

• Calls will always go through the first provider if you add 1 before the outgoing number. Therefore, if the subscriber with 201 wants to dial outgoing numbers with the 1 prefix, the calls will go through the first provider.

• Calls will always go through the second provider if you add 2 before the outgoing number. Therefore, if the subscriber with 202 wants to dial outgoing numbers with the 2 prefix, the calls will go through the second provider.

You can schematically represent this as follows:

You can implement this task in two ways in MikoPBX:

1. Subscribers 201 and 202 will always add specific prefixes before dialing on their phones. For example, if they want to call the number 74952293042, they will add the prefix 1 or 2 before this number, such as 174952293042 or 274952293042.

2. Subscribers 201 and 202 do not dial special prefixes; the PBX itself performs this action for them.

First Method

The first method of implementing our task assumes that subscribers 201 and 202 will independently dial the corresponding prefixes on their phones. Subscriber 201 will always add 1 before the number, and subscriber 202 will add 2.

1. For the first provider, create an outbound rule. Go to Routing → Outbound Routes. Add a new rule.

1. Fill in the parameters as shown in the screenshot below:

3. For the second Zadarma provider, we create an outgoing rule. Go to the Routing → Outgoing routes section. Adding a new rule as in the screenshot below:

Second Method

The second method of implementing our task assumes that subscribers 201 and 202 do not dial specific prefixes on their phones; the PBX does this for them.

2. In the Routing → Telephony Providers section, add a third provider account.

1. Fill in the parameters as shown in the screenshots below:

1. Save the account and copy the ID of this provider in the address bar.

1. Add an outgoing rule for the created provider. By default, we will direct all calls through this provider, so be careful when creating an outgoing template. Calls through our providers can be made to numbers starting with 7, so our template takes the form:

1. Please note that the priority of the outgoing rule for the Router provider should be lower than all!

1. Go to System -> System file customization section

1. Open the extensions.conf configuration file for editing.

1. Select the "Add to end of file" mode. In the editing window, insert the following lines:

In the code snippet above, you need to create the correct context name. The format of the created context:

PROVIDER-ID - the value you saved in the third step described in this method. In our example, it's SIP-1690973516.

Save the changes and return to the list of configuration files.

This way, for the 201 and 202 accounts, we have set prefixes. All outgoing calls will now go through the required provider.

Default Route

In some cases, when defining incoming routes, you may need to redirect a call not to an internal number but to an employee's mobile number. In this case, you need to describe the "Default Prefix," otherwise, there may be problems with handling such calls.

When routing by DID number:

For each provider, you should also describe the context:

With these configurations, you have completed the setup.

It is necessary to replace the number prefixes 345, 347 with +345. Example, the numbers 3454952293042 and 3474952293042 should be converted to +3454952293042.

1. Go to "Routing" → "Outbound Routing"

Click "Add a new rule"

1. Create a template as shown in the image:

Click "Save settings"

1. Go to the “System” section -> “System file customization”

1. Select the file “/etc/asterisk/extensions.conf” to edit.

1. Select the “Add to end of file” mode.

1. Add the code to the second field:

Save settings.

Some softphones / CTI solutions transmit a phone number with special characters when dialing, for example +371(2) 229-3042

Such a call is very likely to fail, it will be completed by mistake.

1. To solve the problem of "filtering" characters, an additional context should be described through the menu

1. We will edit the extensions.conf file.

1. Add the following context to the end of the file:

Some providers require sending an additional SIP header when initiating an outgoing call. In this article we will describe a way to install it.

1. To solve the problem, additional contexts should be described through the System File Customization menu.

1. We will edit the extensions.conf file.

1. Add the following text to the end of the file:

When using the "User Groups" module:

• Let's say a conference room with the number "354233" is configured on the PBX.

• When calling an employee(s) to a conference, it is always necessary to connect an external subscriber.

• When disconnecting employees from the conference, the external subscriber must be disconnected

This may be required to organize communication with an external (relative to MIKOPBX) conference. It will allow saving on outgoing calls (only one line will be occupied).

1. In the "Telephony" section, go to "Conference" and create a new conference.

1. We will indicate the name of the room "Z-CONF-354233"

1. We will indicate the internal number "354233"

1. Name "Z-Worker-CONF"

1. The number to call "2200103" (can be arbitrary)

1. Specify the code type "PHP-AGI script"

1. Programme code:

1. Adding the task to the end of the file:

In this example, "DIALPLAN-APP-EC12CFAE6783FE82FD34F16E40C7386B" is the ID of the previously created application. The ID can be peeped in the browser address bar when editing the application.

1. Add the following code to the end of the file: