Future Nine Not Working Most Times

<< < (7/9) > >>

Mango:
DNS has been fixed.

ebow:
Quote from: Mango on September 08, 2014, 05:06:29 pm

DNS has been fixed.


Yup, and I'm able to log into the customer portal site and all my info appears to be intact. Was able to just make a call out and call in!   ;D

edit: and I didn't do any kind of re-registering or anything, just waited and tried a few times.

ebow:
Another thought: this thread title is "... not working most times" -- I haven't found that to be the case, myself. There have been some glitches, including DTMF beeps from vocals, a few call cutoffs, and a bit of latency over the past few months (from what I understand, things that can be expected from most lower cost VOIP providers), but mostly it works pretty well up until this outage. Here's hoping it was just a server crash or attack that can be prevented in the future!

Mango:
The topic was started by a user with a configuration issue, so the subject isn't related to today's DNS issue.  My guess is the OP had a problem with his router.  He hasn't been back, so hopefully that means the firmware upgrade solved the problem.

There was no server crash (customers were able to make/receive calls if they registered to a server's IP address).  At the moment, no evidence of an attack.  Apparently their DNS provider erroneously suspended their account.

ebow:
Quote from: Mango on September 08, 2014, 05:27:12 pm

The topic was started by a user with a configuration issue, so the subject isn't related to today's DNS issue.  My guess is the OP had a problem with his router.  He hasn't been back, so hopefully that means the firmware upgrade solved the problem.

There was no server crash (customers were able to make/receive calls if they registered to a server's IP address).  At the moment, no evidence of an attack.  Apparently their DNS provider erroneously suspended their account.


Thanks for clearing that up. I have a lot going on and have been reading threads a bit too quickly.

I'm curious about registering to the IP address, though, in case this happens again in the future. I've forgotten a lot about what I learned when I first got my OBi and set up F9, since everything worked smoothly. Would I put the IP address in the "Service Provider Proxy Server" field in my ObiTalk dashboard (instead of "incoming.future-nine.com") or in each spot that I find "incoming.future-nine.com" on the local device config site (192.168.x.x)? Actually, I bet they're the same thing (simple vs. advanced access).

Navigation

[0] Message Index

[#] Next page

[*] Previous page