Outbound dialer doesn't start

[NonLinearly]

I have add the demo outbound dialer to the call flow apps and the app has been deployed correctly (green). I made a 849 queue and assigned the 860 extension to the app. I make a call to 860 to start making calls but nothing. The service (3CX PhoneSystem 01 Call Flow Server) is running!

 

[SnakeRiverWebDevelopment]

Try calling 860 direct, this should start your CFA

 

[edossantos]

First, check the 3CXCallFlow.log file in verbose mode, to ensure that it's making calls.

Then, if calls are not being made, check if you have outbound rules in place.

 

[VoIPTools]

Also consider that the calls generated by the dialer are coming from "MakeCall" and not from an extension. If your outbound rules have restrictions that require group membership, or explicitly require calls coming from extensions, dialer calls will be blocked.

Also, make sure whatever outbound rule is being used has a DID specified. Without a specified DID, 3CX will send "MakeCall" as the caller ID number and the call will likely be rejected by your SIP carrier.

 

[NonLinearly]

I am not in the office now. But I suspect that has to do with outbound rules. But what is the extension that makes the calls so that it is added to the outbound rule. Is the 860?
VoIPTools said
"If your outbound rules have restrictions that require group membership, or explicitly require calls coming from extensions, dialer calls will be blocked."
So I have to not fill such restrictions with the risk everyone to make external calls if the prefix is known

 

[VoIPTools]

You have some choices. You could, for one example, have the dialer add a prefix (perhaps 7777) to each number dialed. Then, have the outbound rule strip the 7777 before sending it to your carrier.

 

[NonLinearly]

You have some choices. You could, for one example, have the dialer add a prefix (perhaps 7777) to each number dialed. Then, have the outbound rule strip the 7777 before sending it to your carrier.

Not "some choices". This choice only.