> Not a "great idea" to try to separate voice/fax calls. Using separate DID's > would be better.
That's just it, right now, users are used to being able to use just the single DID for both voice and fax calls and that to me, really is unified communications. Of course, the faxing portion takes up resources, which I don't want to take away from the users so while I want voice/fax over the same DID, I want to send each one to something different. > Use a Patton PRI gateway, they work tremendously well. You can take certain > DID numbers and re-route to a FXS gateway, which could in turn be used to > dial a Multi-tech digit finder (rebroadcasts digits) connected to a fax > finder, giving you a diskless fax method (emailed as pdf). Problem is, if I use two DIDs per person, then that's not going to be an issue, easy enough to route calls based on DID. But being able to distinguish between a voice and fax call over the same DID and routing that to a different server, that's my challenge at the moment. > Easier still... host the faxing somewhere else. Noone seems to be able to > properly support t.38 yet, but if it comes in over PRI, you ought to handle > it as t.38 as far as you can. I've had great luck with T.38 over SIP trunks to date, it's always worked. I expected to have a lot of problems but still wanted to test it and I can't say we've missed even one fax. > We used to have fax to did over a siptrunk, but then the ITSP kept breaking > it. Right, that is a problem for sure and yes, I'll be using PRI only so should not have as many problems. I'll look into the Patton also, thanks for the suggestion. Mike
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
