"Send fax via email" feature not available for any US providers - V20 Update 4 Build 487

[VictorYourITGroup]

Not to hijack the thread but since the people in it are using the fax system.
What is the advantage to using the fax system in 3CX as opposed to the ones offered by the providers?
Assuming client is ok with email to fax systems.

 

[SnakeRiverWebDevelopment]

Not to hijack the thread but since the people in it are using the fax system.
What is the advantage to using the fax system in 3CX as opposed to the ones offered by the providers?
Assuming client is ok with email to fax systems.

In our case it is just easer, no extra fees, we receive more than we send so it just make since. We use our providers API to send when needed.

 

[illcs]

For us it was the ability to eschew pots lines and save money on MRC and it just works very little or no issues in over 10 years of use.

 

[VictorYourITGroup]

In our case it is just easer, no extra fees, we receive more than we send so it just make since. We use our providers API to send when needed.

Oh! That makes sense.
Thanks for the clarification.

 

[YiannisH_3CX]

So, to get back to the original question, has anyone gotten this to work with a sip trunk connection they created in Version 20 Update 4 or higher (I upgraded to build 5 on one of my systems to see if that fixed it but no luck).

I do see people saying it's working and I can also confirm this should work as well. You need to either assign a DID to the fax server directly or create a fax forward to the email of an existing extension. If neither options work then some troubleshooting is in order.
Assign the DID to a normal extension which is not defined in the default destination of the trunk and call it. Does the call route to the correct extension? If so assign it back to the fax forward extension and start a pcap.
Is the inbound fax T38 or audio? Is the negotiation OK? If you are unsure about any of these and assuming you are using a supported provider, create a ticket with our support department so they can look into this.

 

[bitn2]

I can confirm that works like before. I just installed a new pbx with a new trunk und fax is working like charme.

 

[fortech]

Hi, in case this is still an active topic? (not 100% clear, is >1 mo later now).

For what it is worth. My usual simple FAX setup is
- get the FAX did ported to VoipMS / or if you are not confident, first purchase such a FAX DID and do some testing to pre-validate all that I say here.
- use preferred POP / they have many in USA-Canada and support DID in ~most parts of the world, good coverage in USA/Canada for sure.
- after that, I just don't even bother with 3cx getting involved in the FAX stuff. I get the feeling 3cx prefer people to not use 3cx for faxing more-or-less. For that matter I prefer if my clients don't get involved in faxing either (whoo! modern 1990's tech! wow, I can send it as if by courier, and it gets there NOW instead of same-day-later. so much cheaper than same-day courier as well. Sigh. yes, I know some workflow depend on fax, maybe we get rid of fax machines before the Y3K ? we shall see.)

anyhow. enough semi-rude tongue-in-cheek.
next then:

VoipMS have a nice simple web-admin portal, you may go here and setup
(a) FAX_TO_EMAIL config > so this routes inbound faxes to what destination email address you designate
and then
(b) EMAIL_TO_FAX config -> allows your team in the office to easily route outbound faxes via email, ie, "Here is a PDF, drag and drop to outlook, send it to the gateway address email recipient at voip.ms . and designate the FAX recipient as part of subject line of message / as per the hints doc at voip.MS

(c) IF you are feeling like more fun, and want to support legacy FAX machine or MFP>FAX outbound over analog line, then find yourself an ATA you don't hate, configure it as a SIP Client against a SIP sub account on VoipMS and then allow the legacy physical fax scan machine to squeeze the faxes out via analog > ATA > Landline > VoipMS is your carrier > terminates the call to the external FAX ## and you send the physical paper fax out this way. Ugh, so much fun but it generally works. I've setup various Sipura, Cisco, Handytone over the years in this sort of config, generally 'it just works' unless someone kicks the power plug for the ATA or something like that.

clearly the email-to-fax and fax-to-email are a bit cleaner IMHO but some workflows still depend on physical paper I realize (sigh)

Tim

 

[voyant]

I am still unable to create a trunk that will forward to the fax server or deliver a fax to an email with V20. I have tried this on new systems and old systems. I have tried it with preferred SIP providers and other providers. The Route setting does not include any fax options when creating the trunk.

Has anyone been able to do this in the last 4 months with a new trunk?

 

[YiannisH_3CX]

The Route setting does not include any fax options when creating the trunk.

Yes the Default route in the trunk does not offer any fax options because the proper way to do this is either by assigning a DID to the fax server or creating a fax forward.

Has anyone been able to do this in the last 4 months with a new trunk?

Multiple people have confirmed this is working and I have offered multiple troubleshooting steps above. Did you follow any of them? If so what did you try and what were the results? Give us some information so we can help you.

My guess is you are having call source identification issues and the call does not route where you assign the DID and it always routes to the default route of the trunk.

 

[voyant]

I am using a trunk with a single DID. I can not route it to a fax forward extension or a fax server as these options are not available. I am forced to route it to a user extension. I have tried assigning the DID to the fax server and the call still goes the user extension identified as the default route for the trunk. I have assigned the DID to fax forwarders and the calls still follow the default route. what needs to happen to get the system to ignore the default route and send the call to either the fax forwarder or the fax server?

 

[NicholasP_3CX]

I am using a trunk with a single DID. I can not route it to a fax forward extension or a fax server as these options are not available. I am forced to route it to a user extension. I have tried assigning the DID to the fax server and the call still goes the user extension identified as the default route for the trunk. I have assigned the DID to fax forwarders and the calls still follow the default route. what needs to happen to get the system to ignore the default route and send the call to either the fax forwarder or the fax server?

You essentially need to have the DID assigned in the correct format. See my response for a similar situation here

Solved Thread 'Individual DDI is not working'

Apr 8, 2025

Hi All,

I have new Multitenant PBX installed.

The issue here is Main SIP trunk is working but i have couple of Individual DID numbers are not working , by default pointing to default route.

I have more than 25 more PBXs which worked perfectly, All the trunks on generic SIP Trunk works fine.

One different I can see between working and non working on multitenant, doesn't support (Asterisk) *122334 , I need to add ISD code +353(Ireland) example,

Could any one help here, please?

Thanks
Rajan

• rajan
• did pointing to default route
• Replies: 8
• Forum: Phone System / PBX