Something stuck? No Vpanel or inbound calls

[Xponder1]

Everything is working for you though right?

Mine is working fine on both ports. I only pointed it out because they are settings you or Brandon asked us to change. I dunno what mine is doing this morning but its sure hammering away at the internet. The wan light is flashing none stop and my router is showing its hammering away. It is using somewhere between 250 and 500kbps none stop with the phone not in use. Are you all doing something? It seems to be all outbound traffic from the device.

[orum]

I didn't have any issues throughout the weekend, while there were others troubleshooting. I just came home for lunch. Incoming calls are not coming into our phone and of course, no MWI.

I checked vPanel and no devices are registered.

I just rebooted my ATA and all appears to be well again.

My ATA is behind my router with all the appropriate ports forwarded.

Dan

[christcorp]

I'm still having issues. Almost once a day; maybe every other day; I lose incoming calls and have to reboot the adapter. Then it's fine for a while again. My settings are the same that others are mentioning. I notice by telnetting in that my port 1 will become UNREGISTERED (Yet I can call out); and Port 2 will still show REGISTERED. Luckily, between failover and simultaneous ring, I'm not missing calls.

It's possible that every time VoipO makes a change, that it's requiring the adapter to be rebooted. If true; this wouldn't be a problem if VoipO was only making changes every so often. But this is becoming a regular thing. I personally am not upset, because I'm a techno-geek and don't mind troubleshooting it. And as long as outgoing is still working, my wife will never know. (Most calls are outgoing; very few incoming). I believe the same thing is happening to my beta line which is on a Linksys RT31P2. I've had to reboot that one a couple of times. Same issue; outgoing fine, incoming not. This is only something that's been happening for the last few weeks. I've move the 502 into the DMZ of my router just in case. "Even though I don't have any router settings that should be affecting the voipo lines".

Any thoughts If not, I might take it off of auto-provisioning so I can experiment with certain settings. But the fact that similar things is happening with the Beta line on the linksys, makes me believe that it's something at the SIP server level. But to be honest, I haven't monitored the Beta line as extensive because I normally don't have a lot of incoming calls on that one. I will check it when I go home tonight to see if I have to reboot it. later... mike....

[VOIPoTim]

I'm still having issues. Almost once a day; maybe every other day; I lose incoming calls and have to reboot the adapter. Then it's fine for a while again. My settings are the same that others are mentioning. I notice by telnetting in that my port 1 will become UNREGISTERED (Yet I can call out); and Port 2 will still show REGISTERED. Luckily, between failover and simultaneous ring, I'm not missing calls.

It's possible that every time VoipO makes a change, that it's requiring the adapter to be rebooted. If true; this wouldn't be a problem if VoipO was only making changes every so often. But this is becoming a regular thing. I personally am not upset, because I'm a techno-geek and don't mind troubleshooting it. And as long as outgoing is still working, my wife will never know. (Most calls are outgoing; very few incoming). I believe the same thing is happening to my beta line which is on a Linksys RT31P2. I've had to reboot that one a couple of times. Same issue; outgoing fine, incoming not. This is only something that's been happening for the last few weeks. I've move the 502 into the DMZ of my router just in case. "Even though I don't have any router settings that should be affecting the voipo lines".

Any thoughts If not, I might take it off of auto-provisioning so I can experiment with certain settings. But the fact that similar things is happening with the Beta line on the linksys, makes me believe that it's something at the SIP server level. But to be honest, I haven't monitored the Beta line as extensive because I normally don't have a lot of incoming calls on that one. I will check it when I go home tonight to see if I have to reboot it. later... mike....

Has anyone had a drop today (and you know it was fine this morning) or could these have been from yesterday/overnight?

[christcorp]

Well I did a number of reboots last night on my network. (I was working on stuff - not really IP related). When i was done, late, I call TO my voipo lines 2 or 3 times to make sure they would ring in. They worked fine at about 11pm last night. As well as showing REGISTERED. It wasn't until I checked my adapter via telnet a couple hours ago that I saw that port 1 was UNREGISTERED and port 2 was registered. So, whatever happened, happened today. later... mike....

[burris]

Well I did a number of reboots last night on my network. (I was working on stuff - not really IP related). When i was done, late, I call TO my voipo lines 2 or 3 times to make sure they would ring in. They worked fine at about 11pm last night. As well as showing REGISTERED. It wasn't until I checked my adapter via telnet a couple hours ago that I saw that port 1 was UNREGISTERED and port 2 was registered. So, whatever happened, happened today. later... mike....

I went back to sip with the original settings and all seems fine..

I was having a similar problem on Central02 with the test settings this afternoon.

[christcorp]

I've ONLY used sip.voipowelcome.com for my PRIMARY LINE. I've ONLY used jupiter for the beta line. later... mike....

[sr98user]

Has anyone had a drop today (and you know it was fine this morning) or could these have been from yesterday/overnight?

I haven't had a drop since yesterday. Before that, it dropped registration twice. I am on sip.voipwelcome.com and provisioned.

When it dropped before yesterday, one line would show registered and other as not registered. But the vPanel would show no registered devices and calls would go to the network down number.