Call Forwarding/Voicemail - How do you want it?
 

Hi,

We would like your thoughts on how you want this to work. At the moment this is how it works for an inbound call:

1. The system checks if the member's ATA is registered. If so, the inbound call is sent to the ATA.

2. Call forwarding rules are checked. If a match occurs, inbound call is forwarded.

3. Route call to voicemail

There have been requests to enable/disable step 3 and also to promote step 2 ahead of step 1.

Comments?

There is always the "user configurable" approach, so that everyone could have it their way. ;)

From a personal standpoint, I would promote the forwarding rules ahead of the registered adapter. And that should especially be true for all the forwarding rules that aren't "default". After all, what good does it do to have "custom forwarding" (based upon number), if the adapter being "registered" overrides all forwarding?

1. Call forwarding rules are checked.
   1. If a match occurs, inbound call is forwarded.
   2. If no match occurs, or no rules exist, proceed to...
2. If ATA is registered, send call to ATA.
   1. If ATA forwards call to voice mail (either immediately or after timeout) (e.g. voxalotnumber@voxalot.com), then go straight to voice-mail. I don't know how things like my SPA3K implement forward to voice-mail - do they do another SIP invite? In any case, the key here is that if the SPA send to voice mail then it should go straight there. This allows me to do things like call forward using *72 from my phone or DND using *78 - no PC required.
   2. If call is not answered within user defined timout, then go to voice mail.
3. Go to voice mail.

Because I don't have call forwarding rules set up, I'm getting 1-3 at the moment that suits me fine, but I can see where having forwarding rules set up would be good.

I agree with BJReplay; that's what I would expect to happen.

I noticed that currently mapping a Voxbone DID to Voxalot, and call forwarding voxalot to a listening ATA will not allow the call, if it goes unanswered, to be sent to voice mail. Instead after four rings or so, the ringing changes abruptly to a fast busy instead of the Voxalot voice mail IVR being loaded up. My desired behavior instead of the busy would be for voice mail to turn on. Otherwise, I might as well just point the Voxbone DID straight to the ATA and let it be able to ring indefinitely.

This ringing turning into a fast busy behaviour also occurs when the Voxalot account is called by SipBroker, when Voxalot is not currently registered with any device and a call forwarding rule is in effect to a waiting ATA.

Call forwarding has been changed to align with BJReply's process above. The ring time-out has been extended to 60 secs.

This will end up user defined but for now is set to 60secs.

Please let us know if there are any problems.

Thanks
 

Ummm, OK. I'd like to thank my mum, my dad, my agent...

I'm glad people agreed, and that you agreed as well.

I don't know if this is technically possible but I would like forwarding to occur, if the conditions are met, but if the number it is forwarded to doesn't answer I'd like it to go to the voxalot voicemail.
That way I can have a separate mailbox for callers on voxalot to those of the forwarded number.

I would appreciate this feature as well.