Issue with PhoneSystem.Root.MakeCall(<from>, <tonumber>) in Latest 3CX Versions

AshishKushwaha

Gold Partner
Basic Certified
Joined
Apr 29, 2024
Messages
63
Reaction score
10
We've been using the PhoneSystem.Root.MakeCall(<from>, <tonumber>) method successfully up to version 5.551. However, in the latest 3CX releases, we are encountering an issue.

The call to the <from> extension is placed successfully, but after the call is answered, the system attempts to dial the <tonumber> automatically. At this point, we receive a "Call Transfer Failed" message, and the call is immediately disconnected.

This behavior was not present in earlier versions, where the transfer used to complete successfully.

Has there been a change in how MakeCall functions in the newer versions, or are there updated requirements or permissions for call transfers? Any guidance or workaround would be greatly appreciated.

Thank you in advance!
 
  • Like
Reactions: Evolute IT
Hello Ashish,

That method from the Call Control API was not recommended to be used for a long time. The preferred method is the one using the RegistrarRecord to start the call, instead of the number.

If you're trying to build an outbound dialer, you can also take a look at SIP Caller, which works perfectly well with 3CX.

Kind regards.
 
  • Like
Reactions: Evolute IT
In answer to your question @AshishKushwaha, the API does not appear to have changed. Perhaps you have an outbound rule issue in your test environment?

Remember, the call is coming from "MakeCall" so you need at least one rule that does not include group or extension filters, AND has a configured caller ID number.

Creating the necessary outbound rule is something many, many people struggle with, so I suggest you create a rule that requires the phone number start with something like "8888". Have MakeCall prepend these extra digits automatically, then have the outbound rule strip the extra digits. This makes it simple to add a outbound rule specifically for MakeCall that has no impact on the rest of your phone system, but ensures there is an working rule for MakeCall. Put that rule on the bottom of your list of outbound rules.
 

Latest Posts

Forum statistics

Threads
111,962
Messages
589,995
Members
164,867
Latest member
swegner