We do this with the Patton's via a dialplan entry but I don't mess with the Cisco/Linksys stuff so I can't say how flexible that is. They do have manuals and forums for this kind of thing and you will probably find your answer pretty quickly in their forums.
Another route I've tried with mixed results... put the gateway and the ATA/User in a different branch and try to get the branch to handle the gateway permissions. It looks like this is "broken" or not finished yet though, and there are JIRA's on it. On Wed, Feb 1, 2012 at 10:58 AM, Robert B <[email protected]> wrote: > Tony, > > That's what I thought. The SPA3102 fully supports T.38, although it looks > like the provisioning profile in SipX does not include the options, so > manual configuration is likely. Or at least partial manual. > > Not too worried, as long as it will negotiate T.38 with the > termination/origination provider (that properly supports T.38) and play > nicely, then we're good. > > Now the question is -- how can I have the ATA add a dialing prefix > automatically so I can create a custom Fax dialplan in SipX... :D > > -- Robert > > > > > On 2/1/2012 9:50 AM, Tony Graziano wrote: >> >> sipxbridge does not block the codec. >> >> at the same time the question is really a half question: >> >> if the ATA is configured to handle t.38, you can connect a fax machine to >> it (and even register it to sipx if it is capable) and send a fax from the >> plain paper fax machine to a unified messaging fax account on sipx. >> >> At the same time, if the DID (PSTN call) points to the ATA registered >> device and the call is from a sip trunk provider who properly handles t.38 >> (i.e., it works to a unified messaging account on sipx) the fax machine will >> also handle the inbound fax. It also would not matter if the PSTN gateway >> was a POTS line or PRI, as long as the PSTN facing gateway handles t.38 >> properly. >> >> I cannot attest to the model you are using. We do this with Patton >> gateways/PRI and FXS devices and it just always works. >> >> The ATA WILL ABSOLUTLEY INTERFERE if it is not t.38 capable or configured >> properly. Also, since the inbound or outbound call has to negotiate a >> codec, the UA must support t.38. Sipx DOES NOT transcode this. It has to be >> natively available and offered on both ends of the call. > > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
