Page History

1.1.1 Accounts Management

Once you have almost one group you can fulfill it with SIP Accounts. In the Group List (PSOM 1.0 Groups) click on the Accounts icon on the right of each group's row. 

Subtitle
Prefix figure SubtitleText The Sip Users Table AnchorName sip users table

As a general list of the accounts which are present in each group, the one shown in 

The first column is reserved for the Details, which is a link to monitor each account's activities, current status and configuration. Most of the following fields are quite self-explanatory. The last column is for quick links about installation and configuration of customer's clients.

Send Installation Sms is good for sending via Text message a link meant to be used to download and thus install the PrivateGSM application. More about the Automatic Activation and about the Provisioning can be read in paragraph 1.1.4.

Send Activation Sms serves to plant the configuration file into the selected customer's client using Text Message as a mean of transport. The Text Message would include an URL to be used for downloading the configuration file itself.

You have three way for create new users:

1. the plain way: manual configuration 
2. the wizard way: automatic activation
3. the batch way

Each one is going to be detailed in the next paragraphs.

1.1.1.1 Create a new account, the plain way (manual configuration)

The "plain way" is a completely manual creation of the account. In this way you control any feature of the account, but you also need to configure the user's client manually. This way is the opposite of the automatic activation.

In the Account List page (

You can create both PGSM (PrivateGSM) or SNOM accounts and they do differ a while.

1.1.1.1.1 PGSM

The Create Account page will show a form with many fields. Mandatory ones are:

• Username

• Password/Repeat Password

• Virtual Phone Number

• Account Type

• Security Model

• Obfuscation Mode

• Obfuscation Key

• Keep-alive Enabled

Username/Password

Username field is automatically generated as a random numeric value and you are not required to change it. Type in a password and repeat it in the proper fields.

Virtual Phone Number

Set a Virtual Phone number as a numeric value of your choice. Please consider that the Virtual Phone Number is the number to be dialed to call the Account (and also the number shown as the caller, when the Account dials a call). We suggest a three character number such as "111" or "123" for SNOM devices and actual mobile phone number for PrivateGSM accounts.

Automatic Activation is not meant for SNOM devices or iPad. You need a PrivateGSM client in order to process the URL and the configuration itself. Plus without a phone that can receive an SMS, it wouldn't be delivered at all.

Account Type

• To configure a PrivateGSM 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".

Security Models

• To configure a PrivateGSM Enterprise account the security model must be "SDES".

• To configure a PrivateGSM Professional account the security model must be "ZRTP".

• To configure a Snom account the security model must be "SDES".

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.

In order to receive secure phone calls, PrivateGSM client must set up an always-on connection to PrivateServer. 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. This behavior is particularly critical with IOS devices. 

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.

The actual default value for the keep-alive interval is 60 seconds. You can configure the general keep-alive timeout in the NAT configuration form. Please read PSAM 2.4 Asterisk advanced configurations to get informations about it.

Virtual 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.

1.1.1.1.2 SNOM

In the Account List page (

There are some few but still important differences between the 

• Deny
• Permit 

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>

Examples:

• 192.168.0.38/255.255.255.255 : Denies traffic from this IP address
• 0.0.0.0/0.0.0.0 : Denies every address

Permit

Permit is the exact opposite of the Deny option. It represent the whitelist based on the IP address and the net mask we want to have access. You have to write this in the form: <ipaddress>/<network mask>

Example:

• 192.168.0.38/255.255.255.0 : Allows traffic from this Network

1.1.1.1.3 Actually create the Account

After you filled in the form (either the PGSM or the SNOM one), please click on the Create icon at the page's bottom. 

You'll get back the Account List page and the table shows now your new user (

To use the automatic activation even in the plain way go reading the 1.1.4 Automatic Activation.

1.1.1.2 Create a new account, the wizard way (automatic activation)

The "wizard way" is the new method for creating accounts. It's made for easing the load on the service manager's shoulder, letting him/her focusing on the service configuration without having to bother about the installation and configuration of the client.

In the Account List page (

You'll see the "Edit Account page" with a precompiled, non-editable username  as in 

Please set a Virtual Phone Number and choose a Provisioning Profile.

If not differently configured, the default values for the Obfuscation are fine. The other fields are optional.

Compile all necessary fields of the new account, select a Provisioning Profile and click on "Create". Now jump to paragraph 1.0.3.6 for activate the user.

1.1.1.3 Create a new account, the batch way

The "batch way" is an account creation mode designed specifically for large number of users to be created quickly.

Starting from Account List page 

Prepare a .csv file with some account. The file must be formatted as the example below, keeping header names in the first row

fullName,gsmNumber,email,securityModel,description Alessandro Bergamaschi,+391234567890,alessandro.bergamaschi@privatewave.com,end-to-site,Personal account Luigi Rossi,+3932456753,luigi.rossi@privatewave.com,end-to-site,Personal account Marco Bianchi,+39432242342,mbianchi@gmail.com,end-to-site,Personal account Mario Colombo,+394325346546,colombo.mario@privatewave.com,end-to-site,Personal account

Select the default provisioning profile and a group for the newly account created. Upload the file and click create: you'll be leaded to the Group list page.

Once you've done you can choose whether to manually activate the user or to lean on the automatic activation.

Anchor
account_details account_details

1.1.1.4 Account's details

The figure 

Three tabs are shown in the Account's details window:

• State
• History
• Configuration

State is the default view you get and shows if the Account is connected and his licence status.

History shows any relevant information about the account.

As you can see in 

1. Timeline lists all the informations about the creation and activation of the account as well as date and time of text messages sent and received.
2. Last session events is an excerpt of the SIP Sessions targeted to the account. 
3. Latest calls is an excerpt of the CDR showing all the recent calls placed by the account. It's possible to show all the received calls as well, by clicking on the All received calls at the list's bottom.

Configuration is what's left of the account's details form as it was intended in previous versions of PrivateServer.

From this summary of the account's configurations you can manage the account itself. It's possible to Send Installation Sms or to Send Activation Sms, action which we explore deeper in paragraph 1.1.4, as well as to Disable account. The last action inhibits the user to call or to be called and a specific Audio Message is issued by the PrivateServer to inform the user.

It's also possible to Edit the account's settings (more about this in the paragraph 1.1.2), Refresh account's data (which is proved to be quite useful to monitor the Text Messages status, like the Installation clicked) or simply Delete (paragraph 1.1.3) the account itself. In the following paragraphs you'll read more about account's management.

Anchor
account_update account_update

1.1.2 Update the Account

To change the SIP Account values you need to reach the form showed in

In the form that would be presented to you (shown in

As shown in 

Anchor
account_delete account_delete

1.1.3 Delete the Account

In order to delete the account you have to access at the account details as described in paragraph 1.1.1.4. You have to get the Configuration details as in 

Press it and confirm the deletion in the next warning pop up window (

Once you're done, by pressing the "Ok" button, the Account List page will be shown up without the Account and with a warning: see 

Anchor
automatic_activation automatic_activation

1.1.4 Automatic Activation of the Account

 After you created your new account(s) you have to configure the customer's client application PrivateGSM. In the wizard way it's MANDATORY to use the automatic activation in order to enable the account. In the plain way it's optional, though useful.

The Automatic Activation is quite useful in two occasions:

1. after you just finished creating an user
2. whenever you need a quick account's reconfiguration without involving too much the user

To be able to send text messages with the Automatic Activation you first need to get the Account list (

Confirm as in the above picture and the PrivateServer advices the operation has been completed:

Getting back to the account list you can read the exact status and the time of its change:

So what's happened is that the status has changed from "Created" to "Installation SMS sent" and the "Last Status date" has been updated to the time the SMS has been sent to the customer.

After the customer has downloaded and installed the application, the "Last status" changes to "Installed" but the "Enabled" is still "False". "Last Status date" is updated as well.

Next step is to send the "Activation SMS" in order to enable the user to place and receive calls.

Just click on the related link at the end of the customer's row in the Account list table. As for the "Installation SMS" you are requested to confirm the action (refer to 

Note the change in the "Last Status" and in the "Last Status date": the former is now "Activation SMS sent", the latter is updated to the new time the action was performed. 

You can know for sure that the user has configured his/her PrivateGSM application because after the action has been performed the account's "Last Status" becomes "Activated" and the "Last Status date" is updated as in the former cases.

Now the "Enabled" fields is changed to "true" meaning that the customer is ready to go.

If the customer actually goes on line with the PrivateGSM application, than the "Last Status" becomes "Connected".

Anchor
account_disable account_disable

1.1.5 Disabling/Enabling an Account

If you need to temporary block any account in both directions so that he cannot place or receive calls, then you can just disable him. When a disabled account tries to perform secure voice actions a proper audio message is played warning about the account' status.

Any account is enabled by default.

In order to disable an account you need first to reach the form shown in 

Just press it and it will change as in 

1.1.6 Searching an Account

You can search search a group's accounts with the search box on the menu bar of the Account list page.

Subtitle
Prefix figure SubtitleText The searching interface AnchorName searching account

The search covers the following fields of accounts:

• Owner
• Username
• Caller id
• E-mail
• Description

The search string is interpreted as a list of words, separated by spaces. All words in the search string must match. Words must match exactly, unless they contain wildcards:

• *: matches zero or more characters
• ?: matches one character, any character

Examples:

• Marco matches "Marco Rossi" and "Marco Bianchi", but not "Giulio Marconi"
• Marco Rossi matches "Marco Rossi", but neither "Marco Bianchi" nor "Giulio Marconi"
• Marco* matches "Marco Rossi", "Marco Bianchi" and "Giulio Marconi"
• Marco?? matches "Giulio Marconi", but neither "Marco Rossi" nor "Marco Bianchi"

Anchor
licencing licencing

 1.1.7 Licensing

The communication model of the licence can change quite a bit based on how user activated his account. Manual account creation leads the licence client on PrivateGSM to communicate directly with PrivateWave's licence server. Automatic Activated clients would communicated with their own PrivateServer, which plays the role of a proxy to PrivateWave's licence server. In the latter case, the current licence is cached on PrivateServer and visible in account details.

Since the licence validation is an important component of the secure call, it's important that this difference in the behaviour of the client is fully understood by the Operator Manager. For instance if the Services weren't configured to let the HTTPS/SmartPhone Web Service be reachable on the public NIC, then the licence clients of any Automatically Activated PrivateGSMs would never be able to validate their own licences and thus the client would be stuck until its licence status would be cleared somehow.