Printable View
I have been trying to log into my Vpanel and after I hit submit after my phone number and password, it never loads. Also, I have not received inbound calls for a few hours. I just realized it and opened a ticket. Have not rebooted the ATA yet. Outbound calls are fine. Calls to my number have a long delay and then voicemail. I'm glad I have email notifications turned on!
Also, I got no MWI on my ATA or my phones, no studder dial tone either.
Scott
For vPanel, have you tried going to /logout and the back? It sounds like maybe there's a session caught or something that that could clear out.
Reboot the ATA and it should be up. We've seen a few more reports of registrations dropping than normal lately (maybe due to growth) so we made a few changes today which hopefully should nip that before it starts growing into a bigger issue.
Basically we've adding more NAT keep-alive components, reduced the re-registration interval and will be rolling out a few more changes over the next few days.
Overall the combination of things should help virtually eliminate this ever happening.
I rebooted the ATA and everything started working again. On the Vpanel issue, when I hit the Login button it took probably 2-3 minutes before it let me in. After I was in, everything was very responsive. I am going to try now and see how it goes.
thanks for your help!
Regarding vPanel being slow/unresponsive:
It's possible that the system was taking backups at the time of your login - resulting in a bit of a delay.
I don't think there is much to worry about - appreciate the report though.
When you implement these new changes, could you please post them here and tell us what changes were made? Also, for those of us behind a router, do we need to reboot our ATA to get these new changes? Thanks!Quote:
Originally Posted by VOIPoTim
I do believe that behind a router we will always have to reboot. I had the registration drop as well and just realized it when i was calling home, and it was ringing on my failsafe device (cell phone). I looked in my vPanel and noticed that nothing was registered so I remoted into my PC at home and rebooted my ATA and that was all it took.Quote:
Originally Posted by dcshobby
I lost registration around 3pm. Had to reboot the adapter. Doesn't it try to register every 5 or 10 minutes?
I know PAP2 checks the provisioning file every 1 hour (depending on the interval set). I hope GS502 has something similar to that.
My line one lost registration this morning until I rebooted...then all was well.
I also lost registration and couldnt receive incoming calls but could make them just fine. rebooted the ATA and all seems to be working again.
I just got it again. Registration dumped. 2nd time today.
I'm showing 4 lines registered for my two on the HT502.
One is port 5062 and the other three are port 5079.
Mine was like that last week, actually maybe 2 weeks ago, except I had 6 :eek: lines registered.
My ATA lost registration as well. Calls going to failover. Happened sometime between 10 am and 8:30 pm. ATA is attached directly to cable modem. Never had this issue prior to recent firmware upgrade. Not sure if it's related or not...
A reboot of the ATA did NOT fix the problem.
I have had my 502 behind my router since day 1, before they enabled STUN and other NAT-Friendly settings. I never lost registration either until this latest firmware update.
Just to follow up. After waiting a little while then again rebooting my 502, it did re-register and is now showing in Devices on the vPanel.Quote:
Originally Posted by carlquist
Our guys are working on this this week and we hope to have it fully nailed down by the end of the week. Unfortunately, it seems to be related to firmware.
We're working on identifying exactly what the firmware issue is to see if it's something we can address without another firmware change. We'll likely make a decision tomorrow if we want to revert.
It's not affecting everyone, but does seem to be affecting enough people to potentially justify rolling it back to the old firmware to give us some time to work it out with Grandstream.
Is there anyone here who is experiencing this that is on the older firmware?
I use Asterisk 1.4.21.2 - usually in the night around 9 PM PST, a few times, the server takes a very long time to respond to register requests. Once it took around 20 seconds to respond, another time, 31 seconds. I have increased the registration timeouts on my server to 60 seconds to prevent my trunk from timing out. I am using central01. I have a ticket open on this - FJJ-815835.
Yes - just posted on DSLR as well before I noticed this post. Still on old firmware and lost registration yesterday, rebooted and all was well. Also lost registration this morning - can not reboot till I get home in a couple hours though.Quote:
Originally Posted by VOIPoTim
Came unregistered again twice since yesterday afternoon
Just found the last one about 5 minutes ago.
I just noticed this happened to me, as well. Slightly different behavior: Primary went to failover, virtual rang through??? Reboot seemed to fix for now.
Mine also became unregistered again sometime this morning.
I just turned up my SPA-2102 to see if anything happens..
Edit: Back to 502...SPA kept dropping registration..
I am also having the same problem. Noticed it yesterday and today. Still unregistered. Outgoing is fine, Incoming goes to failover. Going to reboot the HT502 now. My HT502 is behind router.
Is there anyone here who has experienced this who could help us test the fix tonight?
If so, let me know.
If you mean late tonight I can help out. I can begin testing around 11:30pm CST. I'm at work right now, otherwise I'd love to help.
I have some time tonight. What would be involved?
I have not been able to stay registered all day and currently not able to make outbound or receive inbound. Depending on what time you are looking for help testing I would be willing.Quote:
Originally Posted by VOIPoTim
Let me know what you want me to do. I can spare some time tonight.Quote:
Originally Posted by VOIPoTim
Tim....
Tell me what you need..
burris
I've PMed those of you that volunteered here.
Tim..
I reconfigured per your instructions and with preliminary testing, everything seems to work just fine.
I suppose only time will tell if the registration sticks.
Should I just leave it where it is so long as it keeps working?
Is it a capital B on FXS 2? I looked in my Vpanel and only see 1 line registered where I usually see two. Or will line 2 not show up now with a different username?
Capital B, yes.
I see both of yours on our end. The current user view filters anything different than the number so it just won't show it right now on your end.
Our team has been working on this all day and is continuing to work tonight. For those users affected (not all), the registration is dropped periodically. This is easily resolved by rebooting the ATA, but a daily reboot should NOT be needed.
At this point, it appears to be related to system changes we made to prepare for the firmware update that was rolled out a few days ago not working well with some usage patterns.
We've made changes which we feel will completely resolve this, but before we push them out systemwide, we're testing them.
If there is anyone here who has seen this issue that would like to help test the fix now, call our office at this number: 713-568-9800.
The main numbers will go to the closed recording, but this number is internal and will get through to us tonight.
Our team is continuing to work on this fix tonight. While everything with it is working well now, the more users that test it the more sure we can be of that.
One this is all situated, we'll be making an announcement and issuing service credits for the last few days.
It should be fine to leave, yes. We just didn't want to roll out these changes to primary servers until we knew for sure no new issues were being created.Quote:
Originally Posted by burris
I cannot get FXS2 to register at all. I've tried rebooting several times and nothing...
Also, outbound seems to be fine, but upon answering on an inbound call gets a fast busy and the calling party gets voicemail.
Make sure for it, you're setting to to central02.voipwelcome.com and changing the username to 1112223333B (with your own phone number).Quote:
Originally Posted by Vumes
2816172000 would go to 2816172000B on FSX2.
Yup, thats how it looks.Quote:
Originally Posted by VOIPoTim
What port is it set to? Maybe yours was changed by support? If so, change its sip port to 5060.Quote:
Originally Posted by Vumes