05-13-2011 02:32 AM
Hi,
at our office we've recently upgrade from a old consumer-grade linksys wag200g modem/router/ap to the Cisco SRP527w.
The Cisco is suffering from very frequent ADSL disconnections.
These disconnections happens when there is some traffic to the internet and they seem to don't affect the lan routing: on the weekends there are no disconnections at all while during the working hours there may be disconnections every FEW MINUTES making this router unusable.
Often these disconnections force us to do a full reboot of the router.
Firmare version is SRP520W-1.1.19, the latest.
ADSL line is a 6Mbps/640kbps.
Noise margin is about 11dB for downstream and 20dB for upstream.
No voice line is used and therefore they are both disabled.
2 wireless network are active.
The old linksys was (and is) working correctly, no adsl disconnections at all. Never.
Is there a solutions to this problem? Is it known?
Regards,
Federico Sassi
09-08-2011 04:45 AM
Hi Andy,
Thank you very much for your help. FYI, I have tried to reinstall the original firmware version 1.2.0 (with Voice working fine) on my SRP547W device but the Voice tab is still giving me the "Voice Module not ready" message. So, after this I reinstalled the latest firmware, 1.2.1, again and made no difference.
With that said, I backup the current configuration and I performed a factory reset (pressed the reset button for 10 seconds). The Voice tab is now working fine. After this I restored my configuration from the backup and the Voice tab was giving me the "Voice Module not ready" message again. Finally, I went to Administration tab and run the option "Restore Factory default for Voice" which made no difference. However, when I went to Administration tab and tried to the "Setup Wizard" my current configuration failed to load. Also the SRP547W device help file states that a factory reset may be required if the Voice has issues after a firmware upgrade.
The conclusion that I have is that somehow the firmware upgrade 1.2.1 has corrupted my current configuration causing the issues with the Voice module. This is really a pain since I will have to reconfigure the device from scratch costing me hours of valuable time!
I thought I would share this with you just in case anyone raises this issue in the support community.
Thanks,
Claudio
09-08-2011 01:02 PM
Thanks for your feedback Claudio,
Firstly, I'm glad that you were able to get the voice screen working again by factory resetting the device.
An alternative approach to reconfiguring your router is to the XML provisioning interface. Please see for more details.
Essentially you collect the configuration in XML format, then push it back after resetting the device.
As this is a programmatic reprovisioning of the system, rather than restoring a backed up configuration state (which in your case seemed to be corrupt somehow), you shouldn't have any problems.
Regards,
Andy
05-29-2012 01:49 AM
We are still getting disconnection issues. The modem router is pretty stable with the 3G as WAN link. However, using the dsl line, the maximum uptime that we can get is at least 3 weeks... I just recently upgraded the firmware to the latest release. Hopefully it will resolve the issue, i also notice the new vpn feature from the new release.
Note that when the dsl connection drops, I can access the GUI, the RAM and CPU utilization appears to be normal. The logs has not been very helpful, it will only record the reboot activities that we normally do to resolve the disconnection issue. We are really about to give up on this box, the latest firmware is our last shot. Other than that I really don't know what to do already. We need to get this going and stability has been the main concern. Otherwise we will not be able to provide this device for our business broadband packages.
Desperate me,
Kathy
05-29-2012 02:02 AM
Hi,
we had a very similar problem (router needed reboot for DSL connection every day/week).
Last firmware has improved the situation A LOT but it's not yet perfect. A couple of reboot were needed.
Up to now we have an uptime of 41 days.
Firmware Version: | 1.01.26 (003) Feb 17 2012 |
Good luck.
Federico
05-29-2012 02:16 AM
Hi Federico,
same firmware version here and we had a disconnection issue after three weeks. Not really sure what to do anymore on this. We are currently looking for another router that we can test.. tsk tsk
Current firmware version: 1.01.26 (003)
Thanks again for your feedback,
Kathy
05-29-2012 02:41 AM
We improved the stability by decreasing the DSL connection speed.
We are also experiencing also WiFi stability issues. We need to turn it off and on again (while DSL and eth connection still works fine).
Anyway I think there will be no solution until Cisco releases a stable firmware.
Federico
05-29-2012 02:45 AM
Thanks Federico.Will adjust the DSL connection speed and see what happens.
Yeah, hopefully Cisco dev team are still working on the new firmware. Hopefully it is not any hardware or dsl chipset compatibilty issues.
Kathy
05-06-2013 03:36 PM
Hi Andy,
I'm having the same issue as Claudio but I see that there was no further communication between you two. I have the latest firmware for the SRP541W and have tried all that you have suggested and what Claudio has performed but still get 'Voice Module Not ready'.
You mentioned an XML configuration method to the router, do you have any more direction or information on this?
Thanks,
Ed
Sent from Cisco Technical Support iPhone App
05-07-2013 02:54 AM
Hi Ed,
Are you still seeing voice module not ready after a factory reset? Did you factory reset after upgrading?
You can find more information on XML provisioning at the following:
https://supportforums.cisco.com/docs/DOC-16131
Regards,
Andy
05-07-2013 03:57 AM
Hi Andy,
Yes unfortunately I am still getting the module not ready after a factory reset. Interestingly I have tried to grab the config.xml from the device using the guide you have included and am getting an Internal Server Error (500) which usually means that the service is unavailable for whatever reason.
I am thinking that at this stage I will factory reset, downgrade from 1.25 to an earlier version and then check voice and then upgrade before applying any configuration. It is probably something silly with these devices the are usally pernickity about the way things are done.
If you have any more information or ideas please feel free to share though.
Thanks and regards,
Ed
05-29-2012 02:54 AM
I hope so.
It would be nice to have somebody from Cisco acknowledging those issues and confirming that they are working on them.
regards,
Federico
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide