12 hours without service

[patoka]

Been a voipo customer for a week now, until last night I was very satisfied.

Tried to order pizza about 8pm, got only fast busy after calling.
Sent an email to tech support.
8am Saturday, ticket is still open and still can't call out.

Still, 12 hours is better than the 5 days it took AT+T to fix my line in December.

[usa2k]

I expect you've done the standard mundane things,

• power down, then restart all your devices beginning with the Cable or DSL modem?
• try another number?
• try the phone on the second phone port?

Which ATA are you using?

Likely your post in any forum here will get someone, even though officially there is no technical support on the weekends.

• Available 9AM-7PM CST Monday-Friday

[VOIPoTim]

There are no outages, so you need to work with support to resolve this.

While our official support hours at Mon-Fri 9AM-7PM, we do have limited staff available in our office on weekends so you will get a ticket response.

[patoka]

RT31P2? (large Linksys, eyes do not get better with age...) pots port 2 same as 1.

reboot no change

inbound calls OK, outbound gives fast busy, but rings number called, nothing but dead air on called phone.

[usa2k]

So its directly connected to the Modem and is working fine for the attached PCs.

• What kind of modem is it?
• Odd that it worked for the better part of a week

Or maybe the VOIPo Tech has been talking to you by now?
When VOIPoTim says something is going to happen, it usually does.

I'm just a lowly user here, so my ideas do not represent VOIPo.

[patoka]

system diagram

Westell DSL modem --- hub --- Mikrotik router --- 8 port switch --- Linksys ATA.

I made 2 calls just a few minutes ago, both went through, then a fast busy, then a call with some distorted audio.

Tech support said to power cycle the modem for a config change, did that, nothing by busy signals again, but called phone rings.

[usa2k]

If its a RT31P2 or even a PAP2T, why not run directly off the hub?
It does not sound like the ATA is needed to serve as a router.

I assume the DSL modem is doing DHCP and that is why a hub serves a purpose?
Or is it a just point to monitor data traffic?

EDIT: not familiar with MikroTik Routers but their site is interesting!

[VOIPoTim]

system diagram

Westell DSL modem --- hub --- Mikrotik router --- 8 port switch --- Linksys ATA.

That sounds like the issue. If you take the hub out of the mix, it will likely solve the issue.

Try connecting the device directly to your modem and reboot everything. Then see if it solves your issue.

A switch would be fine, but hubs and VoIP do not mix sometimes from our experience.

[usa2k]

Try connecting the device directly to your modem and reboot everything. Then see if it solves your issue.

That is the best proof. Some routers can be problematic too.
If it works direct, try the hub, if that works, maybe it can stay there?
If it acts up again, retest directly.

I used a hub for a while without issues on WideOpenWest Cable (WOW!). That worked fine back then. The modem issued a maximum of three dynamic real world IP addresses, and did not do firewalling or NAT. Ultimately I feel a switch is a bit better than using a hub. It certainly routes traffic more efficiently. Obviously we only have a small picture of the various devices being used on your network to understand why things are as they are.

VOIPo is a residential product. Home networks are sure becoming more complex every year! Mine is no exception. That will surely mean support issues that are not a direct result of anything VOIPo is doing.

[VOIPoTim]

Also since this is a support/troubleshooting thread and not a straight review, I am moving it to the Residential VoIP discussion forum. The reviews section is only for reviews about the service and the Residential VoIP forum is more appropriate.