Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAJOR ISSUE: Twilio Fax Support Ending #16

Open
tywrenn opened this issue Dec 18, 2020 · 6 comments
Open

MAJOR ISSUE: Twilio Fax Support Ending #16

tywrenn opened this issue Dec 18, 2020 · 6 comments

Comments

@tywrenn
Copy link

tywrenn commented Dec 18, 2020

Unfortunately, Twilio made development difficult by ending fax support:

https://support.twilio.com/hc/en-us/articles/223136667-Fax-Support-on-Twilio

Now we need a replacement by December of 2021

@sjpadgett
Copy link
Member

Shouldn't be too hard to move the fax api to Documo and maybe a better solution. I'll help if you want to tackle.
Have you looked at cost Documo vs Twilio?

@adunsulag
Copy link
Member

@sjpadgett We probably need to update the README to say that any new clients of Twilio are disabled for fax, so until we have Documo support or something else, new clients should avoid using this package.

@sunsetsystems
Copy link
Member

I think Hellofax also has an API of some sort. Might be useful to look at what the different vendors are doing and see if their differences can be resolved with configuration parameters instead of vendor-specific code.

@sjpadgett
Copy link
Member

Adding vendors is actually pretty easy and almost automatic in implementation.
HelloFax looks reasonable(similar to RC pricing) where HelloSign can get pricey. mFax has nice pricing breakpoints and eFax appeared difficult to implement last I checked on their offering.

Still i'd need to reconfig for fax only, sms only, fax and sms(same vendor) or fax/sms dif vendors etc.

@juggernautsei
Copy link
Member

juggernautsei commented Mar 11, 2021

here is my recent experience with the module. When I get some time, I will look into other fax services. I am hoping this is a quick tweak to support composer 2.0.11.

 ubuntu@ip-172-31-27-136:/var/www/html/hb600$ composer require "openemr/oe-module-faxsms:2.2.0-beta"
 ./composer.json has been updated
 Running composer update openemr/oe-module-faxsms
 Loading composer repositories with package information                                                                                         Updating dependencies
 Your requirements could not be resolved to an installable set of packages.

 Problem 1
    - openemr/oe-module-installer-plugin[0.1.0, ..., 0.1.3] require composer-plugin-api ^1.0 -> found composer-plugin-api[2.0.0] but it does not match the constraint.
    - openemr/oe-module-faxsms v2.2.0-beta requires openemr/oe-module-installer-plugin ^0.1.0 -> satisfiable by openemr/oe-module-installer-plugin[0.1.0, 0.1.1, 0.1.2, 0.1.3].
    - Root composer.json requires openemr/oe-module-faxsms 2.2.0-beta -> satisfiable by openemr/oe-module-faxsms[v2.2.0-beta].

  You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.

   Installation failed, reverting ./composer.json and ./composer.lock to their original content.

@sjpadgett
Copy link
Member

composer require "openemr/oe-module-faxsms:2.2.0-beta"

Wrong version for v6.0.0(1)

You are using Composer 2, which some of your plugins seem to be incompatible with

That's the plugin https://github.com/openemr/oe-module-installer-plugin. Just composer down version the after install put v2 back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants