topic Re: StatusCode:BadGateway in Webex for Developers

StatusCode:BadGateway

Urs Wuest — Wed, 04 Mar 2026 07:26:59 GMT

Hi,

I tried to create a CallQueue and get the following response:

"The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.","errors":[{"description":"The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request."}] [TrackingID:ROUTERGW_346f4bb0-5412-487a-842b-3cb27dd3dc6e]

What is the problem?

Best regards

Re: StatusCode:BadGateway

Janos Benyovszki — Fri, 06 Mar 2026 13:16:08 GMT

@Urs Wuest note, that we had several service degradations on the day you reported this issue and some of them are still in effect - https://status.webex.com/commercial/status?lang=en_US .

Re: StatusCode:BadGateway

Urs Wuest — Mon, 09 Mar 2026 07:48:33 GMT

Hi Janos Benyovszki,

I have still the same problem:

"errors":[{"description":"The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request."}] [TrackingID:ROUTERGW_b6579532-303f-4393-ad8a-af88b3166f79]

Does the problems in UAE and Saudi Arabia has an impact when calling from Germany?

Re: StatusCode:BadGateway

sandiban — Fri, 13 Mar 2026 07:34:49 GMT

Hi @Urs Wuest,
Thanks for your patience on this item!
We believe by now you should've experienced better response out of it and hopefully the error doesn't bother you anymore since the issue has been resolved now.
In case you still face any error or, glitches on these mentioned APIs, please let us know. Thank you!

Regards!
Sandip

Re: StatusCode:BadGateway

Urs Wuest — Fri, 13 Mar 2026 08:17:08 GMT

Hi @sandiban
I have still the same error by creating a CallQueue (the same at HuntGroup):
StatusCode:BadGateway, Content:{"message":"The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request." [TrackingID:ROUTERGW_639f7190-188b-4588-adba-177eb32f87a1]

When I list the CallQueue or the HuntGroup everthing works fine - only by creating I get this error.
Could something wrong in the request?
But then the error is misleading.

Regards

Re: StatusCode:BadGateway

sandiban — Sat, 14 Mar 2026 11:44:33 GMT

Thanks @Urs Wuest for your patience so far!
Yes, I checked the logs for the error trackingId you shared and the main error reason behind this API failure is -
"[Error 4201] The phone number is not available. It is already assigned to a user or used in another location: +41-435470218. - null -errorCode [4201]"

So looks like this number: +41-435470218 is already assigned to a User or, getting used by some location in the Org: Recos IC (orgId: 721092f5-fa14-44fc-a66e-c1622d5af8c9)

Could you kindly check the background a little further and see if this is a valid statement.
If so, then you won't be allowed to assign this number again.
And the reason why you're getting 502 status code is because due to this error, the API Gateway is not reach the Calling API gateway upstream server for getting the request processed. It's failing much before than that.
hope this clarified the background now. Please let us know for any further queries. Thanks!

Regards!
Sandip

Re: StatusCode:BadGateway

Urs Wuest — Mon, 16 Mar 2026 09:53:49 GMT

Hi,
yes, that was the problem - the phone number was not correct!
Thanks a lot.
BUT, the error message "Bad gatway ..." is absolute misleading. You should change that in way with appending the above message "The phone number is not available. It is already assigned to a user or used in another location".

Best regards.