I am working with Linksys SPA2102 ATAs (Analog Terminal Adapters) for my 
residential sipx rollout, and I am having a problem with their provisioning.  

I have created the phone profile and generated it.  All settings look as 
expected in the tftproot dir.  When I reset the device and watch it with 
wireshark, I can see it request and receive its IP address, load the 
spa2102.cfg file via TFTP,
load the spa<MAC_ADDRESS>.cfg file.  It seems to complete fine.

The next thing I see is the device requesting the spa2102.cfg again, and then 
it seems to be hosed.  I see repeated offers from the DHCP server for 
addresses, but the device ignores them.  When I call the voice interface on the 
ATA and check settings, it indicates that it has lost its IP address, and that 
the addressing mode has become "aasn", or sometimes "alasn", neither of which 
is a valid option (it should be static, DHCP. PPPOE, etc.).  

It's as if the parsing of the config fails and crashes the device, but I can't 
be sure, as it is difficult to tell exactly what is going on with these cryptic 
devices.

Does anyone have any suggestions?  Is there anyone out there using this device? 
 If so, perhaps you could attach a sample of a working spa<MAC_ADDRESS>.cfg 
file that I could alter and put into play as a test.  

Thanks,

Jeff

P.S. I did update the device to the latest firmware, with no improvement.


_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to