VOIspeed Gateway configuration
Gateways represent the entities through which the PBX communicates with the outside world, in other words they represent the interface with the company’s telephone lines. A gateway can be a hardware device physically connected to the company’s telephone lines (ISDN, Analog, GSM), or it can be a VoIP operator. In the VOIspeed Cloud architecture, the hardware gateways (ISDN, GSM, Analog) authenticate themselves on the server as if they were a user, therefore the PBX administration will have to create the authentication credentials
On the gateways representing VoIP operators, however, it is the PBX that authenticates itself to the operator as usual.
|Company||It is the current company on which you are working (cannot be changed)|
|Type||Indicates the type of physical interface to which the gateway connects. Precisely:
VOIP: VoIP operators
ISDN: indicates an ISDN gateway on basic access or primary access (eg Mediatrix 440X)
GSM: indicates a GSM gateway (e.g. V-6021, 2N)
Analog Line: indicates a gateway for FXO analog lines (eg Mediatrix C730, Patton 4112)
|Enabled||Enable or disable gateway from PBX routes (VoIP account registration will be disabled)|
|Name||Gateway name (required)|
|Linee||Number of total lines that the gateway can manage. Indicate the exact number of channels or lines available on the gateway. Examples:
ISDN: 2 lines for each basic BRI access (ISDN socket, or ISDN port of a router if provided by another operator)
ISDN: 30 lines for whole primary accesses, 15 for fractional primary accesses
GSM: 1 line for each SIM inserted in the gateway
Analogue Line: 1 line
VoIP: varies according to the case. Enter the number of lines available calculated on the basis of the available Upload bandwidth (each conversation with the G.729 compressed codec occupies approximately 20kbps, each conversation in uncompressed G.711a format occupies approximately 80kbps). If the operator places a constraint on the number of lines, set the same number, as long as it is compatible with your ADSL connection.
|Allows you to specify the exit number (CLID or caller ID) when the gateway uses the telephone line. This allows you to appear outside with the desired number, as long as the gateway being queried supports this function. The available options are:
|Domain||Indicates the domain of the VoIP operator (eg. Voip.eutelia.it)|
||In the UCloud architecture, the hardware gateways (ISDN, GSM, Analog) all require authentication such as if they were a user. For this reason, the account (username and password) must be created here.
Warning, do not use characters in this field. Set the telephone number of the telephone line as the User ID. If you have multiple gateawy with the same number, use a different number (for example the main number with one more digit). This new number must obviously be entered as a company number
|RTP flow tracker||Valido solo per Operatori VoIP: di default è sempre disattivato e va attivato solamente se l’operatore VoIP supporta le comunicazioni peer to peer tra terminali, dove il PBX non fa da bypass sui flussi RTP|
|Indicates whether the gateway requires authentication or not. It is normally used for VoIP operators. Furthermore, in the UCloud architecture, all gateways (eg GSM, FXO, ISDN) require registration. Activating this option you will be asked: realm, username, password and authentication period (register timeout).
Tip: set the telephone number of the telephone line as username.
|Realm||Very important for VoIP operators: it must coincide with the Realm communicated by the operator. In case of failure to register, check the Realm column in the gateway monitoring: that represents the true expected value, taken from the PBX from the operator’s response SIP packets. Sometimes the commercial offices of the operators account data incorrect (among these the Realm is the most susceptible to errors).|
Notes on authentication parameters: due to the irreversibility of the MD5 encryption operations used in the SIP authentication process, if you decide to change any of the parameters of the triplet of this section (username, realm and password), you will need to re-enter them all how many.
In this section, you can manage the addition / removal of prefixes to / from numbers after being taken over by the gateway. The Prefix Rules field allows you to enter rules for adding or removing the desired prefixes. It is possible to insert more than one rule (one per line) and each of them must have the following syntax:
P1, P2, P3 where P1 = prefix of the called number, P2 = prefix to be removed, P3 = prefix to be added. The comma is considered as a separator, so if there is no prefix to add or remove, you don’t need to write anything, but leave the comma as a separator.
This function is very useful when you want to bind the gateway by prefixing the number dialed: after the call is handled by the gateway, the prefix must be removed otherwise the call would be forwarded to the gateway for a non-existent number.
Example: to exit with the desired operator, the user must prefix the prefix 51 to the number to call (eg: 510612345678). In the Advanced section of the Gateway, enter the rule 51.51, (leaving the last field with the last comma that identifies the last field as empty). This means that calls for numbers starting with 51 will be transformed into calls for numbers without the same prefix.
It is also possible to have the gateway add a prefix to the numbers entered by users because, for example, it refers to a SIP device (eg GSM / UMTS multi SIM gateway) which routes calls to its resources based on a prefix.
Example: the user must exit the SIM 1 of a GSM gateway in a transparent manner when calling mobile phones; the GSM gateway uses the prefix 5 to bind SIM1 (which it then removes internally). In the advanced section of the gateway it will be necessary to enter the following string: 3,, 5 which indicates that to the mobile numbers (prefix 3 …), VOIspeed will add the prefix 5 and send it to the GSM gateway as 53 … The GSM gateway must therefore take care of the removal of the prefix 5 once it has engaged the desired SIM.
NOTE: for convenience numbers to be sent to the gateway, a routing rule must also be created for that prefix, otherwise the PBX would not be able to route the call to the gateway. In fact, these rules apply only AFTER the call has been routed to the gateway itself.