Versions Compared

Old Version 9

changes.mady.by.user Former user

Saved on

compared with

New Version 10

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated page to add workarounds to allow the new SPA122 device to work, even though it is not yet officially supported.

Introduction

...

This document includes general information and some workarounds for these issues, until they are fixed.

Change of models

In May 2012 Cisco/Linksys stopped manufacturing the SPA2102 device (they still make the SPA3102).  They sell a new model, the SPA122, which is not currently supported by Sipx, but which can be used with a few minor workarounds because the profile that Sipx generates for the ata2102 device is sufficiently compatible with the new device.  Making it work primarily requires some minor changes to the provisioning sequence.  See notes below under the relevant sections.

Provisioning

Profile

Provisioning on these ATA devices works as follows (assuming you have a retail version of the device, rather than one which has been bulk-purchased and custom configured).  

...

Like all Sipx device profiles, these values consist of (1) the default values that Sipx ships with, with (2) any modifications to those defaults that were made in the device profile in the “Phone Group” that contains this device, plus (3) any modifications made in the device itself after creating it in the Sipx web interface.  The Linksys device loads this profile, and reboots itself, leaving it ready to operate.

For SPA122

By default, the SPA122 will look for a file called "spa122.cfg" in the root of the TFTP directory.  That file does not exist by default in Sipx, so it must be created manually.  To do this, go to the directory /var/sipxdata/configserver/phone/profile/tftproot and copy the file "spa2102.cfg" as "spa122.cfg".  This only needs to be done once per server to support any number of SPA122 devices.

If you prefer not to make changes on the server, you can instead change the provisioning rule on the SPA122 device.  In the web interface of the device, go to the page Provisioning under the Voice section.  The field Provisioning Rule is set by default to "/spa$PSN.cfg" (which is what tells it to load the file spa122.cfg).  Change this field to the string "/spa$MAU.cfg" and that will instruct the device to directly load the profile generated by Sipx (the macro $MAU gets expanded to the device's MAC address with letters in upper case, which is how Sipx names the profile).  This would need to be done manually on each SPA122 device.

Firmware

If desired, the device can also be configured to automatically update its firmware.  To do so on Sipx, place an appropriate firmware file into the Sipx TFTP root directory (/var/sipxdata/configserver/phone/profile/tftproot/).  For example, the current firmware at the time of this writing (version 5.2.10) might be in a file named spa2102-5-2-10.bin.

...

  1. Use the default setting to allow the SPA device to receive its addresses via DHCP. You can optionally configure your DHCP server to give the device a known IP address, or just let it get one at random.   If you choose random, and want to get access to the device’s web interface for some reason, see the troubleshooting section below.
  2. In the Sipx web interface, create a user (if necessary) then create the device by using the Add New Phone pulldown, and selecting "Linksys ata2102" or "Linksys ata3102" (for the SPA122 device, choose "Linksys ata2102"). Enter the "Serial Number" (i.e MAC address) which is shown on a sticker on the device.  Attach the user to one of the lines on the device.  If you are using a VLAN for your phone/ATA devices, be sure to enable VLANs and configure the VLAN ID in the profile on the page VLAN_Settings. Send the profile for the device. 
  3. Plug in the ATA device to the network, ensuring that it is on a port capable of reaching the Sipx server via TFTP.  If using tagged or static VLANs, ensure that the the port you are plugged into to is configured to support your phone VLAN.
  4. Power on the device.  It should load its profile from Sipx and restart itself.  If you have configured it to also provision firmware updates, it may also load a new firmware version and restart again.  DO NOT interrupt this process (which takes up to 2 minutes on my system). When it’s complete, you should see 3 steady lights on the device, and it should offer you a dial tone when you attach a phone and go offhook.  You should be able to see the device’s registration on the Sipx Diagnostics / Registration screen. 
  5. If things don’t work as expected, see Troubleshooting below.

...

You can initiate a manual restart or a reload of the profile on a Linksys ATA device by entering appropriate URLs for the device through a web browser.  If an administrative password has been set, you will be prompted to enter the username (usually “admin”) and password (see note above to set it, default should be "admin") before the request will take effect.  Assuming an IP address for the ATA device of "192.168.1.100, the URLs are:

Reboot:

Code Block

http://192.168.1.100/admin/reboot

Resync:

Code Block

http://192.168.1.100/admin/resync

You can optionally include a URL of a specific profile to resync to (although this rarely makes sense in a Sipx deployment), for example:

Code Block

http://192.168.1.100/admin/resync?tftp://192.168.1.200/basic.txt

...