No devices registered in Vpanel

Quote:

---

Originally Posted by Montano

My PAP2T was also down this morning. A reboot, and change of servers got it working again. It seems every time I get comfortable and change from central02 back to sip, I wake up to a non-registered TA. When I left it on central02, it remained registered.

---

Same here...not a single problem on Central02...I kept thinking I should go back to Sip, but Tim said that Central was in full service and it wasn't necessary. In fact , provisioning keeps me on central.
If nothing changes, I'm fine..

Quote:

---

Originally Posted by Montano

My PAP2T was also down this morning. A reboot, and change of servers got it working again. It seems every time I get comfortable and change from central02 back to sip, I wake up to a non-registered TA. When I left it on central02, it remained registered.

---

Since it was BYOD, you may need to manually apply one of the fixes that was pushed out through provisioning. Set the re-registration interval to 1 minute.

Xponder1 and Eagle 1, did you reboot after the outage Friday or did you let the devices come back up on their own?

Can both of you PM me your ticket numbers so I can keep up?

Quote:

---

Originally Posted by burris

Same here...not a single problem on Central02...I kept thinking I should go back to Sip, but Tim said that Central was in full service and it wasn't necessary. In fact , provisioning keeps me on central.
If nothing changes, I'm fine..

---

Burris, were you down this morning or just mean you've had better luck with central02?

So far, we've had 2 registration tickets today (so I'm hoping they were from the two who posted here).

With 1 of them, it showed the ATA had not been provisioned since the 5th, so in that case you probably didn't get the fixed applied.

With the other provisioning wasn't enabled at all for some reason (we didn't have their MAC in the system), so they didn't get the fix.

Quote:

---

Originally Posted by VOIPoTim

Burris, were you down this morning or just mean you've had better luck with central02?

---

I have no problems..If you remember a while back, I thought that central was a temp server and wanted to change back to sip..You said not to bother as central was fully up and running. I mentioned that provisioning is keeping me on central and all is well.

Thanks

Quote:

---

Originally Posted by burris

I have no problems..If you remember a while back, I thought that central was a temp server and wanted to change back to sip..You said not to bother as central was fully up and running. I mentioned that provisioning is keeping me on central and all is well.

Thanks

---

While Im on byod at the present time till I get this project done... Central01 has been rock solid for me. The outage Friday morning did show up in the logs but other than that... Audio sounds as good as my qwest line ever did.

edit- to "Friday"
:)

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

Quote:

---

Originally Posted by 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

---

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.

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