Anybody Having Trouble Today?

**VOIPoTim** · 09-30-2010 07:49 PM

Originally Posted by Russell

So far the "adjustments" appear to be working. Not many calls, but no issues with the calls that have been made or received.

Glad to see. See, sometimes opening a ticket really does work.

**Russell** · 10-02-2010 09:05 AM

Originally Posted by VOIPoTim

Glad to see. See, sometimes opening a ticket really does work.

Tim,

Now that you've had the satisfaction of saying, "I told you so" :-), would you be kind enough to let me (and other curious readers) know what kind of "adjustments" were made on my account? As previously mentioned my setup could not be more vanilla: RT31P2 connected directly to the UVerse router (which Brandon has successfully tested with numerous devices). 12Mbps/1.5Mbps service UVerse service.

**VOIPoTim** · 10-02-2010 10:26 PM

Originally Posted by Russell

Tim,

Now that you've had the satisfaction of saying, "I told you so" :-), would you be kind enough to let me (and other curious readers) know what kind of "adjustments" were made on my account? As previously mentioned my setup could not be more vanilla: RT31P2 connected directly to the UVerse router (which Brandon has successfully tested with numerous devices). 12Mbps/1.5Mbps service UVerse service.

It's not really as simple as saying that a certain router or network setup needs X done to work well. It's more about looking at everything including our logs to see how the traffic is flowing and where errors are.

Every situation is unique. Even a minor firmware version difference in a router/modem can mean that the two versions need complete opposite tweaks applied. Just like we don't have scripts for support, we don't have specific things that are done with different models.

Support reps will simply just look at it, look at the traffic, diagnose, and then change it so that the traffic starts looking valid and problem-free.

For example with audio issues, customers may insist it's a "cheap router", a bad device, etc but one quick look in our logs may show the audio stream stopping when it hits their router. We also see a ton of cases where the traffic is coming through but is being "deformed" by a SIP ALG on the router, etc. These are all cases where we can take a look and between seeing the logs, the network setup, etc diagnose.

Support can determine what needs to be done and do it. That's why we encourage everyone to contact support. Contacting support is the always going to be the fastest and most efficient way to get problems resolved.

**Russell** · 10-03-2010 09:13 AM

I'm not sure if it's coincidence or not but right in the middle of a Skype call the RT31P2 decided to reboot. Obviously, the Skype call got dropped. My setup: computer connected to RT31P2 connected to UVerse box.

**VOIPoTim** · 10-03-2010 04:12 PM

Originally Posted by Russell

I'm not sure if it's coincidence or not but right in the middle of a Skype call the RT31P2 decided to reboot. Obviously, the Skype call got dropped. My setup: computer connected to RT31P2 connected to UVerse box.

If it's happening frequently, then just contact support to work through it.

A periodic reboot is normal though. How long had it bee since it rebooted?

If the devices aren't rebooted periodically, they will reboot (typically weekly) to download the new provisioning file in case there are updates. We can't really push any changes to them without a reboot so it's important to have them reboot periodically to process changes.

A periodic reboot is also needed just to refresh the device. They will not stay on and work well indefinitely without a reboot. If they are on more than a week or so without a reboot, you'll start having dropped calls, poor voice quality, lost registrations, and just general erratic behavior. There's actually a thread on DSLReports now where people are discussing if Linksys VoIP devices need a reboot periodically and the majority opinion is yes that they get very unstable if not rebooted periodically.

http://www.dslreports.com/forum/r248...est-recreation

Finally, another case where a reboot may sometimes be needed is in a failover scenario on our end where we're re-provisioning the device to another server. In a case like that the system will typically send a reboot signal in the SIP headers to the device.

**Russell** · 10-03-2010 04:33 PM

Originally Posted by VOIPoTim

If it's happening frequently, then just contact support to work through it.

A periodic reboot is normal though. How long had it bee since it rebooted?

If the devices aren't rebooted periodically, they will reboot (typically weekly) to download the new provisioning file in case there are updates. We can't really push any changes to them without a reboot so it's important to have them reboot periodically to process changes.

A periodic reboot is also needed just to refresh the device. They will not stay on and work well indefinitely without a reboot.

Not sure if there's anyway to determine past reboot history. If there is tell me how and I'll look it up. Just checked and it's now been running for 08:21:07 which makes the reboot time when I was in the middle of my Skype call (a little after 10 am local time).

May I suggest that the periodic reboots to refresh the device be done in the middle of the night. Ideally, it'll be a control panel option as to when this should take place with the default being something like 3 am - I'd choose the middle of the night based on our family schedule.