Versions Compared

Old Version 8

changes.mady.by.user Luca Guerrieri

Saved on

compared with

New Version 9

changes.mady.by.user Luca Guerrieri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are some few but still important differences between the 

Xref
AnchorNameaccount creation form SNOM
 and the 
Xref
AnchorNameaccount 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
  • 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
Tip
titleEXAMPLE

You may have multiple rules for masking traffic. Combining together the Deny and the Permit option let you have a fine grain rule of access for any single user's account.

Please keep in mind that the access rules are processed from the first to the last, meaning that the Deny will be used first and then will be analysed analyzed the Permit one.

So:

  Deny: 0.0.0.0/0.0.0.0

  Permit: 216.27.242.66/255.255.255.255

 Deny every address except for the only one allowed.

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

Subtitle
Prefixfigure
SubtitleTextnew SIP account
AnchorNamenew sip account

...

Tip

An information line advice the operation just performed. 

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

Xref
AnchorNamenew sip account
).

Note

Using this way makes the account enabled by default.

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

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 

Xref
AnchorNamesip users table
click on the Create batch account action to open Create open Create batch account pageaccount page:

Subtitle
Prefixfigure
SubtitleTextcreate batch account
AnchorNamecreate batch account

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

Code Block
languagenone
titlebatch users csv
fullName,gsmNumber,email,securityModel,description Alessandro Bergamaschi,+391234567890,alessandro.bergamaschi@acme.com,end-to-site,Personal account Luigi Rossi,+3932456753,luigi.rossi@acme.com,end-to-site,Personal account Marco Bianchi,+39432242342,mbianchi@gmail.com,end-to-site,Personal account Mario Colombo,+394325346546,colombo.mario@acme.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

...