PDA

View Full Version : Something stuck? No Vpanel or inbound calls



scott2020
01-26-2009, 11:13 PM
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

VOIPoTim
01-26-2009, 11:47 PM
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.

scott2020
01-27-2009, 08:23 AM
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!

VOIPoDylan
01-27-2009, 01:40 PM
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.

dcshobby
01-27-2009, 03:03 PM
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.

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!

Vumes
01-27-2009, 05:02 PM
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!

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.

sr98user
01-27-2009, 05:16 PM
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.

burris
01-27-2009, 05:46 PM
My line one lost registration this morning until I rebooted...then all was well.

dlangley
01-27-2009, 05:53 PM
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.

Vumes
01-27-2009, 07:41 PM
I just got it again. Registration dumped. 2nd time today.

usa2k
01-27-2009, 09:05 PM
I'm showing 4 lines registered for my two on the HT502.
One is port 5062 and the other three are port 5079.

Vumes
01-27-2009, 09:07 PM
Mine was like that last week, actually maybe 2 weeks ago, except I had 6 :eek: lines registered.

carlquist
01-27-2009, 09:27 PM
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.

scott2020
01-27-2009, 09:54 PM
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.

carlquist
01-27-2009, 09:57 PM
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.

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.

VOIPoTim
01-27-2009, 11:10 PM
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.

VOIPoTim
01-27-2009, 11:59 PM
Is there anyone here who is experiencing this that is on the older firmware?

zcnkac
01-28-2009, 12:00 AM
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.

buckethead
01-28-2009, 09:39 AM
Is there anyone here who is experiencing this that is on the older firmware?

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.

dlangley
01-28-2009, 10:25 AM
Came unregistered again twice since yesterday afternoon
Just found the last one about 5 minutes ago.

bretski
01-28-2009, 12:43 PM
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.

carlquist
01-28-2009, 01:18 PM
Mine also became unregistered again sometime this morning.

burris
01-28-2009, 01:37 PM
I just turned up my SPA-2102 to see if anything happens..

Edit: Back to 502...SPA kept dropping registration..

myvoip07
01-28-2009, 05:07 PM
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.

VOIPoTim
01-28-2009, 06:37 PM
Is there anyone here who has experienced this who could help us test the fix tonight?

If so, let me know.

Vumes
01-28-2009, 06:43 PM
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.

scott2020
01-28-2009, 06:44 PM
I have some time tonight. What would be involved?

buckethead
01-28-2009, 06:46 PM
Is there anyone here who has experienced this who could help us test the fix tonight?

If so, let me know.
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.

myvoip07
01-28-2009, 06:59 PM
Is there anyone here who has experienced this who could help us test the fix tonight?

If so, let me know.
Let me know what you want me to do. I can spare some time tonight.

burris
01-28-2009, 07:24 PM
Tim....

Tell me what you need..

burris

VOIPoTim
01-28-2009, 07:51 PM
I've PMed those of you that volunteered here.

burris
01-28-2009, 08:08 PM
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?

scott2020
01-28-2009, 08:13 PM
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?

VOIPoTim
01-28-2009, 08:17 PM
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.

VOIPoTim
01-28-2009, 08:21 PM
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.

VOIPoTim
01-28-2009, 08:21 PM
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?

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.

Vumes
01-28-2009, 08:30 PM
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.

VOIPoTim
01-28-2009, 08:35 PM
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).

2816172000 would go to 2816172000B on FSX2.

Vumes
01-28-2009, 08:36 PM
Make sure for it, you're setting to to central02.voipwelcome.com and changing the username to 1112223333B (with your own phone number).

2816172000 would go to 2816172000B on FSX2.

Yup, thats how it looks.

VOIPoTim
01-28-2009, 08:39 PM
Yup, thats how it looks.

What port is it set to? Maybe yours was changed by support? If so, change its sip port to 5060.

scott2020
01-28-2009, 08:40 PM
On some of my calls I am getting horrible static. I know it is digital, but it sounds like back in POTS days when water was in the line or a wire was loose. I just called my DID and I couldn't even make out the voice.

Edit: It happens on the ring-in, so when you call my DID you can hear the "static" even before someone answers.

Edit 2: It doesn't happen every time. Sometimes it is inbound and sometimes outbound. Kind of strange.

Vumes
01-28-2009, 08:41 PM
Local Sip port for FXS2 showed 5062. FXS1 shows 5079. Should I change them both?

VOIPoTim
01-28-2009, 08:45 PM
Local Sip port for FXS2 showed 5062. FXS1 shows 5079. Should I change them both?

Nope, they should be different ports for the different lines.

Try it now though, we just enabled both ports on our end so they should work.

burris
01-28-2009, 08:52 PM
My sip ports are

port1=5079

port2=5062

Been this way all along with no problems till yesterday's registration dropping out..

VOIPoTim
01-28-2009, 08:55 PM
So far so good. Anyone else wanting to help test this...here is the info:

----
1) Login to ATA with admin password. Temporary: Ajw5q1FexW8u8XuL

