Hi, i'm a VoIP provider planning to migrate to SPA122 (FW1.3.1) for my residential customers. Everythying works perfectly so far (mass provisioning, feature interop, etc) but for some reason i'm not getting any logs from all the SPA122 i've tested. I'm sending logs to my already existing and working global syslog server. I'm also trying local and mail just to make sure logs are generated.
Log module: Logging is enabled in log module on local | email and syslog server for both kernel and system | level debug
Log setting: size@200 | syslog IP set to local (routed) IP, not same subnet but it responds to ping | port 514 | email settings all OK | number og log 200 | interval 3 minutes
Voice/System: sylog and debug server set to my syslog server IP | debug level 3 (tried all 6)
Voice/Line 1: sip debug option at full
No log on my syslog server
No log received by email
No log in administration/logviewer/download log (all)
Is there an option i missed? Know issue? All other settings beside voip are pretty plain, beside LAN/WAN acces is only allowed on HTTPS.
Provisionned through XML and manualy through GUI (both tested)
Unfortunately i got no answer. I had to leave this problem aside for now, but i'm thinking it might come from my switch manufacturer (Metaswitch) base config file provided for SPA122 ATA's. I'll let you know if i find something.
This could be the provisioning file from your metaswitch / provider. Those files are firmware version dependant, so if you have a config file setup for 1.0.x firmware and load it on a 1.3.x device, strange behavior can happen.
I would suggest factory reset the device, configure just logging, and proxy/username/password
To enable logging on the spa go to Voice --> system add the IP address of your log server in the debug and syslog, set debug level =3 Go into the extension --> sip settings --> sip debug option to 'full'
if that works, you can update your config files on the provisionin server by exporting the xml from the SPA ( http://ip/admin/config.xml ) or use the SPC tool to create a factory default config.
spc tool is downloaded from the firmware download site, and is specific to firmware versions,
spc tool use is detailed in the provisioning guide here https://supportforums.cisco.com/document/37081/cisco-ip-telephony-devices-provisioning-guide
btw, your device is under warranty, so you can go onto the cisco site, hover over support --> open a case, then call into 866-606-1866, we can assist you.
Article ID:1966 Network Address Translation (NAT) Settings for Lines on
PAP2T and SPA3102 Phone Adapters Objective The objective of this
document is to configure Network Address Translation (NAT) settings for
the lines of communication on the PAP2T and SP...
Article ID:2742 Speed Dial Settings on SPA100 Series Objective Speed
Dial Buttons are often used to make the process of calling regularly
used contacts quicker and with one button. This option is used in place
of dialing the entire phone number in. This h...
Article ID:2676 Firmware Upgrade on SPA112 and SPA122 Objective To
upgrade the firmware a specific file must be downloaded from the
Internet and uploaded to the device. Upgrading your devices can be very
useful. Firmware upgrades can fix software bugs, im...