- Joined
- Oct 18, 2024
- Messages
- 5
- Reaction score
- 1
I am having an issue where sending fax will not complete. I get a 603 error from my upstream trunk at Voip.ms. Receiving fax works just fine,and delivers over a grandstream ht801 ata to the fax machine.
I have created an outbound rule to make sure the fax machines are sending out on the correct trunk with the Fax DIDs. I can confirm this is working by reviewing the activity logs. The issue is once it sends out it sends a caller id of "false" to voip.ms and the transmission is dropped/denied.
I know this is the issue because in Voip.MS if I uncheck " I use a system capable of passing its own CallerID" and force a DID sending a fax does get a caller id and the fax goes through. Making a sip trunk and sub account in Voip.MS for each Fax DID and hard setting the caller id would be pretty cumbersome but would resolve this issue .
On the 3CX side why doesn't the Fax extension use the Caller ID I have set in Advanced > Fax under each fax extension? I have even tried forcing a caller ID in an outbound rule since 5 outbound rules would be better than 5 sip trunks for fax and that still does not attach the caller ID.
I saw in 3CX's fax/ata kb page that 3cx will serve as a stateless proxy for this connection, is that why it is not applying a caller id?
This part below from here: https://www.3cx.com/docs/sip-trunk-faxing/
Hosted on Version 20.0 Update 3 (Build 806 Release)
I have created an outbound rule to make sure the fax machines are sending out on the correct trunk with the Fax DIDs. I can confirm this is working by reviewing the activity logs. The issue is once it sends out it sends a caller id of "false" to voip.ms and the transmission is dropped/denied.
I know this is the issue because in Voip.MS if I uncheck " I use a system capable of passing its own CallerID" and force a DID sending a fax does get a caller id and the fax goes through. Making a sip trunk and sub account in Voip.MS for each Fax DID and hard setting the caller id would be pretty cumbersome but would resolve this issue .
On the 3CX side why doesn't the Fax extension use the Caller ID I have set in Advanced > Fax under each fax extension? I have even tried forcing a caller ID in an outbound rule since 5 outbound rules would be better than 5 sip trunks for fax and that still does not attach the caller ID.
I saw in 3CX's fax/ata kb page that 3cx will serve as a stateless proxy for this connection, is that why it is not applying a caller id?
This part below from here: https://www.3cx.com/docs/sip-trunk-faxing/
Code:
In this scenario, negotiation between the SIP Trunk Provider and the FXS/ATA Gateway, although proxy’d by 3CX, goes unmodified (3CX acts as a stateless proxy).
The same device can be used for Outbound faxing given that there is a matching Outbound Rule that enables this. Again, 3CX will not process or modify any packets.
Hosted on Version 20.0 Update 3 (Build 806 Release)
Last edited: