Solved Cannot transfer calls to ring group from CFD app

Status
Not open for further replies.

Carlo Okolowitz

Customer
Joined
Apr 6, 2018
Messages
13
Reaction score
1
I have a ring group with two extensions. I can call the ring group internally and it works as expected. I have a menu tree I created using the CFD that should transfer a caller to the ring group extension when they select it from the menu. If someone selects that option, the call immediately hangs up. The captures show the DTMF selection for the menu number that should transfer; but the very next thing sent is a BYE. If I change the menu to use a specific extension rather than a ring group, the calls transfer to the extensions as expected, it only hangs up when using the ring group as the destination. Can you not transfer calls to ring groups?

RESOLUTION: Make sure that all extensions or other numbers in the CFD have been put in quotes. The extension had a leading 0, without quotes around the extension number in the CFD, the number was not a complete or valid extension, so it was ignored and the next step in the call flow was to disconnect the call, so it did just that.
 
Last edited:
An extension is an extension. You can transfer to a ring group with a CFD. Take a look in the Queue Manager Log... maybe you can see an error there?
 
Wasn't aware of a separate log for the queue manager. Where is that log found?
 
The log can be found here. C:\ProgramData\3CX\Instance1\Data\Logs\3CXQueueManager.log. Make a call, then immediately open the log (text) file and scroll to the bottom... then work your way up in the log until you find information about your call.
 
I'm on the pre-packaged Debian install; so, that isn't the path to the log. I'm regretting the decision to try the linux option.
 
Sorry. I forgot you are Linux. /var/lib/3cxpbx/Instance1/Data/Logs/3CXQueueManager.log.
 
Resolved! Thanks for the assistance on this. It was really strange. The logs made it look as though no transfer attempt was made at all. So, I tried looking at the CFD app again and got thinking that maybe since the extension I was dialing began with a 0 that maybe it was dropping that digit unless I put it in quotes. When I put the extension in quotes, the calls now transfer correctly.
 
Dang, you don't know how many times I've been bit by the dreaded quotes. That was my first guess, but when you said it worked with other extensions I figured you must have the syntax right. I guess you made the same assumption. Without the quotes it assumes an integer and strips the leading zero.
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,885
Messages
589,545
Members
164,744
Latest member
johnblackwood1