Check out http://forums.voipo.com/showthread.php?t=1180Quote:
Originally Posted by Vumes
Printable View
Check out http://forums.voipo.com/showthread.php?t=1180Quote:
Originally Posted by Vumes
Ahhh, got it. Thanks Tim.
FYI, one of my 2 lines just dropped offline. I realized this when only one of the phones rang, and checked vPanel to confirm. It was fine an hour or two ago.
A Grandstream?Quote:
Originally Posted by Brian
Yup.Quote:
Originally Posted by VOIPoTim
BTW, I have no desire to ditch the GS and switch to a PAP - I'd much rather stick with the issue and help get it fixed.
Just wanted to chime in that mine dropped as well. I read the thread in the announcement forum. Somehow I always seem to be in the 5% or whatever small number of users that is affected by these issues.
As usual, a reboot of my 502 corrected the problem.
My question is, why didn't it re-register by itself? And also why does the adapter always think it's registered when it obviously (as evidenced from the Devices vPanel page) is not?
They should be.Quote:
Originally Posted by carlquist
That's what we keep asking Grandstream and they don't have an answer for.
The PAP2Ts and Grandstream 286 (older models) re-register almost instantly.
When 502's don't re-register (not all the time), they have either an "Internal Server Error" or "Segmentation Fault" error.
Fair enough. I understand you can't write Grandstream's firmware for them.Quote:
Originally Posted by VOIPoTim
I'm not to this point yet. But are you guys willing to swap out my 502 for a PAP2T? If they aren't able to nail down the cause and correct it in the near future, I will probably get to the point where constantly "policing" my 502's registration status becomes too cumbersome.
Lost registration again today probably around 8.30pm. Had to reboot and get back to normal.
My 502 did not drop registration or if it did got up and running again by itself.
Mine is still outside the router, how about you "droppers" ?
As far as I know the ones that dropped were all behind a router.Quote:
Originally Posted by quattrohead
Mine was in front. I've since switched to the PAP2T that arrived today. So far so good.Quote:
Originally Posted by VOIPoTim
Yes, mine was behind router. I run too many apps, site-to-site vpn's and servers at home. I also use a cisco asa router and firewall. Having the ht 502 in front of my router caused a lot of issues with my other applications. It also did not allow the throughput of my asa. The ht 502 was clearly open to all traffic from voipo.Quote:
Originally Posted by VOIPoTim
So I believe it is truly a problem with the grandstream as Tim has been saying all along. Not anything with the Voipo network or servers.
Are the Pap2t devices set to re-register every 60 seconds like the ht 502's? It would seem that I might be missing incoming calls while the ht 502 is re-registering as it takes some time to re-register. I realize that outgoing calls may not need to be registered, but it seems like ultimately it would be less of a chance of missing calls, if my device is unavailable for 10-15 seconds each minute...But then again, maybe I don't quite get the way that works...
I got the email letting me know I had no devices registered. Thank you for the email. I am confused because I read the other thread about the issue earlier and confirmed my phone was still working so it became unregistered sometime after that. After the email I checked and sure enough it was not registered. A reboot did resolve the issue. I really think Grandstream is letting you down Tim.
As many of these things as you have and are going to be purchasing you would think they would be a little more helpful in resolving these problems. Seems clear to me at this point all the problems that you have had for the most part are the device and not the service.
Thanks again for the email!
Yeah, they're both re-registering. It shouldn't really affect the calling (even if you're on a call it's doing it).Quote:
Originally Posted by eagle 1
I got home and my daughter was on the phone (as usual) so I did not think anything was wrong. But then my failover line rang. I checked email and had one from VOIPo about an hour old, telling me my 502 was not registered. I checked vPanel and sure enough, still no devices registed. I booted my daughter off the phone and cycled power on the 502. All is well again in vPanel.
FYI, my 502 is not behind a router.
David
Just checked again and Vpanel is showing no devices registered again.
FYI:
I have attempted to use both the provisioned HT502 and PAP2T, but neither device provided the call quality and stability of my PAP2. Certainly, the PAP2T should be able to attain the same level of service if I were able to configure it (no admin access).
Both ports of the PAP2 are being served by central01.voipwelcome.com with FXS1 using port 5079 and FXS2 on port 5062. There is no port-forwarding or DMZ, STUN is not enabled and the registration expiration is set at 3600 seconds. I have had no loss-of-registration issues with these settings.
Ken
Edit: I can provide screen captures of my configuration pages if anyone desires them.
I just tried to call home and went straight to voicemail. I rebooted my HT502 last night to get it registered again, but it looks like it lost registration again.
Where are the "no devices registered" emails configured? I have not received one yesterday, or today. Was this a one time event, or monitoring we can set up?
Thanks,
Dan
I've never received the e-mail either.Quote:
Originally Posted by orum
For what its worth, my Phonepower supplied 502 has never shown a problem in over 6 months behind the router that I have had them.
What does this tell us ? Dunno.
quattrohead,
What is the firmware level of your Phonepower box?
Product Model: HT-502 V1.1B
Software Version: Program-- 1.0.1.21 Bootloader-- 1.0.0.9 Core-- 1.0.0.25 Base-- 1.0.0.76
System Up Time: 16:24:23 up 15 days
That is what my HT502 has on VOIPo typing *** 16Quote:
Originally Posted by quattrohead
Well, there goes logic out the window...the firmware are the same.
But, someone from VOIPo should be asking you to go into the admin pages on your Phonepower box and figure out what is different, and makes yours work.
I'm sure Tim has looked at this, but I think that every provider has a different system of handling their calls as well as registrations.Quote:
Originally Posted by abward
However, it may be a good idea if they haven't considered it.
They have the admin pages locked out with a password.
I had worked with them on a "noise" issue. They did a remote desktop session and then just terminated it when done leaving FF open ;) ....thought FF should have the password in the field so went back and told FF to remember it.
Unfortunately, it seemed to be wrong :confused:
Quote:
Originally Posted by abward
This was posted in its own thread, but bears repeating here:
One thing we've seen quite a bit recently is people reporting a loss of registration
Since the devices are re-registering every minute it seems like some people are looking in vPanel right within the 3 second or so window when it's happening.
If you think your device is no registered give it a minute or so to confirm before reporting it to make sure it's not just a case of perfect timing.
Just checked this morning. And I lost registration. I waited for 5 minutes before I did a reboot. There is no UDP traffic between the SIP server and ATA during that time. After the reboot I am back to normal.
I had lost registration sometime overnight or early this morning as well. I waited approx 3 mins before rebooting the 502. The devices page never indicated a registration within that time so I went ahead and rebooted. That corrected the problem.
Just for the record, I have both my PAP2T as well as my 502(2nd number) online.
I did just take a look at the VPanel for my 2nd line, and although the 502 shows as registered in the ATA, I had to do a manual reboot for it to really register.
Outbound of course, did work before I rebooted. Now it does shows in the panel.
The 502 is set for 1 minute registration and is pointed to the sip server..
The PAP2T sits there and purrs..not a problem.
After about 2 weeks of no probems, yesterday I started having registration problems again.
Once yesterday afternoon, once last night and once this morning.
Yesterday afternoon: 1 port showed as registered, calls went to failover.
last night: port 2 unregistered but still got calls on port 1.
this morning: same as last night.
in all 3 cases a reboot fixed the registrations.
Lost registration again last night/this morning...
Dan
My BYOD PAP2T has had no registration issues for a couple weeks now. I'm feeling better and better as each trouble free day passes.
Lost registration on one of my lines this AM (and I waited quite a while before I power cycled).
I'm unregistered again too. just checked
This is really getting to be a bit much. My ATA was registered and working yesterday morning when we left for the day and returned home this afternoon. I got a call from my Son on my wife's cell phone tellimg me his calls were going to my failover number again. When I checked VPanel, sure enough, the ATA was not registered. I'm opening a ticket to see what if anything can be done about this as it has been worse in the last few days. I really don't want to have to babysit my GrandStream all the time. Hoping we can get to the bottom of this.
RA
No need for a ticket right now, but can those of you that have lost it recently (or ever) please open a ticket if you do from here on out.
I don't want to get into details just yet, but I just made a rather big discovery.
I was just looking in system logs myself and noticed something pretty big standing out (at least to me). I may not know what it means fully, but I know keywords and when certain keywords and ERROR shouldn't be together. I had 2 of our admins look into it and sure enough they said it's an issue that should be fixed, but was overlooked all this time.
I think sometimes admins see errors and think "oh that's ok to ignore" since they know what it is and "know" that there are a lot of things that "shouldn't be an issue" but when I don't know what it is to the extent that I don't brush it off until someone explains to me why it says error "even if it doesn't matter" just so I know. With that being said, I noticed something that several other full-time sys admins did not and we think it could be the culprit.
We're looking into this more, but this little error could have been causing this entire mess.
Great. Thanks Tim. Your communication through this entire thing has been top notch.