Chris, With T38, the simplest seems to be a one-step process: the call received from PRI is routed to the fax machine, with T38 enabled The 2 FS should not have any issue to talk T38. or to avoid T38 at all, as the others proposed, just find a way to transmit the fax as data (rsync, scp, ....) David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 21/05/2011 à 21:17, Chris Cureau a écrit :
Hi, everyone!
I am trying to implement a workable fax solution between two FreeSwitch servers. This is what I had in mind so far:
T1 PRI <--> Sangoma A102 <--> FreeSwitch (host) <--> T.38 SIP (internet) <--> FreeSwitch (remote) <--> Sangoma B600D <--> FAX machine
I am assuming here that the T.38 protocol between FreeSwitch servers will ensure that the data transfers between the two sites successfully. Would this actually be a two step process, where one server receives the fax (say, from the PRI) on one call, then sends to the second server, and the second server initiates a second call to the fax machine?
The object here is to successfully pass faxes using SIP. Is there a better way to handle this?
Thanks in advance, Chris _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org