Unconditional Call Forwarding and FOP2
-
Hello,
I'm quite new to FOP2 but it is a fantastic product that is relatively easy to configure and use. I do however have a small issue. I have a client using FreePBX 2.10.1.2 and the v1.2.11 FOP2. There are several users with call forwarding enabled on their extensions (through ARI). This works without issues when trying to make a call directly to their extensions. When the receptionist transfers a call to their extension (via FOP2), however, the call goes directly to the user's voicemail instead of forwarding to the number specified in CF settings.
Any help would be appreciated.
Thanks!
-
When transferring, fop2 redirects to the dialplan extension@context and follows the rules that are set there. So, any call forwarding or any other dialplan rule should be followed the same as if you dial the extension from any handset. What kind of transfer are you using? attendant or blind? There is not much to do in fop2 itself as the transfer commands will just put the call in your dialplan, and asterisk will pick action up from there.
-
They are using blind transfer and the call forwarding works without issue if you use a handset to dial the extension (it forwards to the cell phone with no issue). The other strange thing is that another FOP2 user can make the same transfer and it obeys the call forwarding for the extension they are transferring the call to. Both users have the same FOP2 permissions so I'm a little confused. My CLI output doesn't show anything out of the ordinary. When dialing the extension that is forwarded (from a handset), CLI shows the proper call forwarding being applied (unconditional). However, when transferred from FOP2 to the forwarded extension by this particular user, CLI only shows transfer to voicemail even though Transfer is the only button being clicked on FOP2.
-
Unfortunately your description does not make much sense. A blind transfer made by some user works and the other does not.
FOP2 implements attendant transfers using the Atxfer manager command, and blind transfers using the Redirect manager command. Both commands take as destination an extension@context.
After the transfer/redirect is sent to that extension@context, is the dialplan that controls behavior. Fop2 does not care, does not know about Call forward or Follow me or whatever. It just puts the call in the dialplan extension@context.
You can enable full debug in fop2, but it will be very hard to read/follow. Your problem lies in the dialplan/asterisk, fop2 is not responsible of voicemails, call forwards and whatnot. You can inspect the asterisk full log also (/var/log/asterisk/full) after increasing verbosity and debug levels (asterisk -rx "core set verbose 10"; asterisk -rx "core set debug 1"), that might give you a better idea on what could go wrong, but again, it is wrong in the asterisk side of things.
-
Nicolas,
Sorry to have wasted your time, this one turned out to be related to a ring group setting that the particular user was a part of. It was a big ring group so I didn't put two and two together and see that the "Ignore CF Settings" was checked for this ring group so the system was, in fact, operating the way it should. Once I turned this setting off, the user was able to transfer the call out of FOP2 and it obeyed the CF setting of the extension being transferred to.
Thanks for your help on this, I appreciate it very much!
-
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login