FWD gets unregistered after couple minutes

I have SPA-2002 with BroadVoice on Line 1. I am trying to set up FWD on line 2. I tried both FWD configuration guide and Voxilla wizard (FWD No NAT). Everything works OK; I can make a test call, and a toll-free call. However, after couple minutes Sipura info page shows "Unregistered" on Line 2, and there is no dial tone. Sipura Line 2 tab doesn't have any credential information any more - everything is erased.

Also, I tried to lower "Register expires" value from 3600 to 60 as somebody suggested - didn't make a difference.

Any idea why it happens? BroadVoice keeps working fine... I can re-run the wizard, and make couple more calls, and then it get erased again...

Thanks in advance

EDIT: Looks like I solved it... I changed the wrong setting - "Proxy Fallback Intvl:" instead of "Register expires". Once I lowered Register expires to 180 (it seems to lose registration after 4-5 minutes) - it stays put...

May I suggest that the wizard set this value to something like 180 - instead of 1800 that it does now...

Actually, I take the good news back :cry: While it sems to take a little bit longer with lower settings; FWD still unregisters after 10 minutes or so...

So, back to my original question -- any idea what can be causing it?

Thanks
Felix

Sometimes getting "unregistered" is a router and/or ISP issue.

For example, some ISPs (including my DSL service) will "time out" after a few minutes of not doing anything on the internet, and drop your connection. Now your router will likely immediately reconnect you when you next try to access the internet, but you may get a new (public) internet IP (address) when this happens. The problem here, is that the Sipura "registration" would be for the OLD (pre-disconnect) IP address, and therefor you will lose registration.

And sometimes it's your local networking equipment fighting you. For example, some routers will "times out" the specific connection (and close the "port" used by the registration), even if you don't time out the ISP itself (and get another IP address). The result is the same as far as the Sipura registration is concerned. Because you no longer have the open connection, you lose "registration".

Here are some Sipura settings that may help, no matter what the cause:

"NAT mapping enable: yes"
This tells the Sipura line to try to compensate for a NAT router (which most of us "home users" are behind).

"NAT keep alive enable: yes"
This setting tells the Sipura to send out a small packet every few seconds. Sometimes this can prevent the type of "timeouts" you may be experiencing.

"Register Expires: 300"
This causes the Sipura to try to reregister every 5 minutes (instead of the default of once/hour). While this doesn't prevent loss of registration, it does make it much less of a problem. Because if you do lose registration for any reason, you will have it back in a few minutes at most! And if it really takes 10 minutes of inactivity to lose registration (and the Sipura is setup to reregister every 5 minutes of inactivity), this may prevent the problem from occuring at all!

DracoFelix,

Thank you for your quick response

Both these settings are set to yes by Voxilla wizard.

I now realize that my original description was somewhat unclear (because I first thought that there is a problem; then - there isn't; then - there is again) - sorry.
I lowered "Register Expires:" value to 60. It does register several times, but after 4-5 minutes it stops. Not only the info page shows "Not registered" but all registration iformation on the Line 2 page is wiped out! So, I don't have it back in a few minutes.

As far as ISP or router problems... I don't have DSL or PPPoE - I don't think the cable modem times out.

And Line 1 (BroadVoice) doesn't have this problem...

I also noticed a strange problem. Since I set up Line 2 for FWD, the SPA web page doesn't load completely. It outputs all the data, but the progress bar get stuck and the flag (in IE) or circle (in FF) keeps going until I his Stop. Also, when SPA goes from registered to Not registered (after 4-5 minutes) it takes extra 10-15 seconds for SPA web server to respond. I don't know these are related or not...

Thanks, as always!

I think I figured out what is causing the problem. I still need advice as to how to handle it :roll:

If I turn off provisioning in Line 1 (BroadVoice line) - everything is OK. I noticed that every 5 minutes or so, the phone goes off-hook momentarily and after that Elapsed time gets reset, and my FWD line gets unregistered, etc... Apparently, if I turn provisioning off, BV doesn't send any updates to SPA, nothing gets reset, and my FWD is up and running.

I have two questions in this regard. First, while I understand that many experts here keep provisioning off, and keep an eye for various settings (proxy server seems to need constant care). I would prefer to let BV take care of these things, at least for now!

Second, and more important. If I switch to VoicePulse, and they lock the adapter - would I run into the same problem? That is, since with VoicePulse I can't turn provisioning off, my FWD settings will be wiped out every 5 minutes or so?

you may run into a prblem where they will downgrade the firmware to 1 line and FWD settings will disappear.
I think it is a risk on your part.
It would be nice is BV just managed the proxy since this is the only thing that needs changing because BV is screwing around with something that is not broken.