Voicemail unreachable when logging out of SIP

[laurent]

Yes I know there's already a million threads about voicemail issues, but eveyone has a different problem and they're all interwitted in various threads, making it impossible to actually follow development.

This thread is for a very specific issue I'm having right now.

After using a mobile SIP device (Siphon on my iPhone, over 3G btw, works awesome contrary to my previous statements), I close the application. The application may or may not unregister fom the server, that I don't know.

What I do know, however, is that from this point on, my voicemail is unreachable to callers. When I call my FPL number from a PSTN line, I get a few seconds of silence, then fast busy. This indicates a failed call, so my understanding is that the FPL server tried to find an SIP device, none was available, then went to voicemail, which also failed, then no more options available to the call is logged as failure.

I wanted to bring this particular issue to the attention of the admins because a lot of work is being done right now with the voicemail system, and while you've got both hands into the server guts, you may want to take a stab at this as well.

Sorry if it's a gruesome example, but halloween is coming.

[FONGO_steve]

If you wait any length of time, say 30 minutes, to 30 hours, does voicemail ever start working again?
And do you get the same results if you use a completely different internet/network connection? Like a coffee shop one?

I have seen a few reports of this, but most say that if they wait long enough that it will eventually start working. What's happening is the device isn't unregistering with our server - we aren't quite sure if it's the device/network/router not releasing the connection with our server, or if something is causing our server to not refresh fast enough. It seems to happen on a fairly low percentage of accounts, but I am still going to have it looked into regardless because I'd like to know if anything at our end would cause this and then have it fixed accordingly.

[laurent]

Yes I agree tihs is most probably triggered by a device suddently disappearing and not unregistering. This would be the same as a power outage at any client of yours; their ATA wouldn't unregister.

In this situation, albeit rare, it becomes important that the server processing the call moves to the next item in list instead of failing the call completely. Making sure voicemail picks it up would not only ensure your termination is completed, but also the clients would enjoy voicemail picking up their calls while the power outage / internet outage left them without phones.

In my case, it's back operational because my home ATA registered again (60 minutes expiration I think.)

The test I made was over 3G. I connected Siphon, received a call from a PSTN line, then closed the app, which probably skips the unregister, and then called again a few times from the same PSTN line. I'll test again later today over wifi, but I don't think it would make any difference as I'll just drop out from the map from the server's perspective the same as I do over 3G.

[hinchesk]

Having the same issue but only using the Mac client (2.0.2), no other SIP devices/clients. I used the Menu item to log off and close the client, then tried calling my FPL number several times. It's been over an hour since I logged out of the FPL client but my voicemail still won't pickup.

I've also tried reducing the time it takes for vmail to answer under the Follow Me settings but there's no difference. Ideally the 'Seconds to voicemail' option would let you override any other devices/clients that haven't properly unregistered.

[FONGO_kris]

hinchesk, could you PM me your number please? I'd like to try something out - It may not work, however if it does we may need to release an updated software phone!