It is great that 3CX has extended it's capability to include Facebook and SMS messaging.
I would like the ability to add our own SMS provider settings into 3CX for our customer base.
If it was implemented in a similar manner to the custom CRM extension / Generic SIP Trunk it would allow service providers to create an integration that's more suited to their operating environment, without requiring 3CX to add individual vendor support.
The CRM templates exhibit a comprehensive set of functionality which we believe would facilitate connectivity with most providers.
We would imagine it would look something along the lines of;
- a "Configuration" scenario that covers
* Configuring basic account information and numbers
* The ability to enter supported numbers, (or map them directly to an agent / extension)
* Providing the url that responses should come back to
- a "SendSMS" scenario which exposes;
* An agent to number mapping (assuming it was enabled for the extension or globally)
* The message being sent - allowing us to build an appropriate connection with the SMS provider
- a "ReceiveSMS" scenario that would;
* Allow an agent to be looked up, (or provided, based on the preconfigured mapping)
* Provide the ability to map fields from the response into the expected 3cx format
I would like the ability to add our own SMS provider settings into 3CX for our customer base.
If it was implemented in a similar manner to the custom CRM extension / Generic SIP Trunk it would allow service providers to create an integration that's more suited to their operating environment, without requiring 3CX to add individual vendor support.
The CRM templates exhibit a comprehensive set of functionality which we believe would facilitate connectivity with most providers.
We would imagine it would look something along the lines of;
- a "Configuration" scenario that covers
* Configuring basic account information and numbers
* The ability to enter supported numbers, (or map them directly to an agent / extension)
* Providing the url that responses should come back to
- a "SendSMS" scenario which exposes;
* An agent to number mapping (assuming it was enabled for the extension or globally)
* The message being sent - allowing us to build an appropriate connection with the SMS provider
- a "ReceiveSMS" scenario that would;
* Allow an agent to be looked up, (or provided, based on the preconfigured mapping)
* Provide the ability to map fields from the response into the expected 3cx format
Upvote
23