2) Disable provisioning temporarily by removing the Config Server Path under Advanced Settings.

3) Under FSX Port 1, change your server to central02.voipwelcome.com

4) Under FSX Port 2, change your server to central02.voipwelcome.com AND add a B to the end of your username/auth username. Example: 2816172000 would change to 2816172000B

5) Reboot and see if you can find any issues.


After Testing/Reverting to Normal:

If you need to revert, just re-enable provisioning by changing Config Server Path back to provision.dev.voipo.com and rebooting. It should reconfigure as it was before.
----

myvoip07
01-28-2009, 08:57 PM
My sip ports are

port1=5079

port2=5062

Been this way all along with no problems till yesterday's registration dropping out..
Those are the default Local sip port settings for HT502 provisioned by VoiPo. I got mined changed to the HT502 factory default per below

Port1=5060
Port2=5062

burris
01-28-2009, 08:59 PM
Those are the default Local sip port settings for HT502 provisioned by VoiPo. I got mined changed to the HT502 factory default per below

Port1=5060
Port2=5062

I've had my ports changed in the past and so long as they weren't the same, they worked

VOIPoTim
01-28-2009, 09:03 PM
What is everyone seeing so far?

There are dozens of you on it, so hopefully the bulk of you being quiet is a good thing :)

Vumes
01-28-2009, 09:04 PM
Tim, on FXS2 should my proxy server be central02 as well, or leave it as sip, or blank?

VOIPoTim
01-28-2009, 09:05 PM
Tim, on FXS2 should my proxy server be central02 as well, or leave it as sip, or blank?

Should be central02.

VOIPoBrandon
01-28-2009, 09:05 PM
Tim, on FXS2 should my proxy server be central02 as well, or leave it as sip, or blank?


central02.voipwelcome.com

