View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000026 | Pax Fax | Pax Fax | public | 2025-04-05 07:33 | 2025-04-29 05:05 |
| Reporter | titanium | Assigned To | |||
| Priority | high | Severity | block | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000026: Phaxio api and dashboard no longer exist for new users. They have been assimilated into Sinch. | ||||
| Description | There is no way to get access to a Phaxio dashboard anymore, it has been moved to the Sinch dashboard now. The api/documentation is now different. https://developers.sinch.com/docs/fax/v2-v3migration/ Some instructions for the Pax Fax app seem to be similar: For the "Phaxio API Key" and "Phaxio API Secret" I put the Key/Secret from Sinch. However, for the "Phaxio Webhook Token" it instructs to go to the Phaxio account, click 'Webhooks' on the left panel, then copy the token found under 'Webhook Token'. There seems to be no corresponding Webhooks section on Sinch. Where to get a Sinch webhook that will work with Pax Fax? Same question goes for the Phaxio Callback URL - what to replace it with? Much appreciated. | ||||
| Steps To Reproduce | Go to https://developers.sinch.com/docs/fax/v2-v3migration/ If you attempt to register by pressing sign up on https://console.phaxio.com/sf_guard_users/sign_in - it redirects you to https://sinch.com/apis/fax-api/ You can register on the new dashboard here - https://dashboard.sinch.com/signup | ||||
| Tags | No tags attached. | ||||
|
|
I've just tested logging in to phaxio.com and sending and receiving faxes from Pax Fax. Everything works as usual. Existing phaxio.com accounts work as expected with Pax Fax. Yet, what you mention above is perfectly true: when a new customer tries to open a new phaxio.com account, he is redirected to sinch.com and if he signs up for a new account there, he finds a new dashboard, where he can't find many of the fields that existed on Phaxio's dashboard, such as the 'Webhook Token' field. According to this page: https://developers.sinch.com/docs/fax/v2-v3migration/ it seems that phaxio.com accounts will have to migrate to sinch.com accounts and all the apps that connected to phaxio.com will have to transition to connecting to sinch.com, with all the necessary changes imposed by their API. Sinch's dashboard loads very slowly and seems unintuitive and Phaxio should have informed their existing customers about the upcoming transition, therefore, I'll have to investigate further and decide if I change Pax Fax to connect to sinch.com, or renounce to phaxio/sinch entirely and connect Pax Fax to other better and cheaper fax provider, such as Telnyx. |
|
|
Thank you for taking a quick look. I see, it's good that it still works for people with existing Phaxio accounts for the time being. That being said, as you have seen, this makes Pax Fax unusable for new people. I need to let my team know whether we can expect to use Pax Fax in the near future, or whether we need to let go of our idea of using Nextcloud for faxing. For us, it doesn't matter if it will be Telnyx or Sinch, just as long as Pax Fax will begin working. Can you please provide a rough estimate of whether it will take you just a few weeks or perhaps many months to make the modification to the Pax Fax app? That way I can bring something back to my team. Thanks again! |
|
|
I've asked Phaxio about this transition to Sinch's API that they didn't announce, and I'm waiting their reply tomorrow. I remember that Telnyx has discontinued basic authentication for HTTP requests to their API, which makes receiving faxes from them inside Nextcloud impossible. Many years ago, when I chose Phaxio as fax provider for Pax Fax, they were the best provider because they offered reliable services at the cheapest price possible: $2 per month for a phone number and 7 cents per sent and received page. All the other providers, like eFax, myFax, iFax, Fax.Plus etc. had a much higher monthly ongoing cost, like $10, or more. Why should a small business pay $10 or more each month just to be able to send a few faxes per year? Meanwhile, Telnyx added faxing to their voice and SMS services and they became 'the best provider' but as I mentioned, they can't be used to receive faxes inside Nextcloud. So, Phaxio remains a good choice for Pax Fax. Yet, sooner or later all apps will have to transition to Sinch's API. According to this page: https://sinch.com/apis/fax-api/ , a fax page will cost only 4.5 cents, as opposed to 7 cents with Phaxio. A US fax enabled number will cost $0.88 per month, as opposed to $2 per month with Phaxio. So, if Sinch's API is as reliable as Phaxio's and if their dashboard gets a bit faster, Sinch seems actually better than Phaxio. Since I consider being able to send and receive faxes inside Nextcloud very important, I plan to change Pax Fax to make it support both API's, in the sense that I'll add a new section on the Settings page, where each new user will enter his Sinch credentials in order to use them to send and receive faxes connecting to Sinch's API, while old users will continue to use their Phaxio credentials on the Settings page to send and receive faxes as usual, until they find the time to port their phone numbers from Phaxio to Sinch. Also, the documentation will have to change, to show users where to find the necessary credentials on Sinch's dashboard. I can't tell exactly how much time the code changes will take, since it also depends on other factors, such as on Sinch's support response time, but it definitely shouldn't take too long. I suppose about two weeks. I'll post a reply on this thread once I finish. |
|
|
Great, thank you. I appreciate the details and that you will attempt to get it done fairly quickly. We'll be waiting! Cheers |
|
|
Pax Fax version 1.1.9 has been published. After you upgrade, enter your Sinch credentials on the Settings page. You can test by sending a one page pdf file to your own number. As I was expecting, Sinch support delayed this new version quite a bit. |
|
|
Thanks! Will check it out soon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-05 07:33 | titanium | New Issue | |
| 2025-04-05 10:02 | DoubleBastionAdmin | Note Added: 0000101 | |
| 2025-04-06 03:03 | titanium | Note Added: 0000102 | |
| 2025-04-06 13:04 | DoubleBastionAdmin | Note Added: 0000103 | |
| 2025-04-06 14:07 | titanium | Note Added: 0000104 | |
| 2025-04-25 06:52 | DoubleBastionAdmin | Note Added: 0000105 | |
| 2025-04-25 06:55 | DoubleBastionAdmin | Note Edited: 0000105 | |
| 2025-04-29 05:05 | titanium | Note Added: 0000106 |
