No devices registered in Vpanel

[ralfaro]

I hate to pile up on you guys, but I have been having the same issues and I am assuming it is the same problem. Last night between 6 and 7 pm I received 2 calls on my failover number, so I am assuming the ata had become unregistered. Shortly after 7:15 or so, it started working again. I opened a ticket on this. Now, this afternoon, another call went to my failover, in fact it was from another Voipo number and shortly thereafter it was working again. I have rebooted that AATA 2 or 3 times since yesterday thinking there was some sort of config push I hadn't gotten, but this seems to be an on-going issue. Thankfully, my failover seems to be working fine so I can deal with it, but I'm hoping someone gets a handle on this soon. So far I have turned several people onto Voipo and they have signed up, but I don't dare do this now until this problem gets solved for good. I know you guys are trying hard to get to the bottom of it, so I wait patiently, knowing that you will indeed solve this soon.

RA

[VOIPoTim]

I hate to pile up on you guys, but I have been having the same issues and I am assuming it is the same problem. Last night between 6 and 7 pm I received 2 calls on my failover number, so I am assuming the ata had become unregistered. Shortly after 7:15 or so, it started working again. I opened a ticket on this. Now, this afternoon, another call went to my failover, in fact it was from another Voipo number and shortly thereafter it was working again. I have rebooted that AATA 2 or 3 times since yesterday thinking there was some sort of config push I hadn't gotten, but this seems to be an on-going issue. Thankfully, my failover seems to be working fine so I can deal with it, but I'm hoping someone gets a handle on this soon. So far I have turned several people onto Voipo and they have signed up, but I don't dare do this now until this problem gets solved for good. I know you guys are trying hard to get to the bottom of it, so I wait patiently, knowing that you will indeed solve this soon.

RA

Can you open a ticket so we'll have that and can work with you there?

This could be back, but we've only had 3 reports of any issues now and usually we'd have hundreds, so it may still be isolated.

[ralfaro]

Tim, I did open a ticket on last night's issue and got a reply from Justin stating they were looking into it. I didn't open another ticket on this afternoon's issue because it was basically the same thing as last night. The ticket number is [RSQ-524455.

I am about to open another one though regarding voice mail. Even though I have auto-login checked under voice mail options, the system is prompting me for my password. I rebooted, but still the same thing.

RA

[VOIPoTim]

Tim, I did open a ticket on last night's issue and got a reply from Justin stating they were looking into it. I didn't open another ticket on this afternoon's issue because it was basically the same thing as last night. The ticket number is [RSQ-524455.

I am about to open another one though regarding voice mail. Even though I have auto-login checked under voice mail options, the system is prompting me for my password. I rebooted, but still the same thing.

RA

Rick,

I'll take a look at that ticket and we'll see what we can do for you to get you situated.

In terms of the auto login, I just made a post about it: http://forums.voipo.com/showthread.php?p=9114#post9114

[christcorp]

For what it's worth: Tim, I and Justin (VoipOJustin); worked back and forth on my Grandstream in the beginning in the week when it had all the same problems. No registration, dropping registration, etc... We changed the registration to 1 minute; changed to Central02 server; downgraded the firmware to .15. I have not had one problem sense then. There are 2 MINOR problems, but they are server related and not that important.

1) The grandstream shows BOTH PORTS registered. BOTH PORTS work. I can be on a call on PORT 1; and make another call on the clone in PORT 2. ALL IS GOOD. However; in the Vpanel; ONLY 1 device shows up as registered. Again, this is not really a problem. But I did know that prior; on the sip.voipwelcom.com server, I would see 2 registrations under device in the vpanel. Maybe it's a sip.voipwelcome.com thing; maybe the firmware; I don't know. It's not a big issue.

2) The VoipO servers are having a difficult time CALLING EACH OTHER. I.e. I have my beta line on Jupiter server and my Primary line on Central02 server. If I can FROM juptier to Central02, it rings my failover line. If I call FROM Central02 to the Jupiter, it goes to Voice Mail. This WAS an issue a time back. Maybe it is something that was never really addressed being it's not that common to talk to other voipo numbers; let alone one on a different server. I'm PRETTY SURE that if BOTH are on the same server; e.g. Beta and Primary both on Central02; then they can call each other. When I was using sip.voipwelcome.com on BOTH lines, it was fine. Again; not a problem.

Anyway; just wanted to say that things have been working fine on the grandstream and the current settings. Maybe it's the 1 minute registration. Maybe it's the downgraded firmware to .15. Maybe it's useing the central02 server. Maybe it's a combination. Tim and Justin know they can use my lines to experiment with if needed. Any time day time hours Mon-Fri. And we can work more together any night or on weekends. But current configuration is stable and a good bench mark for any one that needs the info. My BYOD (Beta line on Linksys) never had issues on any of the servers. Even when I moved my primary to it prior to fixing the grandstream issues. Great job Justin and Tim. You guys have a very high work ethic. As does all the voipo employees. Later... Mike.....