No. The provider is not offering true t.38. If thy send it via g711 to the t1 and convert it locally it will be very unreliable unless it originates and gets sent all the way thru as t.38.
I've never found g711 very reliable. Thusly, sipx aims to use t.38 ONLY because it is really the ONLY way to transmit or receive faxes via sip. If you had a traditional PRI this would also work very well already. On Apr 24, 2011 7:44 PM, "[email protected]" <[email protected]> wrote: > On Sun, 24 Apr 2011 19:19:45 -0400, Tony Graziano wrote: >> You must have the email address of the user filled out in Unified >> messaging and create a FAX extension. In your case you want a DID >> number in the fax section in its proper place. > > That confirms we're good with the setup but wanted to check just in case. > >> Sipx ONLY supports t.38. So if your provider supports t.38, it should >> work just fine. > > This is where things get weird. > > The provider asked what protocol we wanted for SIP traffic but they don't provide end to end SIP services, it's only between their own on site route back to their network. They don't yet offer the usual SIP trunks. > > I specified G.711 to cover the bases until I find a T.38 solution for my fax server but incoming in my main concern which is why I had a sudden need for 4.4.0. > > Thing is, they are handing off a standard PRI trunk to the mediant so faxes and calls are coming in over G.711. > Can the mediant work any magic that sipx would accept? > > > > >> On Sun, Apr 24, 2011 at 6:35 PM, [email protected] <[email protected]> >> wrote: >>> The wiki seems to touch on lots of troubleshooting but I can't seem to >>> find an answer on the following. >>> >>> The new 4.4.0 system is connected to what sounds to me like a weird >>> hybrid setup. >>> >>> The provider has a T1 line between their network and the system site. >>> At the site, they are using a router which is breaking out to a full T1 >>> and a dynamic PRI. >>> The PRI is connected into a mediant 2000 which in turn will talk with the >>> 4.4.0 sipx box. >>> >>> The hybrid part to me is that the PRI portion should simply be that, a >>> PRI, yet, they needed us to specify the protocol to use between the >>> router and their site. Options were G.729 with T.38 (preferred) but I >>> went with G.711 to make sure that fax calls would be covered until I can >>> find a T.38 solution. >>> >>> So at the moment, I'm trying to figure out what we need to do in order to >>> receive faxes onto sipx. We can hear a fax tone but it's not the usual >>> continuous tone waiting for a reply which means to me, something isn't >>> right. I'm not assuming that because of this it means that the mediant is >>> set correctly but it does still pass faxes on to our fax server as well. >>> >>> I haven't followed topics lately so lost track. I believe faxing is >>> incoming to email only, which is all I want but I've not finding anything >>> on if sipx is using a specific protocol such as T.38 or G.711. I've read >>> that it does handle T.30 I believe. It sounds like only T.38 is being >>> supported. >>> >>> Can someone enlighten me about this and what I might be missing to make >>> this work. Voice calls are now working fine in and out. >>> Has anyone put out a document on how this works, something that isn't >>> just threads of troubleshooting but more of an end user guide. >>> >>> Mike >>> >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
