[ADD] sms_twilio: new SMS provider #224898
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
robodoo
added
forwardport
|
cherrypicking of pull request #206818 failed. stdout: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?). In the former case, you may want to edit this PR message as well. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
8c36dc9 to
3e014d8
Compare
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
3e014d8 to
a68552a
Compare
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
a68552a to
a006cdd
Compare
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
ea0f4a8 to
6567bbc
Compare
1 similar comment
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
6567bbc to
4c41bf6
Compare
Current situation We provide a SMS service for our clients through an IAP service. I has almost no annoying configuration, the Odoo database sends data to an IAP proxy, that sends the SMS to our providers for them. It is easy to use and user friendly. Issue For this to work, Odoo "registers" itself to our providers in behalf of our clients. The problem with Mobile operators in many countries it is often asked for the clients to register themselves and submit an authorization request to be able to send SMS on their network. As such, Odoo is not supposed to register itself in place of their customers. In some countries like USA, Australia, UK and soon France this service is not working well or even at all. Solution Registration process is fastidious, and on top of them it changes from country to country. We do not want to start implementing registration processes by countries just for SMS sending. For that reason, we will start to provide a new module where we remove the IAP part and connect directly to a new provider: Twilio. Clients will do all the registration themselves directly with the provider, and setup their account in Odoo to send those SMS. Twilio is a well known provider with extensive coverage, ideal for a global solution like Odoo. Stable target This module targets 17.0 which is going to be the oldest supported version soonish. It is going to be forward ported until master. It should be stable compliant and should not break any flow involving IAP contact. Bridge support for SMS marketing and therefore marketing automation is provided. Task-4658352 X-original-commit: aa04aeb Co-authored-by: Thibault Delavallee <tde@odoo.com>
It should always belong to a company, hence making the field required and made deletion cascading. Task-5053537
Purpose is to test support and propagation of various errors in tests. Task-5053537
'success' or 'sent' can be received when succeeding, leading to a more correct notification message. Task-5053537
tde-banana-odoo
force-pushed
the
18.0-17.0-sms-twilio-rigr-430781-fw
branch
from
4c41bf6 to
b41b829
Compare
|
@robodoo override=ci/security See #206818 (review) |
|
@robodoo r+ rebase-ff |
|
Merge method set to rebase and fast-forward. |
|
child PR #224899 has become a normal PR because head updated from 85af790d1ad0656a76c353f9e7bf0bb54336f9f7 to 30a13abdf27d0f1886ae23ce1f7c182749e0f80d. This PR (and any of its parents) will need to be merged independently as approvals won't cross. |
robodoo
pushed a commit
that referenced
this pull request
Aug 31, 2025
Current situation We provide a SMS service for our clients through an IAP service. I has almost no annoying configuration, the Odoo database sends data to an IAP proxy, that sends the SMS to our providers for them. It is easy to use and user friendly. Issue For this to work, Odoo "registers" itself to our providers in behalf of our clients. The problem with Mobile operators in many countries it is often asked for the clients to register themselves and submit an authorization request to be able to send SMS on their network. As such, Odoo is not supposed to register itself in place of their customers. In some countries like USA, Australia, UK and soon France this service is not working well or even at all. Solution Registration process is fastidious, and on top of them it changes from country to country. We do not want to start implementing registration processes by countries just for SMS sending. For that reason, we will start to provide a new module where we remove the IAP part and connect directly to a new provider: Twilio. Clients will do all the registration themselves directly with the provider, and setup their account in Odoo to send those SMS. Twilio is a well known provider with extensive coverage, ideal for a global solution like Odoo. Stable target This module targets 17.0 which is going to be the oldest supported version soonish. It is going to be forward ported until master. It should be stable compliant and should not break any flow involving IAP contact. Bridge support for SMS marketing and therefore marketing automation is provided. Task-4658352 X-original-commit: aa04aeb Part-of: #224898 Related: odoo/enterprise#93569 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com> Co-authored-by: Thibault Delavallee <tde@odoo.com>
robodoo
pushed a commit
that referenced
this pull request
Aug 31, 2025
It should always belong to a company, hence making the field required and made deletion cascading. Task-5053537 Part-of: #224898 Related: odoo/enterprise#93569 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
robodoo
pushed a commit
that referenced
this pull request
Aug 31, 2025
Purpose is to test support and propagation of various errors in tests. Task-5053537 Part-of: #224898 Related: odoo/enterprise#93569 Signed-off-by: Thibault Delavallee (tde) <tde@openerp.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We provide a SMS service for our clients through an IAP service. It has almost no annoying configuration, the Odoo database sends stuff to an IAP proxy, that sends the SMS to our providers for them. Cool, easy, it's used quite a bit.
BUT for this to work, Odoo "registers" itself to our providers in the name of our clients. The problem is that the situation with Mobile operators in many countries is rapidly evolving, and more and more countries now require the clients themselves to submit an authorization request to be able to send SMS on their network. As such, Odoo is not supposed to register itself in place of its client. In some countries (and big ones, like USA, Australia, UK and soon France), this service is not working well, or at all, anymore.
The registration process is fastidious, and on top of them it changes from country to country. We do not want to start implementing registration processes by countries just for SMS sending.
For that reason, we will start to provide a new module where we remove the IAP part and connect directly to a new provider: Twilio. Clients will do all the registration themselves directly with the provider, and setup their account in Odoo to send those SMS. Twilio is a well known provider with extensive coverage, ideal for a global solution like Odoo.
task-4658352
Forward-Port-Of: #206818