SIP to Virtual Fax Modem
-
@Dashrender said:
of course not, but you could have just that SIP trunk go to this FreePBX to accept incoming faxes... I'm not sure how you would handle outgoing ones.
That's extra complication for no reason, why add a second PBX to it? There's already paid software that does the virtual modems I'm just looking to see if there's a free SIP Modem before I buy one.
-
@Dashrender said:
I'm not sure how you would handle outgoing ones.
We already do both incoming and outgoing over the phone system currently.
-
You were asking for a free solution - so I gave you one.
What software is running behind the analog modems you have now? Are you trying to find something that will plug directly into the analog modems place behind that software?
-
@Dashrender said:
What software is running behind the analog modems you have now? Are you trying to find something that will plug directly into the analog modems place behind that software?
No software they are USB modems plugged into a Cisco VG320 to setup. It's just using windows fax server. We want to free up some of the VG320 for more console ports (remote access to routers and switches) and find a SIP -> Virtual Modem software.
Similar to t.38 but hoping to find a free ware or opensource one.
-
Now I'm really lost - I thought t.38 was the desired SIP protocol for Faxing?
Though I recently read some posts saying that t.38 wasn't all it was cracked up to be.. and other normal SIP protocols were just fine for faxing - I don't know what the truth is.
Do you still need/want the SIP trunks to terminate into Windows Fax?
-
Yes I still want to do it this way. And now it does not terminate into windows fax. It creates a virtual modem.
Similar to these
http://www.eltima.com/products/virtual-modem-pro/
http://www.t38faxvoip.com/buy.htm -
@Dashrender said:
Now I'm really lost - I thought t.38 was the desired SIP protocol for Faxing?
g.711u sometimes actually works better.
-
@Dashrender said:
Now I'm really lost - I thought t.38 was the desired SIP protocol for Faxing?
I was referring to the t.38 software not the protocol.
-
@Dashrender said:
Though I recently read some posts saying that t.38 wasn't all it was cracked up to be.. and other normal SIP protocols were just fine for faxing - I don't know what the truth is.
That all of it works sometimes, none of it works always and faxing (digital over analogue over digital) is a bad idea.
-
@scottalanmiller said:
@Dashrender said:
Though I recently read some posts saying that t.38 wasn't all it was cracked up to be.. and other normal SIP protocols were just fine for faxing - I don't know what the truth is.
That all of it works sometimes, none of it works always and faxing (digital over analogue over digital) is a bad idea.
You have have had a bad experience then we do all faxing at a very large scale over our phone system.
-
@Jason said:
You have have had a bad experience then we do all faxing at a very large scale over our phone system.
Not really, it's just a fact that the protocols are not entirely reliable as the mechanisms for traditional fax reliability do not work when going through DA and AD conversions. It mostly works, but when you do PBX consulting, "mostly" rarely cuts it with customers. The expectations that it will match traditional reliability is the problem. VoIP beats traditional reliability while FoIP falls short.
-
I can't be positive, but I'm guessing that our EHR provider has FoIP solution. When we switched to all faxes going directly to them, the number of bad fax calls that we received spiked. The vendor refused to accept any responsibility in the problems either - saying.. well, it's working for the other 2000+ clients we have...
-
@Dashrender said:
well, it's working for the other 2000+ clients we have...
And they leave out...
- They have 10K clients.
- To other clients, you are listed as one of the "working" ones.
- Not complaining and working are not the same.
