Browse Category

Technical Hints

2N Automation: Wake on LAN

We recently set up our 2N IP Vario to wake up our computers when we scan our key fobs to enter the office. This means that our employee’s computers are switched on and ready to go before they even arrive at their desk.

We did this by writing a web app which uses the ‘Wake on LAN’ protocol, this was then added to 2N’s automation feature. ‘Wake On LAN’ is an existing protocol supported by many desktop computers.

Once a user scans their key fob on the IP Vario it then sends a HTTP request to our web app that includes the id of the key fob. The app then finds which user has scanned into the building by looking up the id of the key fob which was used and finds the associated user. With the username, the app then looks up the mac address for that user’s computer which calls Wake On LAN to broadcast a magic packet across the network. If the PC has power but is not turned on the computer will then boot.

Here is an example of the config we set up in our IP Vario’s automation:

<automation><row><name>Event.CardEntered</name><value>Card=valid;</value></row><row><name>Action.SendHttpRequest</name><value>Event=1; Uri=$(1.Card)</value></row></automation>

Full factory reset on Vega 3050G

The new Vega 3050G gateway uses a different method for performing a full factory reset than other gateways.  This was called a “config clear” on other gateways.


Before doing this make sure you have backed up the license key from the Vega as you will need to manually restore it afterwards.  Without this, the Vega will only process a couple of calls at a time.

Instructions on how to get the license key can be found here:

If you cannot do this for some reason (such as not knowing the admin password) then you will need to raise a support request with us and tell us the serial number of the unit.  But be aware, we have to then request the key from Sangoma and this can take a business day.  If your gateway is  being used, wait for the license key before doing the reset.


Connect a serial console cable to the Vega, instructions can be found in the link above.

With the console cable still connected, remove the power cable from the Vega.  Get ready to start pressing the enter key on your keyboard, put the power cable back in and immediately start pressing the enter key on your keyboard.

You should see the uboot prompt on the screen:


At this point, enter these commands one by one (pressing enter each each one) to action the reset:

sf probe

sf erase 0x70000 0x90000


The Vega will now reboot with all factory settings including network and password settings.

Note: be very careful to type those commands in correctly, the 2nd one is erasing a section of the flash memory, getting the numbers wrong could damage your Vega gateway.

Lastly, restore your license key using the instructions found in the link above.



Polycom Recovery (Resolve a Formatted File System)

If you’ve ever pressed the wrong button trying to perform a factory reset on a Polycom phone and accidentally pressed “Format File System” instead. You’ll most likely know it can be time consuming to recover the unit if you don’t have a provisioning server set up for this.

Well, you’re in luck! (Hopefully)

You should be able to use our server to download the application back on to the unit. Below is a list of all the units that can be recovered via our server.

Available for Polycom Models:

2345-12365-001.sip.ld = SoundPoint IP 331
2345-12450-001.sip.ld = SoundPoint IP 450
2345-12560-001.sip.ld = SoundPoint IP 560
3111-19000-001.sip.ld = SoundPoint IP 560
2345-12360-001.sip.ld = SoundPoint IP 321
2345-12375-001.sip.ld = SoundPoint IP 335
2345-12500-001.sip.ld = SoundPoint IP 550
2345-12600-001.sip.ld = SoundPoint IP 650
3111-30900-001.sip.ld = SoundStation IP 5000
3111-40250-001.sip.ld = VVX 101
3111-44600-001.sip.ld = VVX 600
3111-46161-001.sip.ld = VVX 310
3111-48350-001.sip.ld = VVX 311
3111-48500-001.sip.ld = VVX 501
3111-40450-001.sip.ld = VVX 201
3111-46135-002.sip.ld = VVX 300
3111-46162-001.sip.ld = VVX 410
3111-48400-001.sip.ld = VVX 401
3111-48600-001.sip.ld = VVX 601
3111-44500-001.sip.ld = VVX 500
3111-46157-002.sip.ld = VVX 400
3111-48300-001.sip.ld = VVX 301
3111-48450-001.sip.ld = VVX 411

Just follow these easy steps:

1) Connect the phone to the network (and power supply if required).

2) The phone will power up and display “starting application, press cancel to interrupt”. You need to press the “cancel” button.

3) It should then display a new screen that displays three options. “Start”, “Setup”, “About”. Press the button for “Setup” and enter the password. (by default it is 456)

4) Then it will display “provisioning server” > Press “Select” and set the “Server” type to “HTTP” > Scroll down to “Server Address” and press “Edit” and enter the following:

5) Then Press “Exit” and then “Exit” again and select “Save and Reboot”.

6) Wait for the phone to reboot and contact our servers, if successful it should say something similar to “Updating XXXX-XXXXX-XXX.sip.ld, please wait”. Where X are numbers.

7) Leave the phone to download the application and wait until it boots up to the default Idle screen.

