- Joined
- Jan 4, 2023
- Messages
- 1
- Reaction score
- 0
After doing weeks of testing I have come across this issue where I suddenly have stopped receiving sms after updating to 3cx v18.5.
I have read through all these forums, docs, and contacted 3cx through the chat. Which then was recommended to post on here about it maybe someone else has had the same issue.
I've already contacted telnyx and although not helpful they did point me to a site where I could check that the message was being sent successfully to a webhook so that I could prove that it works.
Well I already knew the SMS and the VOICE worked correctly. I had tested this already. The calls are routed correctly. There are no fancy routes or time of day or anything that would prevent a call from going through as this has prompted me to create a new instance for testing ONLY. As a best practice I like to do this before deploying any large scale project. Not just a PBX.
Having said all that. I have concluded that there is an issue with the webhook url specific to telnyx.
My first question is, is this issue resolved in the beta before I update this PBX to go through the headache of testing it.
What did I do to confidently say it is the webhook?
So does anyone know if this V6 bete is worth the time to update my offices to it??
I have read through all these forums, docs, and contacted 3cx through the chat. Which then was recommended to post on here about it maybe someone else has had the same issue.
I've already contacted telnyx and although not helpful they did point me to a site where I could check that the message was being sent successfully to a webhook so that I could prove that it works.
Well I already knew the SMS and the VOICE worked correctly. I had tested this already. The calls are routed correctly. There are no fancy routes or time of day or anything that would prevent a call from going through as this has prompted me to create a new instance for testing ONLY. As a best practice I like to do this before deploying any large scale project. Not just a PBX.
Having said all that. I have concluded that there is an issue with the webhook url specific to telnyx.
My first question is, is this issue resolved in the beta before I update this PBX to go through the headache of testing it.
What did I do to confidently say it is the webhook?
- I used a different webhook from the webhook site. (its basically a sandbox type site for testing webhooks)
- status was delivered
- Placed the failover in my messaging profile in telnyx from the webhook site and the 3cx as the primary
- only the failover worked
- both webhooks in telnyx debugging reported as being delivered.
- Created a new sip truck new messaging profile new everything with an sms 800 number to eliminate the A2P aspect as this is strictly for B2C comms.
- Statuses same.
- I see the json sent and received on the testing site.
- So after much red tape internally I was approved for the funds and permissions to set up an account with SKYETEL.
- Completed the text successfully
- Problem is that I have to register the numbers to comply with these new laws about A2P SPAMMERS.
- This business is not like that. We are asked to contact most of our customers through text or chat. Our customer base is more receptive to this method of communication. (the entire world is honestly)
- I will also have to port my numbers over from telnyx to skytel if i have to use this as the provider now.
- I have seen other threads talking about this exact problem because of the whole issue with telnyx not being a recommended provider anymore. I am not trying to get into the politics of that.
- I have created accounts for SIP trunks at WAVIX SKYETEL VOXTELSYS & LUMEN.
- I DON'T WANT TO DROP MONEY INTO THESE ACCOUNTS IF I DON'T NEED TO.
- I am also going to test with googles SIP option
So does anyone know if this V6 bete is worth the time to update my offices to it??