For the records and others who may run into the same problem: Problem is solved. The external Hylafax was configured in a way that it was sending ath1 after initialization. After changing to ath0, modems are no longer considered as busy. Look for "onhook" in Freeswitch CLI after hangup. Best regards Peter On 06/26/13 22:20, Peter Steinbach wrote:
Hello,
according to the Hylafax wiki page we could set up 4 modems with Hylafax. We also used termnetd + interceptty to extend the modem interfaces to a remote Hylafax server. The interface works outbound: Fax from Hylafax to Freeswitch works. However bridging an incoing fax to modem/a/a fails very often. I we want to send a fax, right after the processes are started and modems are connected, it always fails with "no modems available". The same happens if we explicitely set an interface number, e.g. modem/1/a, which is available at that time.
However, after waiting a while, we can get a call through, an available modem is detected. It seems as if modems are detected, but they are not considered as available. Just after some time they may be released, in my opinion.
My questions:
* has anybody else had this issue? * does anybody know, how to workaround this? * maybe this is some behaviour of termnetd + interceptty? * what's the best way to debug this? I have not seen any Freeswitch command for mod_spandsp.
-- With kind regards Peter Steinbach
Telefaks Services GmbH mailto:lists (att) telefaks.de Internet: www.telefaks.de
-- With kind regards Peter Steinbach Telefaks Services GmbH mailto:lists (att) telefaks.de Internet: www.telefaks.de