...
| Note |
|---|
It's still possible to perform an Automatic Activation or to send the installation URL on iPads or devices without phone features using the Provisioning Messages. |
Account Type
To configure a
account select "PGSM" by the drop down menu in "Account Type".To configure a SNOM account select "SNOM" by the drop down menu in "Account Type".
Obfuscation Mode
The Obfuscation mode is a simple but quite efficient trick to let the VoIP pass without being recognized by network equipment intended to block or censor VoIP traffic.
It's not known to be a perfect mask and it aims not to be one, still it works fine up to now and our suggestion is to keep it enabled as by default,
Obfuscation Key
The key used by the obfuscator can be an arbitrary one, still "9" is the default value. It doesn't matter which number you put in here as long as it is the very same one you set up on the client side.
| Warning |
|---|
If the Obfuscation Key value is not the same on both client's account and server's one, then the call won't be placed properly and it might end suddenly voiceless. |
| Xrefanchor |
|---|
| AnchorName | PSOM_keep_alive |
|---|
|
Keep-alive Enabled |
In order to receive secure phone calls,
client must set up an always-on connection to . Each client sends a "keep alive" request to the server it is connected to, in order to keep up the socket. This is necessary as the TCP socket has an idle timeout after which the socket is closed. Some aggressive network equipment can shorten the standard timeout, less than 10 minutes.In order to avoid the socket break caused by such aggressive network equipment, you can enable a server side "keep alive" request. In this way you can be sure that the socket and thus the connection would remain up and stable under every circumstances.
| Note |
|---|
The downside of this option is that there will be some more traffic on the socket (each passage of the request is 1.8 KiloByte, thus you can count almost 3.6 KB of traffic) |
| Warning |
|---|
| title | Battery life warning |
|---|
|
This option can afflict the battery life since more traffic means more radio transmission and on same devices the radio wouldn't have a proper timeout for going idle. |
The actual default value actual default value for the keep-alive interval is 60 alive interval is 60 seconds. You can configure the general keep-alive timeout in the NAT configuration formthe NAT configuration form. Please read PSAM 2.4 Asterisk advanced configurations to get informations about it.
| Warning |
|---|
|
All the clients prior to the 11.1 version cannot respond to the keep-alive request and thus if such option was enabled for their users, then those users won't ever be on-line and reachable. |
Virtual Phone Number Phone Number (secondary)
This field is optional and rarely used, still it can prove itself quite useful if you need the account to be reachable by two different phone numbers on the same device. The secondary virtual number can't substitute the primary one, meaning that this field alone won't be accepted as a valid phone number. You still need to configure the primary phone number if you intend to make use of the secondary one.
| Info |
|---|
Some example for using the secondary phone number are this scenarios: - User changes his own mobile phone number. Using secondary number it is possible to configure the NEW number as primary and the OLD number as secondary. The user will be able to receive secure calls dialed both on his NEW and OLD number.
- User install client on his business phone, but his colleagues could call him both using business and private phone numbers. Using secondary number it is possible to configure the BUSINESS number as primary and the PRIVATE number as secondary. The user will be able to receive secure calls dialed both on his BUSINESS and PRIVATE number. More often that you could expect, users initiate secure calls using the wrong number, complaining about "it does not work".
|
1.1.1.2.2 SNOM
In the Account List page (
| Xref |
|---|
| AnchorName | sip users table |
|---|
|
) you can see an empty list of accounts. To create a new Sip User you have to click on the New Account button the New Account button in the top of the page.| Subtitle |
|---|
| Prefix | figure |
|---|
| SubtitleText | Sip SNOM Account creation form |
|---|
| AnchorName | account creation form SNOM |
|---|
|
|
There are some few but still important differences between the
| Xref |
|---|
| AnchorName | account creation form SNOM |
|---|
|
and the | Xref |
|---|
| AnchorName | account creation form |
|---|
|
: security model, obfuscation Mode and Obfuscation Key fields are gone and instead you can read Deny and Permit. Due to the type of hardware underlying the SNOM account, we do assume that the hardware would be wired connected on a desktop. Also no obfuscation is possible because the device doesn't allow it. Instead the wired channel can provide us an easy to go access list, based on the LAN IP addresses. We can create both one White-List and one Black-List in order to bind the user's access to one specific device which can be identified by the LAN IP address. The different option shown are:Deny
Deny represent the blacklist based on the IP address and the net mask we want to deny when associated to the current user. You have to write this in the form: <ipaddress>/<network mask>
...