Solved Whatsapp working only one way

[ODD Network BV]

Hi guys,

i did implement the whatsapp integration to 3CX.
But is working one way. i can receive whatsapp message from customers in webclient, but can not reply to my customers.
So, seems to be working one way at this moment.

In my whatsapp certificate I get this message also. Maybe 3CX have to finish with the integration???

Whatsapp Certificate message:
The certificate is not available for your business. Only the business solution provider who manages integration with the WhatsApp Business Platform will be able to download the certificate.

 

[N_G]

Are you sure you followed all the steps and your Whatsapp business number is verified and you are on the Facebook meta platform etc etc?

no its working well in all the numbers we have tried but in the end its Whatsapp that approves your business to their platform, not us.

 

[ODD Network BV]

Hi Nick,

Yes i follow all the steps.
Number has been approved.
I see more peoples with same issue.
3cx is not sending any data back to Meta. That is what is happening.
We can not reply on customers whatsapp messages.

 

[blue12]

I am getting the same problem and have the same certificate error.

 

[Gioal]

Same issue here.

Traced via tcpdump, no packet going from 3CX to anywhere when replying a message.

 

[jonfry]

Same here. Inbound messaging only. When I reply to an incoming WA message the reply is not delivered to the sender.

 

[stefanprasch]

Yesterday it worked fine. After that it won’t work.
I think Meta blocked the API or something else.
Only one way! Not back to customers.

 

[jonfry]

It's working again for me this morning. Not sure what caused yesterday's one way chat but it's now behaving itself.

 

[Roy Schotpoort]

i have the same problem
- Im using a test number and aproved
- company has been aproved
- configured the app in the META Developer Portal.

it does work but not when i sent a reply.

 

[amateop]

same problem here, I only get messages but my replies don't reach the user

 

[ngx]

Hi,

We have the same issue.

However we do have two WhatApp accounts under 3CX (purpose is to route to different queues with different numbers).

The first account we added, messages work both ways, we can receive and send.

On the second account we have the issue everyone is reporting. We can only receive messeges from customers, but we can’t send. Replies don’t go thru.

We tripled checked configurations and everything looks fine.

 

[Gioal]

Hi,

We have the same issue.

However we do have two WhatApp accounts under 3CX (purpose is to route to different queues with different numbers).

The first account we added, messages work both ways, we can receive and send.

On the second account we have the issue everyone is reporting. We can only receive messeges from customers, but we can’t send. Replies don’t go thru.

We tripled checked configurations and everything looks fine.

Have you the same whatsapp number in another sip trunk?

 

[ngx]

Have you the same whatsapp number in another sip trunk?

Yes, we do have the same number on a SIP Trunk for Voice and on the WhatsApp SIP Trunk.

Although, one works and the other doesn’t.

Both WhatsApp accounts have the same number in different SIP Trunks, just one works and the other doesn’t.

 

[N_G]

@ngx - Currently you can not have another number configured in the sip trunk.
@stefanprasch - I suspect its the same issue.

To get outbound messaging in this alpha you must have the number only in whatsapp. However in alpha 2 this will be addressed.

You can have the number in whatsapp and in messaging. However please note that whatsapp will not allow you to register the number in both your mobile and 3cx for example. The number must be dedicated to whatsapp.

IMPORTANT: Please note you can only reply to an inbound message. You can not initiate a message to someone, nor reply to someone that contacted you before. The outbound message window is 24 hours and only to a received message. Whatsapp is for responding only, not initiating a chat.

 

[Gioal]

@ngx - Currently you can not have another number configured in the sip trunk.
@stefanprasch - I suspect its the same issue.

To get outbound messaging in this alpha you must have the number only in whatsapp. However in alpha 2 this will be addressed.

You can have the number in whatsapp and in messaging. However please note that whatsapp will not allow you to register the number in both your mobile and 3cx for example. The number must be dedicated to whatsapp.

IMPORTANT: Please note you can only reply to an inbound message. You can not initiate a message to someone, nor reply to someone that contacted you before. The outbound message window is 24 hours and only to a received message. Whatsapp is for responding only, not initiating a chat.

@Nick Galea are in your plans implement the feature to start a conversation via whatsapp?

 

[N_G]

Whatsapp is not really meant for this. It means getting your outbound messages pre approved by Whatsapp. It all depends how easy it will be from the portal to do this and what the policies will be.

We are working on Telegram support and there it will be much easier to initiate an outbound message.

 

[Evolute IT]

We are working on Telegram support and there it will be much easier to initiate an outbound message.

Is Apple iMessage for Business still on the roadmap? I know it's a very complex platform so I was curious. I remember you mentioning it in the v18 Intro video.

 

[petxi79]

same problem here, I only get messages but my replies don't reach the user

we have the same problem, we can receive messages from Whatsapp but when we reply the customer doesn't receive the answer.

 

[paurus]

We are working on Telegram support and there it will be much easier to initiate an outbound message.

Wow!!! Wow!!! Super!!!

 

[blue12]

we have the same problem, we can receive messages from Whatsapp but when we reply the customer doesn't receive the answer.

I had this problem and changed the DID to 000000 for the trunk number. After doing this WA worked fine.