- Joined
- Aug 6, 2018
- Messages
- 35
- Reaction score
- 4
What about MMS? Is that a no? Or just a not yet?
Put it in test environment only. I have some serious memory usage since this update and the UI is slower for some reason.
And that's on my lab instance.
I've noticed the same thing. Random memory and CPU spikes. I guess that's why it's beta...
I was really hoping for Microsoft Direct Routing capability for Microsoft Teams support. Is still on the roadmap?
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.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:
- Ensure your Web Port is exposed to the WAN for inbound message delivery
- Ensure that you use the API version 2.1
When I change the number format to +1xxxxxxxxxx in the Route section in
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?
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 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 +.
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??
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
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.