ah Tim beat me to it :).
________
Geo/chevrolet tracker (http://www.chevy-wiki.com/wiki/Geo/Chevrolet_Tracker)

Vumes
01-28-2009, 09:18 PM
Ok, thats what I thought. I still have a no go. Want to take a look at my device? If it doesn't work out, i'll just revert back, but just wondering why it won't work out.

scott2020
01-28-2009, 09:19 PM
Everything looks OK except for the horrible static on my incoming calls. Maybe it is something with my DID or something.

VOIPoBrandon
01-28-2009, 09:23 PM
Ok, thats what I thought. I still have a no go. Want to take a look at my device? If it doesn't work out, i'll just revert back, but just wondering why it won't work out.

I saw both of your lines registered a second ago, any chance you have done some changes? Could you go ahead and power-cycle, the ATA while I'm grabbing a network trace on your account, thanks!

Vumes
01-28-2009, 09:27 PM
They were both registered because I reverted back and provisioned, then tried all over again. Power cycling now.

myvoip07
01-28-2009, 09:36 PM
My Incoming calls disconnect after 30 secs, Outgoing fine

buckethead
01-28-2009, 09:37 PM
After being able to get in and make the changes I seem to be staying connected now - System Up Time: 21:48:45 up 5 min - first time that has shown more than 0 all day. Incoming and outgoing calls seem to be working fine after a couple test calls.

VOIPoBrandon
01-28-2009, 09:44 PM
They were both registered because I reverted back and provisioned, then tried all over again. Power cycling now.

Odd, I was seeing them connected to the central02 server. Lets see how it goes this time.

Xponder1
01-28-2009, 09:52 PM
Correction I set mine as directed to test it and port 2 just gives me a fast busy. Both say they registered.

So how do we know when to change the provisioning back?

VOIPoBrandon
01-28-2009, 09:58 PM
Correction I set mine as directed to test it and port 2 just gives me a fast busy. Both say they registered.

So how do we know when to change the provisioning back?Could you PM me your phone number, if you want to check a few last settings to make sure it is alright, otherwise whenever you are ready to revert feel free.

Also, what action gives you fast busy? Incoming Call, outgoing Call? etc?
________
MONTANA MARIJUANA DISPENSARY (http://montana.dispensaries.org/)

Xponder1
01-28-2009, 10:01 PM
Sent. Port 1 I tested in and out both for 2 mins and they were fine.

Xponder1
01-28-2009, 10:05 PM
Could you PM me your phone number, if you want to check a few last settings to make sure it is alright, otherwise whenever you are ready to revert feel free.

Also, what action gives you fast busy? Incoming Call, outgoing Call? etc?

Outbound calls and inbound did not work to the second port.

I tested by calling my cell phone then using my wifes phone to call the house.

VOIPoTim
01-28-2009, 10:07 PM
Outbound calls and inbound did not work to the second port.

I tested by calling my cell phone then using my wifes phone to call the house.

Was port 2 set to central02 too?

Xponder1
01-28-2009, 10:11 PM
Was port 2 set to central02 too?

Yes I just checked and made sure.

scott2020
01-28-2009, 10:12 PM
I also get fast busy with outgoing calls on port 2.

EDIT: When I dial 11 digits it works. Dialing 7 digits on port 2 gives fast busy.

Xponder1
01-28-2009, 10:16 PM
I also get fast busy with outgoing calls on port 2.

EDIT: When I dial 11 digits it works. Dialing 7 digits on port 2 gives fast busy.

As Brandon requested I tried a 1 800 number and it had the same issue and I called my cell XXX -XXXX and it had the problem. After reading your comment I tried dialing my cell with the area code and it worked fine.

scott2020
01-28-2009, 10:18 PM
My static problem is pretty bad. I only can call from my cell phone. Other calls to other numbers from my cell are fine. It is static from the beginning of the ring in all the way to voicemail. Voicemail is all static as well. It is so loud I can't communicate. It seems to be only inbound calls right now. Also, my virtual number seems to be clear, so maybe it is something with my Level 3 DID here in MO.

Xponder1
01-28-2009, 10:24 PM
I noticed port one has nothing in the outbound proxy field but port two has sip.voipwelcome.com

Does that matter?

VOIPoTim
01-28-2009, 10:31 PM
I noticed port one has nothing in the outbound proxy field but port two has sip.voipwelcome.com

Does that matter?

Take out the sip.voipwelcome.com one.

Xponder1
01-28-2009, 10:38 PM
Take out the sip.voipwelcome.com one.

Removed and rebooted same issue.

VOIPoTim
01-28-2009, 10:40 PM
As Brandon requested I tried a 1 800 number and it had the same issue and I called my cell XXX -XXXX and it had the problem. After reading your comment I tried dialing my cell with the area code and it worked fine.

So this is only 7 digits and 800 number?

Is this only on line 2 and they work fine on line 1?

Xponder1
01-28-2009, 10:41 PM
So this is only 7 digits and 800 number?

Is this only on line 2 and they work fine on line 1?

100% correct. Line 1 is fine.

scott2020
01-28-2009, 10:52 PM
Same here. Port 1 I can dial 7 digits and the call works. Port 2 I cannot dial 7 digits but 11 digit dialing works.

VOIPoBrandon
01-28-2009, 10:52 PM
Alright guys, give the 7 digits a go -- and hold on the 800 numbers, due to the new registration on FXS2, we have to make some modifications to adjust. Please stand by.
________
Teen Vids (http://www.fucktube.com/categories/39/teen/videos/1)

scott2020
01-28-2009, 10:54 PM
7 digits worked for me just now on port 2.

Xponder1
01-28-2009, 10:57 PM
Alright guys, give the 7 digits a go -- and hold on the 800 numbers, due to the new registration on FXS2, we have to make some modifications to adjust. Please stand by.

I tested and it worked fine. I did not read this until after I sent you the private message but I did test the 800 number you provided me and it worked fine.

Incoming and outgoing are both working.

VOIPoTim
01-28-2009, 11:06 PM
Anything else anyone finding?

Xponder1
01-28-2009, 11:12 PM
Anything else anyone finding?

Tried some more numbers including another 800# and all seem fine.

VOIPoTim
01-28-2009, 11:20 PM
One more thing for you guys testing this...

Set "Unregister On Reboot" to Yes for both lines.

Xponder1
01-28-2009, 11:30 PM
One more thing for you guys testing this...

Set "Unregister On Reboot" to Yes for both lines.

Done and tested to confirm still working fine. ;)

Vumes
01-28-2009, 11:49 PM
Brandon, figure anything out about mine at all?

Xponder1
01-28-2009, 11:54 PM
Brandon, figure anything out about mine at all?

Just curious what happens with yours?

Vumes
01-28-2009, 11:56 PM
Just curious what happens with yours?

FXS2 won't register no matter what I do. Also, on inbound calls, even though FXS1 is registered, I get a fast busy when I answer the Voipo phone, and the calling party goes to Voicemail.

Xponder1
01-29-2009, 12:05 AM
FXS2 won't register no matter what I do. Also, on inbound calls, even though FXS1 is registered, I get a fast busy when I answer the Voipo phone, and the calling party goes to Voicemail.

Ok and you have it set like this? ( XXXXXXXXXX = your number)

Port 1
SIP User ID: XXXXXXXXXX
Authenticate ID: XXXXXXXXXX

Port 2
SIP User ID: XXXXXXXXXXB
Authenticate ID: XXXXXXXXXXB

On both
Outbound proxy on both ports blank.
Unregister on reboot : Yes
Primary SIP server: central02.voipwelcome.com

And under advanced page
Config Server Path : blank

?

When I did it I went a page at a time and it would say the changes will take affect after reboot but then I just went to the next page. When I changed it all I then hit the reboot button.

They also had me check and make sure my dial plan matched on both. My dial plan shows the following.
{ *12 | *400 | [2-9]xxxxxxxxx | 1[2-9]xx[2-9]xxxxxx | 011[2-9]x. | [49]11 | [x*]+ }

Vumes
01-29-2009, 12:07 AM
All but the outbound proxy on port 2. It is also central02.voipwelcome.com

VOIPoTim
01-29-2009, 12:07 AM
FXS2 won't register no matter what I do. Also, on inbound calls, even though FXS1 is registered, I get a fast busy when I answer the Voipo phone, and the calling party goes to Voicemail.

Is the STUN setting enabled on Line 1, but not Line 2? If so, try enabling it on both.

Make sure both ports have the "Unregister on Reboot" option set to yes.

Xponder1
01-29-2009, 12:08 AM
All but the outbound proxy on port 2. It is also central02.voipwelcome.com

proxy needs to be empty they say

Vumes
01-29-2009, 12:10 AM
Is the STUN setting enabled on Line 1, but not Line 2? If so, try enabling it on both.

Make sure both ports have the "Unregister on Reboot" option set to yes.

Tim,

Stun is set to YES on both and so it Unregister on Reboot. I am removing the outbound proxy now to see if that makes a difference.

Xponder1
01-29-2009, 12:11 AM
Is the STUN setting enabled on Line 1, but not Line 2? If so, try enabling it on both.

Make sure both ports have the "Unregister on Reboot" option set to yes.

On the advanced page my stun server shows 74.52.58.50
You could check that too.

Vumes
01-29-2009, 12:16 AM
On the advanced page my stun server shows 74.52.58.50
You could check that too.

Thanks Xponder, mine also shows the same. I removed the outbound proxy and that fixed the fast busy signal. So I can make and receive calls without a problem it seems, but Port 2 still will not register.

Xponder1
01-29-2009, 12:17 AM
Thanks Xponder, mine also shows the same. I removed the outbound proxy and that fixed the fast busy signal. So I can make and receive calls without a problem it seems, but Port 2 still will not register.

Not trying to insult you just trying to help at the top does it say active = yes?

Vumes
01-29-2009, 12:18 AM
Ok, I spoke too soon. I can receive calls IF i don't let it ring more than one time. After that, I answer and get a fast busy still.

Xponder1
01-29-2009, 12:20 AM
Ok, I spoke too soon. I can receive calls IF i don't let it ring more than one time. After that, I answer and get a fast busy still.

I just tested mine and let it ring a few times then answered and it was ok.

Vumes
01-29-2009, 12:21 AM
Not trying to insult you just trying to help at the top does it say active = yes?

;) No problem, and yes both of them say YES to active.

Xponder1
01-29-2009, 12:26 AM
;) No problem, and yes both of them say YES to active.