Important Note: Remember to upgrade the firmware version of the unit to the latest once the recovery has been completed. We can’t guarantee the firmware on the recovery server will be the latest.

Configuring a Sangoma Vega 3050G Gateway for use with 3CX

Firstly, log into your 3CX dashboard and navigate to the extensions tab on the left.

Create a new extension 

Replace the Authentication ID near the bottom with the extension number input at the top

Now, in a new tab navigate to your Vega’s web interface and log in. Once at the dashboard, click Quick Config on the left hand side. From here, click VOIP and change the Registration Mode to FXS Port. Next, replace the SIP Domain & SIP Server IP/Name fields with the IP address of your 3CX server.

Note: We also advise changing the first CODEC at the bottom to from g729 to none, as shown below.

After that, navigate to the FXS tab. You will notice that all of the Telephone Connections are enabled as shown below.

Disable all of the connections that you do not wish to use, and replace the Numeric Caller ID, Textual Caller ID, Telephone number and Registration and Authentication ID with the extension number, in this case 5001. Then type the authentication password in its respective field at the end of the row.

Return to your Extensions tab on 3CX. If you followed the guide correctly, there should be a green circle next to your new extension indicating that it has registered correctly and is ready to use.

If it is still red, go to your 3CX Dashboard > IP Blacklist and ensure that your PBX server has not been blacklisted automatically, as show below. If this has occurred, simply select the Denied IP, click edit and change Deny to Allow.



How to route calls via prefixes on the 2N VoiceBlue Next

If you are using prefixes from your PBX in order to route out via different SIM cards you need to configure the voiceblue to be expecting this. The first thing you will need to do is assign the SIM cards to a GSM group. In this blog it’s configured for two SIM cards/prefixes.

1. In the web user interface go to Gateway configuration > GSM group assignment and set each module to have their own group and press save.

2. Now we need to configure the prefixes that the voiceblue needs to be looking out for when a call gets sent to it. Under “Gateway configuration” go to “Prefixes” and then select one of the prefix tabs along the top.

2b) Once you’ve selected one of the Prefixlists we need to set the “Default count of digits” to the digit length we will be sending out via the SIM card and not how many are being sent to the voiceblue via the pbx. Example the voiceblue receives 12 digits and sends out 11 to the mobile network.

2c) Then we need to configure the table of accepted prefixes. This configures what prefix the voiceblue is looking for. In the “Detect prefix” field enter the desired prefix you are using then press “Add”. It should then appear in the list.

2d) Then we need to configure the “Table of replaced prefixes”. When the “/” is highlighted click the “Remove” button. Once removed in the “Remove prefix” field enter the desired prefix you are using and click the “add” button. Example: it should appear in the list as “8/”

2e) Once you’ve configured the above press save at the bottom and repeat for each prefix being used but remember to use a different list.

3a) Now we need to configure the LCR table. Go to “Gateway configuration” > “LCR table” and configure the first VoIP LCR by clicking the edit button.

3b) Then select the prefixlist that is going to be used for the first SIM group by editing “prefixlist or number of digits” with the prefixlist tab you configured earlier.

3c) We now need to configure the SIM group by going to “Groups/Tariffs” and selecting the required GSM group we created earlier.

3d) Press the OK button and then save the settings.

3e) Press the copy button for the VoIP LCR we just edited and then edit the prefixlist and GSM group as before for the second SIM routing and press OK and Save.

4) You should now be able to make calls via the desired SIM using prefixes on the voiceblue next.

2N External RFID reader for 125kHz & 13.56MHz How-to Guide

In order to use the 2N RFID reader you need to install the correct driver software.  This is only available for Microsoft Windows and can be downloaded from this page:

Scroll down to the Documents section and you’ll see the driver listed in the “Software & Firmware” list.

Once installed, you will see an icon in the task bar on your computer:

Right click this and select “Settings”.  This window will pop-up:

The device field may be empty, make sure you have the USB reader plugged in:

You may need to click refresh in the settings window.  Make sure you have the correct device selected before clicking “OK” to close that window.

Now you can use the reader to scan compatible RFID/NFC cards into the 2N Access Commander software or in the web interface for 2N intercoms and access control devices.

For example, in the web interface for an Access Control unit:

Click on the card icon and you will be prompted to scan a card:

That’s it, you’ll now be able to use that device to open the door.

Gigaset DX800A Call Transfer Guide


  1. Hold down a memory key for a few seconds until the function menu appears.
  2. Scroll down and select ‘R Function’.
  3. This will map the function to that memory key.
  4. When you want to transfer a call, press the memory key and a screen will appear. 
  5. Type in the number of the phone you want to transfer the call to and press the memory key again.
  6. You will get a screen like this to confirm the transfer has been successful:


Installation guide for 2N® 2Wire Kit

