Call Control API Error

Mary Grace Barchi

Silver Partner
Advanced Certified
Joined
Oct 30, 2025
Messages
2
Reaction score
0
This is the error we get when we try to bargin using the Call Control API:
Call control operation failed with result: Rejected(NotSpecified:Has no rights to barge in!)

In case it helps, this is what we're invoking using the C# Call Control API:
var ext100 = PhoneSystem.Root.GetDNByNumber("100");
var registrarContacts = ext100.GetRegistrarContactsEx();
var result = await registrarContacts[0].BargeInCallbackAsync(ac, PBXConnection.BargeInMode.BargeIn);


We invoke this when we receive an "Update" notification from the Call Control API, where the ActiveConnection is in the Connected state, for a call between an extension (agent) and an ExternalLine (customer). In this case we want to add another extension (with number 100) barging in the call. However we get that Exception when we invoke this.

Our final goal is to use the extension number of a Digital Receptionist or Call Flow App to barge in the call, which we tried and didn't work either. But this is not even working with an extension, which should be allowed....
 
Hello Mary Grace Barchi,

Did you also try this with a phone to Barge In?
Just to be sure this is not a problem with rights on the 3CX.

Like, does ext. 100 have the full rights to bargein to the call.
If not, this can be the Department, or call controll rights ...
If you can do this from a real phone (webclient, smartphone, hardphone) on ext. 100, than it should be the API indeed.

I am asking this, because the error is pretty specific about something wrong with the rights.

Paulo
 
  • Like
Reactions: Evolute IT
I've struggled to understand how to properly setup permissions when you create the API key. I think @paulodagraca offers a good place to start, but you may want to tinker with the permissions chosen when you created your key.
 
  • Like
Reactions: Evolute IT
This is using the C# Call Control API, so there is no API Key involved. The API should have full access, so I'm not sure what could be happening here.
 
  • Like
Reactions: Evolute IT
Ah, not too many people use that API (we do exclusively) so I made an incorrect assumption. Then the issue is permissions in 3CX and testing the ability to barge from a phone will confirm.
 
...where the ActiveConnection is in the Connected state, for a call between an extension (agent) and an ExternalLine (customer)
Incorrect sentence. ActiveConnection is not "between" them, it is the one of them
 
  • Like
Reactions: Evolute IT

Forum statistics

Threads
112,025
Messages
590,367
Members
164,976
Latest member
Roman Mazur