Tim is it possible that a Vpanel setting could have anything to do with the problems described?

Just throwing out random ideas. I find it weird mine works flawless and he is having a problem with it unless Brandon changed something on the VOIPo side that I do not know about that only affected me (or maybe did not affect him as intended).

Vumes
01-29-2009, 12:29 AM
Xponder, is your ATA in front or behind your router? Mine sits behind the router forcefully. So just throwing something out there to see if that could be a reason. Prior to this unregistering problem that started the other day, everything was going well.

Xponder1
01-29-2009, 12:29 AM
;) No problem, and yes both of them say YES to active.

User ID is phone number: NO
SIP Registration: Yes

on both?

Vumes
01-29-2009, 12:30 AM
User ID is phone number: NO
SIP Registration: Yes

on both?

Both look just like that.

Xponder1
01-29-2009, 12:31 AM
Xponder, is your ATA in front or behind your router? Mine sits behind the router forcefully. So just throwing something out there to see if that could be a reason. Prior to this unregistering problem that started the other day, everything was going well.

Behind my router. Linksys WRT54GS V6 running DD-WRT with the ports forwarded to the device as per the paper that came with it. 5060 5079 90 5004
Have you tried to DMZ your ATA?

Oh, and is yours set to a static ip address? I use my router to force mine to use the same ip when it gets its DHCP info.

Vumes
01-29-2009, 12:32 AM
Yes, mine looks the same. Different router, but I had no problems with this ATA prior to this registration issue.

Vumes
01-29-2009, 12:33 AM
I guess I can just roll it back to how it was, I'm just really curious to what is going on. :cool:

Xponder1
01-29-2009, 12:35 AM
Yes, mine looks the same. Different router, but I had no problems with this ATA prior to this registration issue.

I am convinced your problem is on their side. Has Brandon messaged you?

Vumes
01-29-2009, 12:35 AM
No, maybe he's sleeping like a normal human being. :p

Xponder1
01-29-2009, 12:36 AM
No, maybe he's sleeping like a normal human being. :p

Dunno his last post was "please stand by" lol :p

Vumes
01-29-2009, 12:38 AM
"Please stand by till morning. Thank you" LOL he he he.

Xponder1
01-29-2009, 12:38 AM
"Please stand by till morning. Thank you" LOL he he he.

He is going to have a neck ache from falling asleep on his desk....

Vumes
01-29-2009, 12:40 AM
Maybe his forehead is hitting the "Do not Register Second Line for Vumes" button.

VOIPoTim
01-29-2009, 12:42 AM
I guess I can just roll it back to how it was, I'm just really curious to what is going on. :cool:

Yeah go ahead and switch back for now.

