Customization: Customized Unfortunately, you have no stock PAP2 - the device you have has been manufactured for a large Cisco (well, Linksys) customer (probably a large ISP or so)  and has been customized to satisfy it's specific requirements. In short, you just can't use.   Well, sometime, the burned-in configuration may not be 100% safe, so there MAY-BE chance to break-in, but it require skills, a lot of time, and it may not end in success. If you are skilled IT technician and you have two or three days of spare time, you can try it. But unless you take it as challenge, it's ineffective use of your time.  ... View more

It looks rather like network issue than phone issue.   It is a pre-configured phone ? How the 192.21.x.x address has been assigned to it ? I mean - are you sure you know it's IP address correctly/have your phone the IP address you thing ? Is the IP address in question reachable from the computer you are trying to do it ?   Your LAN administrator should be able to help you with those questions. ... View more

Unfortunately, documentation is imperfect. Cisco doesn't follow all changes in firmware - so it may be syntax for an old firmware (even original 1.0.2 which is no longer available at all). Or you hit firmware bug - unfortunately, Cisco doesn't care bug reports so much from users with no service contract (and even with it your chances for fast solution are not so good).   My advice ? Forget pushing using curl. Lets SPA112 fetch configuration from your Linux server instead. It can fetch it periodically, so there may be some delay, but it works.   And if you have local Asterisk, you can trigger fetch of configuration from it.   Note that new configuration causes device reboot most of time - thus service disruption for users. ... View more

attempt to use SPC to compile ... resulted in 28 “unrecognised parameter names”. Did you downloaded the latest SPC compiler (just blind shot, I'm not using SPC) ? how to access it without using the http://userid:password@... syntax (which leaves the admin credentials lying around in browser history and doesn't work anyway) isn't immediately obvious. It works for me, but it may be matter of browser used. Also, my browser doesn't save passwords in history. Moreover, it's one-time step. Once configuration gets saved, you need no to access the URL again. But it's not main security issue you have.   SPAxxx devices are NOT designed to be exposed in unfriendly environment. They lacks countermeasures against DoS, brutal-force style of password guessing and there in the past severe security bugs has been discovered including those allowing unauthorized access to the device. So you are in risk of tool fraud and it may be costly experience.   You should keep phone network separated from regular network, so regular users have no access to SPAxxx devices at all. Of course, overall security design of your network depends on local conditions, risks you wish to avoid and - of course - budget and skills you have ...   We have phone network in separate LAN with no connection outside, so no one can arrange DoS against them nor misuse a firmware vulnerability. Devices can speak with local PBX only (just free Asterisk) and PBX can access outside. Configuration are loaded from server via HTTPS protocol, SPAxxx authorizes self to server by in-device embedded certificate - so even if someone connects computer to phone network, he have no chance to fetch configuration of a phone (e.g. passwords stored in configuration can't be compromised) - it in turn mean he can't connect to PBX, so he can't make unauthorized calls (and possible tool fraud).   ... View more

Sorry, spacfg.xml is name for SPA3xx/SPA5xx devices. For SPA1xx/SPA2xx the config.xml needs to be used instead. See SPA ATA: Saving Configuration for Analysis Using admin/config.xml for details. I prefer XML form of configuration because 1. configuration saved by Save function is in proprietary binary format. You can do nothing with it but load - and even this may not work. 2. XML can be generated by a custom tool or edited in plain text editor I will not claim it "good practice" - I just consider it better.   why do you advise not using SPC to convert an existing .cfg file to xml   Note that cfg produced by "Save" is not the same as text cfg suitable to be used by SPC. Those are completely different beasts. The first one is proprietary binary blob, the second is text file (but different format than XML). It's why you can't compile saved CFG by SPC. I'm unsure the SPC can convert CFG (text CFG created for SPC, not the [Save]d one) to XML. I'm not using SPC at all, so I don't know what features has been added into it in the mean time. But even if it can convert, I have no reason to do it. Plain text CFG for SPC and XML are bot text files. Both are readable by naked eye, both can be edited by text editor or generated by simple custom tool. But text CFG for SPC needs to be compiled while plain text XML can be used as is. The first one require external binary program, while the second method require nothing. May be better question is - why I should use SPC for anything ...   ... View more

You are asking us ? It's customized car. We don't know the topology of internal electronics. You even didn't disclosed what devices are connected to SPA8800 (and port number of each connected device).   Well, as a blind shot - SPA8800 is used as POTS (analog) <-> SIP converted. It's protocol convertor ... View more

No way to recover access without reset to factory default. But you wish to support vehicle in the future - it mean you need to understood the network topology, you need to know who's your VoIP provider and how the gateway needs to be configured to connect to it. With those information you need no current configuration, as you will be able to recreate it from scratch. Even if you will replace SPA8800 with something else, you need those information to configure such device. In short, you just need to know how it works - at IP level as well as VoIP level.   OK, to seems you know the network topology, so you know how to configure SPA8800 at the IP level. Now you need to discover VoIP parameters. You need to know who's your VoIP provider. As you are paying bills to them, you know who is it.  Call support and ask for "How to configure VoiP client" white paper. .   ... View more

My recommendation is - don't use save/load feature at all. XML form of configuration can be fetched via http://[phone ip]/admin/spacfg.xml URL. Such save contain no password, you need to add them by manual edit. It's one time step - once configuration become saved this way, it become primary source of configuration. Every change of configuration you wish to do needs to be done in this file. So you have "backup" of configuration and you need not to save it anymore. This file can be provisioned into phone whenever you wish - just configure "Profile Rule" to a server where the XML configuration can be fetched.   Forget SPC, XML configuration is used as is, no compilation is required.   ... View more

the spa8800 is being fed uplinks from a cellular modem and a satellite modem through an asa5505 There was some recent electrical work on the vehicle itself and the phones stopped working. fall into our domain.  It should be analyzed step by step. Is the IP connection working - e.g. can you communicate from in-car LAN outside ? Is SPA8800 network configuration correct ? Can you ping it from in-car LAN ? Is SPA8800 registered to VoIP provider ? Such information is available (among others) on WWW status page of SPA8800 - it's available even with no login credentials entered. If it's not registered - capture SIP packets, identify where the SPA8800 is trying to register and SIP responses to registration request. Ask your VoIP provider for help if registration requests triggers and error response. Note - starting from this Friday I will have no access to internet for two weeks. So I will be unable to guide you step by step. You will be on your own. Sorry. ... View more

Few days has passed, but no logs has been disclosed. I assume you solved it.   Otherwise - as a blind shot - symptoms you described may be caused by a NAT issue. ... View more

Reset to factory default is the only password recovery procedure for this device. Configuration will be lost and needs to be recreated. Your new engineer will do it for you. He need to know who's your VoIP provider (you are paying bills to them) and it's "How to configre ..." documentation (VoIP service provider will send you a copy).   By the way, I know no other 4xFXS+4xFXO ATA gateway available - even from another vendor. ... View more