V16, Update 7 Alpha Sports FB & SMS Business Messaging and Live Chat Improvements

  • Thread starter Thread starter Constantinos Constantinou
  • Start date Start date
Another vote for Twilio for SMS support.
 
Dear Flowroute user,

numbers must be in e164 format in 3CX (+1-XXX-XXX-XXXX) for the inbound route and when you enter the TO number. All number transformation will be done by 3CX to comply with the provider.

Some other things which might be overseen which are needed for inbound messages to arrive:
  1. Ensure your Web Port is exposed to the WAN for inbound message delivery
  2. Ensure that you use the API version 2.1
 
  • Like
Reactions: accentlogic and N_G
What about MMS? Is that a no? Or just a not yet?
 
  • Like
Reactions: Eagle2469
Last edited:
Twilio is under consideration. FOr future builds the SMS will be sent directly from the 3CX instance but this will be for the next version....
 
Would love to see chat support for WhatsApp
 
  • Like
Reactions: JLSeagull
Both Apple Business chat and Whatsapp are not open enough to support on our platform at the moment. Basically there is an administrative process for both that means for most small to medium businesses its not a possibilty. Once it is and they have open APIs of course we will do so immediately.

Meanwhile it seems INstagram will be added to the Facebook API so Instagram will be coming soon.
 
I was really hoping for Microsoft Direct Routing capability for Microsoft Teams support. Is still on the roadmap?
 
I was really hoping for Microsoft Direct Routing capability for Microsoft Teams support. Is still on the roadmap?

Came here with the same Question....
 
  • Like
Reactions: HLM 3CX
Dear Flowroute user,

numbers must be in e164 format in 3CX (+1-XXX-XXX-XXXX) for the inbound route and when you enter the TO number. All number transformation will be done by 3CX to comply with the provider.

Some other things which might be overseen which are needed for inbound messages to arrive:
  1. Ensure your Web Port is exposed to the WAN for inbound message delivery
  2. Ensure that you use the API version 2.1
When I change the number format to +1xxxxxxxxxx in the Route section in Messaging, I cannot text outbound and inbound does not work. When it is left as 1xxxxxxxxxx outbound works but no inbound. 3CX passes all firewall checks and API is Ver. 2.1 in the Flowroute portal.

When sending a text it force you to add the +, which is ok. I then enter the number I am texting to in the format 1xxxxxxxxxx. Again, it works outbound when the route is without the + and not at all with the +.
 
Both Apple Business chat and Whatsapp are not open enough to support on our platform at the moment. Basically there is an administrative process for both that means for most small to medium businesses its not a possibilty. Once it is and they have open APIs of course we will do so immediately.

Meanwhile it seems INstagram will be added to the Facebook API so Instagram will be coming soon.

Twilio has support for Whatsapp. Maybe for some that use it, 3CX, if and when Twilio is supported, could also add the Twilio Whatsapp support for those that are wanting it.

Ref: https://www.twilio.com/docs/whatsapp
 
I had already tried the +1 as well previously just in case. The instructions say to copy the number as is from Flowroute which is just the 1XXXXXXXXXX. I'm pretty sure it's on the 3CX end and I really hope they just ditch the central relay and just let the webhook callback to the individual instance using a custom path on the 5001 port. This is already done with normal Click2Talk and Click2Meet so should be possible to be handled with the server instance as well.
 
  • Like
Reactions: accentlogic
I was really hoping for Microsoft Direct Routing capability for Microsoft Teams support. Is still on the roadmap?

You can use our SBC to integrate your 3CX with MS Teams, DM me for more details. *It does require an E5 license or the added on phone system license in MS.
 
Both Apple Business chat and Whatsapp are not open enough to support on our platform at the moment. Basically there is an administrative process for both that means for most small to medium businesses its not a possibilty. Once it is and they have open APIs of course we will do so immediately.

Meanwhile it seems INstagram will be added to the Facebook API so Instagram will be coming soon.

When is 3CX going to release SMS for all SIP carriers? We tried to get on this release and were told to wait.

We are also in the works to update our API to support WhatsApp and RCS
 
When I change the number format to +1xxxxxxxxxx in the Route section in Messaging, I cannot text outbound and inbound does not work. When it is left as 1xxxxxxxxxx outbound works but no inbound. 3CX passes all firewall checks and API is Ver. 2.1 in the Flowroute portal.

When sending a text it force you to add the +, which is ok. I then enter the number I am texting to in the format 1xxxxxxxxxx. Again, it works outbound when the route is without the + and not at all with the +.

The issue is the setup of your custom
domain certificate, it misses the intermidate cert.

For other as well, a good place where you can check this is here: https://www.sslshopper.com/ssl-checker.html
 
So 3cx seems to think that implementing an integration to Facebook is important when we Network Admins have been spending the last few years removing access to it from our networks. How does that make sense??
 
  • Like
Reactions: sst_ekell
So 3cx seems to think that implementing an integration to Facebook is important when we Network Admins have been spending the last few years removing access to it from our networks. How does that make sense??

maybe it is not for you but for many it is. The usage is up to you and user can manage Facebook messages without allowing them access to the platform.
 
When is 3CX going to release SMS for all SIP carriers? We tried to get on this release and were told to wait.

We are also in the works to update our API to support WhatsApp and RCS

our team is now open to screen requests. You may contact us by using [email protected]