We're going to call it a night and resume this in the morning to give things time to sit overnight. For those of you testing, it would be great if you could leave it overnight, it should be fine.

This way we can see how it holds up overnight and we can push it out during the day when more staff is available for support issues that could come up.

Here is an update:

--

At this point we've pushed out one update network-wide that should resolve this for most users that were experiencing it.

We also have many of you testing on a switch with the final fix on it. We're going to make sure no issues come up with that overnight and then roll that out tomorrow. At that point we anticipate the users experiencing this will see it completely disappear.

Tomorrow we'll make an announcement about it and explain what caused it and what was happening. We'll also be issuing some service credits when the dust settles for affected users.

We apologize for an inconvenience and want to especially thank the huge number of you that volunteered to help test the fix implemented tonight.
to forum ·
--

Vumes
01-29-2009, 12:43 AM
Back to the matter at hand, my local sip port on FXS1 is 5079 and local RTP port is 5004. FXS2 local sip port is 5062 and local RTP port is 5012. Yours the same?

Sounds good. Thanks Tim for the update.

Xponder1
01-29-2009, 12:45 AM
Yeah go ahead and switch back for now.

We're going to call it a night and resume this in the morning to give things time to sit overnight. For those of you testing, it would be great if you could leave it overnight, it should be fine.

This way we can see how it holds up overnight and we can push it out during the day when more staff is available for support issues that could come up.

Here is an update:

--

At this point we've pushed out one update network-wide that should resolve this for most users that were experiencing it.

We also have many of you testing on a switch with the final fix on it. We're going to make sure no issues come up with that overnight and then roll that out tomorrow. At that point we anticipate the users experiencing this will see it completely disappear.

Tomorrow we'll make an announcement about it and explain what caused it and what was happening. We'll also be issuing some service credits when the dust settles for affected users.

We apologize for an inconvenience and want to especially thank the huge number of you that volunteered to help test the fix implemented tonight.
to forum ·
--

Anytime. I love to mess with things. Thanks for the hard work!

Xponder1
01-29-2009, 12:46 AM
Back to the matter at hand, my local sip port on FXS1 is 5079 and local RTP port is 5004. FXS2 local sip port is 5062 and local RTP port is 5012. Yours the same?

Sounds good. Thanks Tim for the update.

Ya mine is the same on both.

Vumes
01-29-2009, 12:48 AM
Ah well, thanks for the tips. I will revert back for now and hopefully it stays registered for now. I'm patient, so no biggie.

Xponder1
01-29-2009, 12:49 AM
Ah well, thanks for the tips. I will revert back for now and hopefully it stays registered for now. I'm patient, so no biggie.

I bet they fix it for you in the morning after a huge cup of coffee.

Vumes
01-29-2009, 12:50 AM
Buenas noches everyone.

Vumes
01-29-2009, 01:04 AM
Tim, I tried to revert back by adding provision.dev.voipo.com to the Config Server Path and I hit update, then reboot, and it did not revert. It did stay, but did not go back to sip so I am trying it manually. Just thought you should know. This can wait till morning, so no worries.

Vumes
01-29-2009, 01:22 AM
Update::: Don't know if this is normal, but I reverted back, and everything works as it should, but I just looked up and the lights on Line 1 and Line 2 are both blinking together. It's been going on now for about 10 minutes. I made a call and received a call and it works fine, but the lights are blinking.... Anything related to this ongoing problem?

burris
01-29-2009, 06:37 AM
Morning Update..

Good Morning, VOIPo....Bet you all had a rough night.

This is a summary of my experience..

I have the 502 and it sits behind a wireless router. Never a problem until the one time it unregistered. Upon reboot, it was ok. I did try my SPA-2102 to see what happens, but although it worked on all functions, it did drop registration from time to time. Haven't tried it on Central02.

Last night I went with the test bed settings. Turned right up and I left it overnight. Still fine this morning.

The only settings I changed were those specified..the rest were as they were after the clone provisioning update a few weeks ago.

What I have now is....

STUN=disabled
Central02 on Sip and OB Proxy
Phone no. in port 1 both in sip user and authenticate
Phone no. +B in port 2 both in sip user and authenticate
Port 1 DNS mode=SRV
Port 2 DNS mode=NAPTR/SRV
Port 1=unreg on reboot=yes
Port 2=unreg on reboot=no

These settings, with the exception of the server selection and +B on line 2 phone number were all the same as it had and was working since inception.

I will leave it on Central02 until you indicate I should switch back to sip.

Thanks to all of you for some really hard work troubleshooting and support all through the night..

KenH
01-29-2009, 06:48 AM
Good morning,

Here's the situation at 7:45 AM EST:

HT502 CPL shows both ports registered.

vPanel: You do not currently have any devices registered to our servers!

FXS1:
Outbound: call completed OK
Inbound: Failover

FXS2:
Outbound: call completed OK
Inbound: Failover

Edit:
Power-cycled the HT502 and vPanel shows one registration. Incoming call on both ports working.

Edit:
Unregister on reboot:
FXS1: Yes
FXS2: No