The 2N 2Wire adapter kit is extremely useful. Giving you the capacity to use exisiting 2 wire cable runs to connect IP devices to a network and power the device via PoE.

But it’s worth doing your homework so you can get the most out of them.

To help with this we have created this guide to help you get to grips with using them.

Essentially they are plug and play straight out of the box but……. this depends on how you want to use them.

Each 2Wire kit comes with two adapters and one power supply.

The solution works fundamentaly using a Master and Slave approach.

Any adapter that you connect the power supply to will become a Master.

Any adapter that you then connect to the Master via the 2wire connection becomes a Slave.

The Master should be connected to the network and the Slave connected to the IP device.

Any Master adapter can have up to 4 slaves connected to it.

Here we will look at three use case scenarios.

  1. Where a single Master & Slave set up is required on a single network.
  2. Where a single Master & multiple Slave set up is required on a single network.
  3. Where multiple Master & Slave set ups are required on a single network.

For the first two scenarios, where only a single Master adapter is required, the 2Wire kit is simply plug and play.

PLEASE BE AWARE that in the case of scenario 3, where multiple Master adapters are required on a single network, a pairing procedure must be executed.

If you connect multiple Master adapters to a single network without performing the necessary unpairing/pairing procedures YOU MAY EXPERIENCE NETWORK CONFLICT ISSUES.

Good thing is….. the unpairing/pairing procedure is very simple. Here we will guide you through it.

First let’s take a look at how to connect a single Master and Slave set up.

This is the simplest configuration and works straight out of the box.

Just make sure you connect the 2 wire correctly to each adapter. Positive to positive & negative to negative.

Now let’s take a look at how to connect multiple Slaves to a single Master.

This is similar to a single Master / Slave configuration in that it works straight out of the box. Multiple Slaves can be wired into a single Master.

Again make sure to connect the 2 wire correctly to each adapter. Positive to Positive & negative to Negative.

Finally we have the multiple Masters & multiple Slaves on a single network configuration.

If this configuration is required and you are installing multiple Master adapters on to a single network, it is very important to perform an unpairing/pairing procedure. If you do not you may experience network conflict issues.

Unpairing and Pairing your adapters

Each adapter has a small hole labelled ‘Grp’. There is a button inside this hole that is used to initiate the unpairing/ pairing procedures.

To access the button you will need a small screwdriver or similar tool.

To perform unpairing/pairing procedures the adapters must be powered.

So you must connect the power supply to the Master and connect the Slave via the 2 wire connection.

But DO NOT connect them to the network or the IP device….. yet.

To unpair an adapter press and hold the ‘Grp’ button for 10 seconds, until you see all lights on the adapter go off.

After unpairing is complete you should see only the power light illuminated.

You should do this on all adapters before attempting a pairing procedure.

To perform a pairing procedure press and hold the ‘Grp button for 2 seconds. When you release the button the ‘TWP’ light will begin steadily blinking letting you know that the adapter is in ‘seek’ mode and is looking for another adapter to pair to.

Once an adapter has found another adapter to pair to the ‘TWP’ will become static, letting you know pairing is complete.

In a single Master & single Slave pairing it doesn not matter which adapter you put into pairing/seek mode first.

But if you wish to have multiple Slaves connected to a single Master, then you must connect all Slaves via the 2Wire connection to the Master first, then run individual pairing procedures for each connected Slave.

To do this you must initiate the pairing/seek mode on the Master first and then the first Slave.

Then repeat this for each Slave connected to the Master.

But remember, unpairing & pairing is only needed when installing more than one Master adapter on a single network. 


Thanks for reading.




How to configure Snom 720 with Plantronics CS520 and EHS Advanced V2.0

List of Components:

  1. Plantronics Base
  2. Plantronics Cable
  3. 3.5mm DC Jack
  4. Snom 4 Pin Connector
  5. Snom EHS Advanced V2.0 Adapter
  6. Plantronics Headset
  7. Plantronics Base Power Supply


  1. Connect the Plantronics Base(1) to the Plantronics Base Power Supply(7).

2. Connect the Snom EHS Adapter(5) to the 3.5mm DC Jack(3). Note that only the DC Jack goes into this end of the EHS Adapter, you do not need to plug anything else into this end.

3.  Connect the Snom EHS Adapter(5) to the Snom 4 Pin Conector(4).

4. Connect the other end of the DC Jack(3) into the back of the Plantronics Base(1).

5. Connect the Plantronics Cable(2) to the back of the Plantronics Base(1).

6. Connect the other end of Snom 4 Pin Connector(4) into the slot in the picture below. Then connect the other end of the Plantronics Cable(2) into the Headset port, making sure you Do Not put it into the handset port by mistake.

7. Check the Dial settings on the bottom of the Plantronics Base(1) to make sure that they match the picture below. 

8. The headset should be ready to use. No phone settings should need to be changed, just make sure that all connections are secure and that you have power to the headset base.