3CX configuration can not be completed

[sparkles]

Hi everyone,

We're currently facing an issue while configuring WhatsApp in 3CX. We seem to be stuck at the step where we're trying to configure the webhook.



After some research, I came to the conclusion that Meta requires a verification process for the webhook, where a specific challenge code must be returned exactly as provided in the URL parameter.

While testing against a mock API and comparing it with the actual webhook endpoint, I noticed that 3CX returns the challenge code as an integer instead of a string. This seems to break the verification — even though a few months ago this wasn't an issue with Meta.

Is anyone else running into the same problem when configuring a new WhatsApp account in 3CX?
Is there a fix underway or a known workaround?

Thanks in advance!

 

[IliasL_3CX]

Hello,

We have made a new configuration of Whatsapp and we were unable to reproduce the issue. The webhook was validated correctly on our side. Can you please ensure that the webserver port of the phone system is reachable from the outside world as this message can also occur if the webserver port is not reachable

 

[sparkles]

Hello,

We have made a new configuration of Whatsapp and we were unable to reproduce the issue. The webhook was validated correctly on our side. Can you please ensure that the webserver port of the phone system is reachable from the outside world as this message can also occur if the webserver port is not reachable

We've verified that it's reachable. But it still couldn't be validated.

We've checked the following:
- Geoblocking has been turned of so free access for the whole world now.
- Verified it's workings of META via an other alternative API (self made) this works. Only not by meta.

Out callback URL looks like this:

https://******.*****.com:5001/sms/whatsapp/61abe6****************34d3 (of course without the *).

And verify token was something random, since 3CX doesn't do anything specific with it so in our case it's "1ju39ebd28ehurgre879fgqe8ir13r"

 

[sparkles]

As an addition to the above, my initial theory of the integer vs string look more likable due to us finding that META is succesfully sending en receiving packages from us. But the body thus the verification response is out of place.


We're running 3CX on Windows Server (20.0.5.551) with port 5001 for the web interface

 

[sparkles]

Hello,

We have made a new configuration of Whatsapp and we were unable to reproduce the issue. The webhook was validated correctly on our side. Can you please ensure that the webserver port of the phone system is reachable from the outside world as this message can also occur if the webserver port is not reachable

Please help?