Edit 09:43 EST:
vPanel now showing three devices, all with identical data (port numbers, expiration time, etc.)

Ken

burris
01-29-2009, 07:16 AM
The previous thread reminded me to take a look in the VPanel, even though everything is working well..

Tim mentioned that the +B line would not show up in the VPanel, however this is what I see at the moment...I'm still on Central02..

305xxxxxx sip:305xxxxxx@192.168.1.6:5079 2009-01-29 14:01:39 Grandstream HT-502 V1.1B 1.0.1.21
305xxxxxx sip:305xxxxxx@192.168.1.6:5079 2009-01-29 14:01:39 Grandstream HT-502 V1.1B 1.0.1.21

edit: I just did notice that the call history stopped recording at about 6:03 pm last night. I would guess that this was due to the server change.
Certainly not anything important for the moment.

fisamo
01-29-2009, 09:01 AM
Update::: Don't know if this is normal, but I reverted back, and everything works as it should, but I just looked up and the lights on Line 1 and Line 2 are both blinking together. It's been going on now for about 10 minutes. I made a call and received a call and it works fine, but the lights are blinking.... Anything related to this ongoing problem?

Is that what the device does during a f/w update? (Even if so, not sure why it would have gone on for so long...)

scott2020
01-29-2009, 09:08 AM
I have 4 devices showing up in Vpanel right now. Things seem to be working fine, but I thought it was a little strange.

KenH
01-29-2009, 09:15 AM
vPanel reverted to:

You do not currently have any devices registered to our servers!

bretski
01-29-2009, 09:31 AM
Sorry I missed this thread last night, otherwise I would have gladly helped with the testing. FWIW, I'm running ok as of a few minutes ago, after having to reboot a couple of times yesterday...

VOIPoTim
01-29-2009, 09:58 AM
Edit 09:43 EST:
vPanel now showing three devices, all with identical data (port numbers, expiration time, etc.)

Ken

This is good. I bet enabling Unregister on boot would take care of this. When it shows 3 lines, that's typically what it needed.

dswartz
01-29-2009, 09:59 AM
I've had the same IP/port showing as a registered device on more than one occasion, although it is now only one, and I've never noticed anything acting wrong or strange when it was more than one.

KenH
01-29-2009, 10:02 AM
This is good. I bet enabling Unregister on boot would take care of this. When it shows 3 lines, that's typically what it needed.

Tim:

Didn't make any changes to configuration, rebooted, and vPanel only showing one device now. Should I change the Unregister on Reboot setting?

Ken

burris
01-29-2009, 10:06 AM
Tim..

Should we consider going back to the sip server, even though all seems to be ok?



I was out for a while and tried to call home..Wife said that although both phones rang, line one got an immediate busy when answered, but if line 2 answered, it worked fine.
I got back and rebooted and seems to work now.

VOIPoBrandon
01-29-2009, 10:45 AM
Tim..

Should we consider going back to the sip server, even though all seems to be ok?



I was out for a while and tried to call home..Wife said that although both phones rang, line one got an immediate busy when answered, but if line 2 answered, it worked fine.
I got back and rebooted and seems to work now.

Burris, did you happen to have unregister on reboot enabled for both FXS1 and FXS2?

Xponder1
01-29-2009, 10:51 AM
Morning update. I still have my device configured as it was last night. Both incoming and outgoing calls are working fine. Vpanel shows only one device listed but someone just mentioned that at this time that is normal. I also noticed Vpanel is not logging calls but that does not surprise me.

Looks good.

Xponder1
01-29-2009, 10:53 AM
Update::: Don't know if this is normal, but I reverted back, and everything works as it should, but I just looked up and the lights on Line 1 and Line 2 are both blinking together. It's been going on now for about 10 minutes. I made a call and received a call and it works fine, but the lights are blinking.... Anything related to this ongoing problem?

Are you sure you do not have voice mail? That would make both lights blink.

burris
01-29-2009, 10:53 AM
Burris, did you happen to have unregister on reboot enabled for both FXS1 and FXS2?

Brandon....

If you remember, when we turned up the clone feature, you specifically mentioned to have one of the 2 lines set to yes and the other to no.
I've had it this way all along, and until the problem a few days ago, everything worked perfectly.

As I mentioned, I'm still on Central02 and when I called home before, one of the 2 lines was set yes and one to no. I set both to yes and seems to be working ok.

VOIPoTim
01-29-2009, 10:55 AM
Morning update. I still have my device configured as it was last night. Both incoming and outgoing calls are working fine. Vpanel shows only one device listed but someone just mentioned that at this time that is normal. I also noticed Vpanel is not logging calls but that does not surprise me.

Looks good.

One we enable the call logs for central02, it'll be fine. Just a display/permissions change.

scott2020
01-29-2009, 12:11 PM
Right now my ATA information page says "NOT REGISTERED" and I go directly to voicemail. I am running the test config.

KenH
01-29-2009, 12:19 PM
1:18 PM EST

HT502: Neither port registered and vPanel: No devices registered

