Inbound enables you to define what should happen to an inbound call, in other words when you recieve calls. Enter the inbound number as it is presented to the Axeos PBX. This varies between carriers so please consult your provider if you do not know what format they use.
This can be set up with one or more actions, see for details about actions in list of types. Each action can be executed only if a certain condition applies or always. Examples are of conditions are: time of day, number of the person calling you or if a switch is on or off etcetera. Please note that when there is no human answering the call and you want to have an active audio channel (music on hold, DTMF etc.) then you must use the answer action to instruct the PBX to set up the RTP (=audio) as well.
When a action tells the PBX to execute rules defined in the menu extensions then it will not return to the inbound rules.
Example: In inbound you have a rule “local extension”. In the menu extensions this dials an IP phone. If you have set a timeout of 30 seconds then it will not continue with the inbound rules you have further defined. It will simply stop in extensions or continue with other rules you have listed under the extension.
The PBX enables you to nest groups of rules. Nesting means you call a routine and when the routine is done then it will continue with the rest of the rules you have defined in inbound. Do keep in mind that termination actions will stop further processing regardless. For example an action hangup will disconnect the call and will never continue with the next set of rules, the same applies for voicemail as this is an action that picks up the call.
To create a new inbound number, click the ‘Add’ button and complete the following fields:
Inbound number: the full phone number as presented by your carrier/SIP provider
Description: enter a description
optional Return trunk: Default value not set, only set when needed. Select the trunk that will be used if the action places an external call and you want to force a specific trunk other then the default trunk. Trunks configured as an Outbound trunk will be available as option.
optional Permissions: Default value not set, only set when needed. select the permission profile to be applied to the number.
Allow unknown SIP clients: Default value not checked, do not check unless you know what you are doing! This option instruct the PBX to ignore any authentication on inbound traffic with SIP. SIP clients, for example an other PBX, to be allowed explicitly can be configured as peer with menu Trunks. Allowing any SIP client without authentication or without firewall rules is a security risk which can lead to phone costs.
To configure a new action click on ‘Add’. You can use drag&drop to change the order of the rules.
Please note the fields available change depending the options you choose. Check for details about actions in this list of types.
Using wildcards in the inbound dialplan
You can use regular expressions to allow the use of number patterns as DID numbers, in order to match more than one number. Basically you can create a wildcard. Would you like to know more about this?
If you are using more than one outbound trunk and all these have a prefix (you can have 1 unprefixed outbound trunk) then you will want to specify the return trunk on your DID’s because the PBX needs to know the number to callback in various scenarios. If you have 2 trunks with prefixes and your DID does not have a “return trunk” set the PBX takes the lowest prefix so you would be able to dial back to someone from your phone.
I have 2 trunks:
– SIP_something with prefix 0
– SIP_alternative with prefix 1
– If I don’t have a “return trunk” set in Inbound for +31204160640 then I will see “00031…” (triple 0) displayed on my phone.
– If I will set “SIP_alternative” as return trunk in Inbound for +31204160640 then I will see “131…” displayed on my phone.
– If I will remove “0” prefix from SIP_0 I will see 0031… callerid on my phone.