What’s Cooking? Our Road Map

Status
Not open for further replies.
3CX is compatible with any camera that works in Chrome.
 
How is SMS planned? Does the SIP trunk provider have to support this or is it via web services?
 
  • Like
Reactions: RickG
Hi,

This still is the prevailing opinion?
Or maybe not an opinion just a fact because Microsoft doesn't certify 3CX SBC.

No plans to connect to Microsoft Teams. Teams is not that open and anyway wants to be a phone system in its next life. We did consider being a simple trunk in teams but it was rejected by Microsoft because they want to be the phone system themselves.

What I could imagine is 3CX as our main telephone solution and Teams also able to make external calls via Direct Routing connecting to 3CX SBC / SIP trunk.
Or is my imagination unrealistic?

Thanks.
 
  • Like
Reactions: jed
Hi,

This still is the prevailing opinion?
Or maybe not an opinion just a fact because Microsoft doesn't certify 3CX SBC.



What I could imagine is 3CX as our main telephone solution and Teams also able to make external calls via Direct Routing connecting to 3CX SBC / SIP trunk.
Or is my imagination unrealistic?

Thanks.
@Excel Telecom
 
How is SMS planned? Does the SIP trunk provider have to support this or is it via web services?
GOod question. We are making progress on this, but its too early to give a final answer. Most probably RCS / SMS and Fbook will be part of the 3CX license, not requiring a separate account but bundled with the main 3CX license.
 
Is there a timeline? Specifically, I am interested most in SMS support, but I am also generally curious about how to find timelines for the roadmap items.
 
  • Like
Reactions: Evolute IT
Hi @Nick Galea
I am convinced that many like me will be happy to have an update of the Roadmap as you did.

We are all aware that the roadmap is an overview / not guaranteed but it is always interesting to know where the team of developers are made :-) thx
 
  • Like
Reactions: N_G
GOod question. We are making progress on this, but its too early to give a final answer. Most probably RCS / SMS and Fbook will be part of the 3CX license, not requiring a separate account but bundled with the main 3CX license.

I think what he's asking, and what I am curious about myself, is whether or not SMS/RCS will be handled entirely by 3CX, or whether we need a compatible provider.

For example, I use Mautic, an open source marketing platform. It has some SMS capabilities, however it requires the use of Twilio, I cannot use any other provider.

Will the 3CX SMS/RCS implementation work with any SIP provider?
 
We will have our own SMS/RCS provider and some select SMS providers will be available. It will not work with any SIP provider, no....
 
So would the 3CX SMS/RCS service work with our existing DIDs?
 
@kylejwx93 no.... Unfortunately there is no standard way to support SMS. We will probably be supporting a few select SIP providers with well documented HTTP API's to send sms. You would have to port your numbers to them to SMS enable them.....
 
Last edited:
It would be awesome if we could utilize a template approach so that we could integrate additional providers.

I can't imagine there are that many methods needed (depending on how sophisticated the 3CX SMS client is). In C# vernacular, I'm thinking something like an interface where the implementation is abstracted.

I would think the basic SMS parameters would be common from one carrier to another. It is only the specific implementation that changes. That been my limited experience.
 
  • Love
Reactions: Evolute IT
We will have our own SMS/RCS provider and some select SMS providers will be available. It will not work with any SIP provider, no....
Any ETA on when we can expect this to be and an idea of what SMS providers ? Hoping some of the global brands will be on the list?
 
@kylejwx93 no.... Unfortunately there is no standard way to support SMS. We will probably be supporting a few select SIP providers with well documented HTTP API's to send sms. You would have to port your numbers to them to SMS enable them.....

So, assuming a compatible provider, will this work as a viable replacement for even giving out mobile numbers anymore?

Could this be a viable replacement in the sense that we can give customers a single number to both call and SMS (all the while, allowing other users to send SMS on our behalf)?

As it is now, I SMS from my mobile provider/cell phone, but do most of my calling from my 3CX. This tends to confuse and annoy customers since they get calls from my 3CX and SMS from my mobile number.

It would be outstanding if I could allow others in my office to send SMS from our 3CX instance (with the same DID), so I don't have to do all of that myself.

I've even been so inundated with SMS coming in that I have had to just leave my mobile phone behind so office staff could reply to all of the messages for me while I tended to other things.
 
@oguruma1218 - its a good point and we will definitely keep this in mind. First sms release will not be like this.... But we are planning to add facebook support so facebook users can send you a message.
 
  • Like
Reactions: accentlogic
I might have missed it, but is there any update when Raspberry PI 4 will be supported for 3CX and/or sbc?

Thanks
 
I am hoping for updated info since that post was about 9 months ago and that could have changed over time.
 
Status
Not open for further replies.

Forum statistics

Threads
111,995
Messages
590,194
Members
164,934
Latest member
bunthoeun.may