Still in test configuration.

scott2020
01-29-2009, 12:47 PM
My status shows registered again now. Maybe an intermittent problem or something on the new server? At least the ATA re-registered itself but my inbound calls were still down 15-30 minutes or so.

Vumes
01-29-2009, 01:17 PM
Are you sure you do not have voice mail? That would make both lights blink.

You learn something new everyday. I do indeed have voicemail. I deleted them and the lights went off. Sheesh. Thanks.

VOIPoTim
01-29-2009, 01:23 PM
I think Ken and Scott just helped us discover something very key here that's been completely overlooked.

More testing to confirm then we'll post. Thank You! :)

scott2020
01-29-2009, 01:39 PM
Sweet! Glad to hear!

KenH
01-29-2009, 01:58 PM
2:56 PM EST

HT502: FXS1 Registered, FXS2: Not Registered
vPanel: No devices registered

Should I reboot?

Edit:
3:26 PM - Rebooted. HT502: Both ports registered. VPanel: one registered device.

VOIPoTim
01-29-2009, 02:29 PM
2:56 PM EST

HT502: FXS1 Registered, FXS2: Not Registered
vPanel: No devices registered

Should I reboot?

Yes. I believe this will be the last time.

VOIPoTim
01-29-2009, 02:49 PM
Has anyone else notice a drop this afternoon since I posted that it's fixed?

KenH
01-29-2009, 02:51 PM
Tim,

At this time, should we retain the test settings or revert to normal configuration?

Ken

VOIPoTim
01-29-2009, 02:54 PM
Tim,

At this time, should we retain the test settings or revert to normal configuration?

Ken

Ken,

Right now to be honest it shouldn't matter. It appears the issue was completely unrelated.

KenH
01-29-2009, 03:06 PM
Returned HT502 to normal configuration. vPanel and HT502 CPL show both ports registered. I notice that now, NAT is shown as Symmetric, rather than Full Cone.
Incoming & outgoing calls are OK.

buckethead
01-29-2009, 03:26 PM
Update from me - I have not made any changes since the initial changes last night which did not involve making it unregistered and I am still up and working. No issues so I have not touched any settings today.

Forgot to add - vPanel has only shown one device registered the whole time. I do not have a 2nd phone hooked into FX2 so have not tested or anything there.

dcshobby
01-29-2009, 05:57 PM
Ken,

Right now to be honest it shouldn't matter. It appears the issue was completely unrelated.

Can you start a brand new thread tonight with something to the tune of "Network Problems Fixed" so everyone can find it right away and maybe make it a sticky? Hope the problem is fixed for good and hope there was a good explanation for it too. Thanks!

burris
01-29-2009, 06:42 PM
Although all seems to be working well and I am still on Central02, the VPanel devices still show only one instance. Call records are up to date.

Since it is working, it really doesn't matter except to make you aware of it.
Maybe because line 2 still has a B after the number?

quattrohead
01-29-2009, 07:55 PM
I did not partake in any of this testing, but I do have the 502 registered 3 times in the CP !!!
502 is currently outside the router but I would like to move it back in sometime.

Xponder1
01-29-2009, 09:08 PM
Update 9:02 PM CST. Still setup with test configuration. Outbound calls using 7 digits on port 2 go to a busy signal again. Inbound calls work on both ports. Add the area code and the call goes threw. Have not tested a 800 number. Brandon had this fixed last night did something change?

I will reboot my ATA and try again in a little while.

VOIPoTim
01-29-2009, 09:10 PM
Update 9:02 PM CST. Still setup with test configuration. Outbound calls using 7 digits on port 2 go to a busy signal again. Inbound calls work on both ports. Add the area code and the call goes threw. Have not tested a 800 number. Brandon had this fixed last night did something change?

I will reboot my ATA and try again in a little while.

Everyone should be able to revert to the normal configuration without issues now as well.

Xponder1
01-29-2009, 09:36 PM
Everyone should be able to revert to the normal configuration without issues now as well.

Ok I will say that when I rebooted it had the same issue. I will go ahead and revert as requested.

Xponder1
01-29-2009, 10:23 PM
I reverted back and logged in and took a look at the settings and it shows a outbound proxy (sip.voipwelcome.com) on port #2 and not on port #1 and port number 2 unregister on reboot is set to no. Port 1 is set to yes.

Phone is working fine on both ports.

KenH
01-30-2009, 05:10 AM
I reverted back and logged in and took a look at the settings and it shows a outbound proxy (sip.voipwelcome.com) on port #2 and not on port #1 and port number 2 unregister on reboot is set to no. Port 1 is set to yes.

I see the same configuration on my HT502.

VOIPoTim
01-30-2009, 10:07 AM
I see the same configuration on my HT502.

Everything is working for you though right?

KenH
01-30-2009, 10:42 AM
Everything is working for you though right?

Yes, everything seems to be OK this morning.

I would like to know what the proper settings for those items is, though.

Ken

Xponder1
01-30-2009, 11:07 AM
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
01-30-2009, 12:25 PM
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

