Documentation V2
From berofix - professional SIP gateway
This Page describes the newest Feature in the 2.X branch. The documentation of the 1.X branch is in most cases still true for the 2.X branch, so only new Features will be described here.
Contents |
Analog Modules
The analog Modules appear as an own technology in berofix. They are comparable with the ISDN Modules in terms of Grouping all analog ports together.
Note: that the analog modules have their own Port number range, which means if you combine Analog and ISDN Interfaces on one berofix the ISDN Interfaces start to count from 1-X and the analog Interfaces start to count from 1-Y as well.
BF4FXO
This module is used to connect to a Public Switched Telephony Network provided as an FXS. It can also be used to connect berofix to an internal FXS Port of a traditional PBX or to a FXS Port on an analog Gateway.
BF2S02FXS
This module is a hybrid module with 2 BRI and 2 FXS Interfaces onboard. Please note, that the BRI Ports start counting from 1 as well as the FXS Ports.
BF4FXS
This module is a 4 Port FXS Module. It allows you to directly connect Analog Fons, Faxes or Modems to berofix.
Dialplan Changes
The beroFix Dialplan allows to match the dialed Number (Destination) and the Callerid (Source) against Patterns. It also allows to modify the Destination and Callerid, for example to put a prefix (like 0) before a Number. Each Dialplan Rule can carry additional Configuration options that are only valid for this rule. With these tools it is possible to modify the call handling behavior of berofix per Destination Number or per CallerID. One usage example is to enable or disable CLIR per Destination prefix.
Destination
As you can see it is quite simple to say which field in SIP or PSTN is the Destination (To Header and DAD), so there is a simple 1:1 Mapping between the SIP Header "To:" and the PSTN Destination Number DAD. To make it possible to match against certain Destination all incoming calls are first processed by the Dialplan.
If the call comes from SIP, the To: Header is matched against all Dialplan Destination fields. If one line matches the configured CallerID is checked against the Dialplan Source field (see below). If one rule matches, then the PSTN DAD (Destination Address) is filled with NewDestination. The Destination matches with regular expressions and the NewDestination contains the results.
Source
If we take a closer look at the callerid we find out that both SIP and PSTN have multiple Fields to carry callerid Information. In general there are at least 2 Fields (Number and Name). Since the beroFix Dialplan can only match against one Source it is now possible to define which of the SIP Headers or which of the PSTN Callerid Fields is used for matching and mangling. This setting is Called "Dialplan Source" and can be found both in the SIP Account Settings or in the PSTN Group Settings.
Source (from SIP)
If the call comes from sip there are for example the SIP Headers: from_display, from_user, p-asserted-identy, p-preferred-identy which can carry the callerid.
Source (from PSTN)
If the call comes from isdn the callerid is in most cases carried in the oad (originator address) field.
