Calls Still Going Straight To Voicemail

[andysiddell]

I see that an announcement was posted on the 29th January stating that there was a voicemail issue. Well my calls are still going straight to voicemail. If I reboot everything it works again for a few minutes and then all calls go back to voicemail.

http://status.fongo.com shows Voicemail - We are investigating possible service issues with voicemail. - 2013-01-30 11:37 but this was 2 days ago and no updates since.

Is anyone else experiencing this issue? I'm in Bellville ON.

Thanks

[FONGO_mike]

What is our timeout set to in your ATA?

[andysiddell]

Hi Mike,

the timeout is set to 30 seconds.

[Tenacious]

Yes my calls are going straight in to VM as well since yesterday.

[andysiddell]

It looks like YET ANOTHER issue with this platform. It's getting beyond a joke now.

[FONGO_steve]

Hi Mike,

the timeout is set to 30 seconds.

You'll want to set the registration timeout to 3600 seconds. Really aggressive timeouts like 30 seconds or less, where devices are registering several times a minute or more, will result in a short block of that IP to prevent abuse. If your set to 30 seconds then that's most likely the case here.

[senos]

Calgary: my calls are going straight in to VM as well since yesterday.

[Tenacious]

Changing to 3600 worked for me. Up again at least for now. Thank you!

[tbrummell]

You'll want to set the registration timeout to 3600 seconds. Really aggressive timeouts like 30 seconds or less, where devices are registering several times a minute or more, will result in a short block of that IP to prevent abuse. If your set to 30 seconds then that's most likely the case here.

Aggressive re-registration times = abuse? WOW! How does every other provider support reg time of 60 seconds then?

[FONGO_mike]

Calgary: my calls are going straight in to VM as well since yesterday.

As we suggested, please set your timeout to 3600

[hete]

In asterisk we have 3 different timeout value :


Registrations? (registertimeout:20) (registerattempts~)
Registration Times? (minexpiry:60) (maxexpiry:3600) (defaultexpiry:120)

[FONGO_mike]

Have you tried and reset and reconfiguring your set-up?

[hete]

Have you tried and reset and reconfiguring your set-up?

More then that, i build a new asterix machine ! Same prob

and :

YOUR SIP STATUS
SIP Status: connected
SIP User Agent: asterisk

[Jake]

Have you tried and reset and reconfiguring your set-up?

More then that, i build a new asterix machine ! Same prob

and :

YOUR SIP STATUS
SIP Status: connected
SIP User Agent: asterisk

Unless they have changed things, they usually block the useragent 'asterisk'. This might be why you are not getting calls. You need to look in your sip.conf (or extended conf file) and change the useragent to anything else.

[andysiddell]

Well all was well for a few hours last night and yet again today calls going straight to VM.

Nothing has changed my end so it has to be FPL!

[Jake]

Well all was well for a few hours last night and yet again today calls going straight to VM.

Nothing has changed my end so it has to be FPL!

Did you change the timeout period?

I have a theory that their servers might be blocking accounts where the register time is too short. You said above it was set at 30, I didn't see a post that you changed it. I have mine set @1800 and it seems to stay connected.

[FONGO_mike]

Well all was well for a few hours last night and yet again today calls going straight to VM.

Nothing has changed my end so it has to be FPL!

Did you change the timeout period?

I have a theory that their servers might be blocking accounts where the register time is too short. You said above it was set at 30, I didn't see a post that you changed it. I have mine set @1800 and it seems to stay connected.

As Steve mentioned in this thread, aggresive set-u[s as 30 seconds could be become blocked for abuse.

[Tenacious]

1 call went to voice mail so far today with 3600 as timeout. Subsequent calls which were my test calls are working fine. Is there such thing as an ideal timeout # ?

Having the ATA check Fongo every hour or 3600 seconds should be more than adequate for more routers. This reminds the router the ATA still need these ports. However, if you have a substandard router, one that does not keep track of the where the ports are forwarding to property for more than 5 minutes, then you have to set the registration period to something smaller, like 300 seconds. 30 seconds is pointless, and puts undue stress on Fongo's servers.

[hete]

i change all Registration Times to 3600 (minexpiry) (maxexpiry) (defaultexpiry) and still fall on FPL VM !

[Jake]

i change all Registration Times to 3600 (minexpiry) (maxexpiry) (defaultexpiry) and still fall on FPL VM !

I think one of my Accounts got blocked the other day, so if you just changed things then mine took a few hours to come back.

Just as a test, try changing your user agent and see if it changes in your FPL online settings page, where it shows your sip settings. Mine didn't change, until the account started working again.

[hete]

i change all Registration Times to 3600 (minexpiry) (maxexpiry) (defaultexpiry) and still fall on FPL VM !

I think one of my Accounts got blocked the other day, so if you just changed things then mine took a few hours to come back.

Just as a test, try changing your user agent and see if it changes in your FPL online settings page, where it shows your sip settings. Mine didn't change, until the account started working again.

i used Mozilla and i just switch to Asterisk and it change nothing :'(

[Jake]

i used Mozilla and i just switch to Asterisk and it change nothing :'(

You have the same as me then. Mine kicked back in about 4 hours later.

It could be you have to wait for your account to become 'unstuck', then the new registration time hopefully will keep the accounts from getting 'stuck' again.

[hete]

it works fine all the afternoon (3600 sec) but just now the system kick us back again

FreePhoneLine, please i host for my friends on my asterisk server and everything goes wrong since 10 days, every line is dead because of that :'(

[andysiddell]

Yes I set the time out to 3600 but this did not solve the problem. I think it's time to say goodbye to this service. I'd rather pay and have reliability.

[senos]

Calgary: my calls are going straight in to VM as well since yesterday.

As we suggested, please set your timeout to 3600

time out 3600. This morning, still the same problem