orum
01-30-2009, 12:26 PM
This did make me think of a feature request...

I don't need an SMS for every call/voicemail, but it would be great to have an option to send an SMS if Failover (either to voicemail or another number) is "triggered".

Dan

christcorp
01-30-2009, 12:36 PM
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
01-30-2009, 12:37 PM
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
01-30-2009, 01:53 PM
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
01-30-2009, 02:00 PM
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
01-30-2009, 02:07 PM
I've ONLY used sip.voipowelcome.com for my PRIMARY LINE. I've ONLY used jupiter for the beta line. later... mike....

sr98user
01-30-2009, 04:04 PM
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.

bretski
01-31-2009, 04:13 PM
I dropped again today. Noticed it when outbound calls would not complete. Looked at vPanel, no devices registered. Power-cycled, and it came back up. :(

VOIPoTim
01-31-2009, 04:25 PM
I dropped again today. Noticed it when outbound calls would not complete. Looked at vPanel, no devices registered. Power-cycled, and it came back up. :(

Open a ticket and we can make a change to your account that will likely fix for you.

The big issue is resolved, but there have been a few cases with specific users where we needed to apply a change.

christcorp
01-31-2009, 04:36 PM
I wanted to wait a day or two to make sure. So far; everything seems to be back to normal. Working good. I am going to let it rock and roll for a couple of days, then experiment again with my network settings to see if there are changes. But so far, so good. later... mike....

VOIPoTim
01-31-2009, 04:37 PM
To elaborate on what I'm saying with some isolated issues....

Some devices are apparently still sending the Line 2 registration before Line 1 which is canceling Line 1 out when it periodically re-registers. We're going to go ahead and roll out the new 2 Line method this weekend, but can make that change now for anyone having issues.

With the new clone line setup, the 2nd line will be using separate SIP credentials and registering independently so the two can never affect each other. That way even if for some odd reason, the ATA sends both at the same time or out of order, it won't matter. The old firmware consistently sent them in order...the new seems to only do that sometimes.

We've only seen a few reports of this so far and from logs it's not affecting many, but like I said we're going to roll out the new 2 line method anyway to prevent it for those it is affecting (and just not reporting it).

buckethead
01-31-2009, 05:33 PM
I am still running on the "test" set up from the other night with nothing in provision path and on central02 for both lines with B in the 2nd. I had some audio problems yesterday and opened a ticket. Through the ticket was asked to put back in provisioning server so it could grab a new sip server to see if that would resolve audio issues. As soon as I entered back in provisioning server and rebooted my device would not hold registration just like the other day - also it would not even grab new firmware as I am still on .8.

In order to keep my service up and going I put back in the "test" test up from the other night and I am now good to go. Audio issues seemed to clear itself up as wife has been on the phone a times tonight with no problems or complaints.

Assuming at some point I am going to need to do something to get up to .21 firmware and correct configuration?

bretski
02-02-2009, 02:04 PM
Open a ticket and we can make a change to your account that will likely fix for you.

The big issue is resolved, but there have been a few cases with specific users where we needed to apply a change.

Dropped again, even after the fix. Only one device showing up in vPanel. Was ok earlier today...

VOIPoTim
02-02-2009, 02:25 PM
Dropped again, even after the fix. Only one device showing up in vPanel. Was ok earlier today...

Was it around this time?

http://forums.voipo.com/showthread.php?goto=newpost&t=1105

bretski
02-02-2009, 02:27 PM
^ Uncertain. I did see that post (after I posted), but a reboot did not help. Still can't make outbound calls. On with support now.

Edit:
Something was screwy with routing, apparently. Support could not see my device, even though it is connected directly to modem. After placing a local (7 digit) call, it started working again for 10 digit calls. All of this was on phone1, phone2 worked ok throughout. Bizarre...

christcorp
02-02-2009, 04:33 PM
FWIW; I received a call from my wife (She was at home); at 1:15pm MST. I didn't think anything of it. I called her back at 3:20pm and it didn't ring in and I got my simul/failover connection. (Thank VoipO for failover and simul ring). But that made me wonder. I got on my blackberry and telnet into my adapter and did a reboot. (Forgot to look first if port 1 was registered or not). Anyway; after the reboot, all seemed well again. Later... Mike....

KenH
02-03-2009, 04:15 AM
My provisioned HT502 ATA shows unregistered again on vPanel, while showing registered on its CPL. This occurred overnight. Rebooting the ATA corrected the problem. I will submit a ticket.

I am losing my patience with what, I was led to believe, was a fully tested and stable service. I have spent too much time & effort trying to make this work (and I wanted it to!).

carlquist
02-03-2009, 06:50 AM
I can confirm that my 502 also became unregistered on the vPanel overnight. VPanel shows no devices registered yet the 502 thinks it is registered. Also, when calling my number it did NOT go to my failover. It rang once then a few secs of silence then a female recorded voice said "Bye" and I was disconnected.

My 502 is connected directly to cable modem.

A reboot of the 502 did fix the problem.