Solved

Attempt to forward a call in setup sate results in Forbidden "operation is not allowed"

  • 27 January 2022
  • 3 replies
  • 466 views

I'm trying to forward a call out of a queue. The call forwarding application works in several ringCentral accounts except for the main customer it was built for.... it works in sandbox and production environments except one.

My app has the Call Control permission, the call state is still in Setup when the forward is sent with the proper payload of extensionNumber.

RingCentral returns operation not allowed / forbidden

Forbidden error happens when the call is in an Answered state but I can't find a reason for the failure.

body={"errors"=>[{"errorCode"=>"TAS-106", "message"=>"Operation is not allowed"}]}

response_headers={"server"=>"nginx", "date"=>"Wed, 26 Jan 2022 05:05:37 GMT", "content-type"=>"application/json", "content-length"=>"123", "connection"=>"close", "x-rate-limit-group"=>"light", "x-rate-limit-limit"=>"50", "x-rate-limit-remaining"=>"49", "x-rate-limit-window"=>"60", "routingkey"=>"SJC01P13", "rcrequestid"=>"99381BLAH6"} @status=403 @reason_phrase="Forbidden"


The one thing I see that stands out is that for this customer queues the calls quickly move from the Setup state to the Proceeding state. Even if we don't send the forward API message, the call still goes into a proceeding state. For some reason this only happens on one environment.


Any help at all would be greatly appreciated.

Zak

icon

Best answer by Phong1426275020 28 January 2022, 18:06

View original

3 replies

Userlevel 1

There are 2 scenario to receive the Forbidden error.

1. A call is in a wrong stage (which is not in this case as you wrote)

2. A call forwarder is not the owner of the call. In your case, it is a call via a call queue, so the owner of the call is the call queue extension (the call queue manager).

So which user is authenticated in your app to forward that call?

Phong Vu! My call forwarder will never be the owner of the call, this is a server side automatic routing application with password authentication. The user I was using was had the Super Admin role, however... it was not the default Super Admin (with default extension 101). I have spent all week on this with a very frustrated customer, it's finally working. thank you!


Userlevel 1

Yes, the only extension that can control other user's call is the main super admin user (not just any super admin). Note that this is for now and can be changed stricter in the future.

Reply