Intermittent call drops on Voip.ms

<< < (2/4) > >>

drgeoff:
Be aware that passwords are NOT stored in the backup file.  After a reset to defaults you will need to manually enter them.

Shplad:
Wow, this site is a pain in the behind. It keeps logging me off. And the interface is so disjointed and confusing.

Anyways, printed out and backed up to disk my config. and settings. I then upgraded the firmware and reset to defaults. So far, it's up and running, but too early to tell if I will get call drops.

For now, here are my latest line tests from RingCentral:


















Does anyone have any idea idea why it can't perform certain tests? I don't have any connectivity or latency issues that I'm aware of on this cable connection. Or do I?

SteveInWA:
Take your device to some other network and test it there.

Shplad:
Thanks, but that's not practical. The problem is intermittent and so I'd have to bring all my supplies with me and stay at someone else's place for a days or longer to be able to run that kind of testing.

What else can you suggest?

SteveInWA:
When you restored your device to default, if you uploaded the saved configuration data mentioned in an earlier post, then perhaps you uploaded the same bad data that previously existed.

I would factory-restore the device, add it to the OBiTALK portal, and then set up voip.ms from there.  The portal has pre-built, known-good configurations for ITSPs, including voip.ms.  Do not restore your config file.

To do this, after successfully adding the device to the portal, click on the desired SPx slot, which will then take you to the SP configuration page.  Scroll down past the Google Voice banner to the bottom, click "OBiTALK compatible service providers", and then click "voip.ms" on the next page, fill in the simple form, and submit.  Wait.  Test again.  There is no legitimate reason to avoid using the portal.

If you won't test the device elsewhere, and you refuse to use the portal, then there's nothing left to advise you to do.  It appears to me that your internet service is inconsistent, based on the results of the tests you posted showing wide swings in the values.  That's why I wanted you to try it elsewhere.

Navigation

[0] Message Index

[#] Next page

[*] Previous page