Re: [asterisk-users] PJSIP T.38 issues

2015-08-01 Thread Jean-Denis Girard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 30/07/2015 13:20, Larry Moore a écrit : Was it enabling alaw/ulaw which helped or did you need to use another method to route the IAX channel through PJSIP or some other configuration setting such as 'faxdetect' which may have been disabled ?

Re: [asterisk-users] PJSIP T.38 issues

2015-07-30 Thread Larry Moore
On 29/07/2015 12:13 PM, Jean-Denis Girard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for your reply Larry. Le 27/07/2015 01:22, Larry Moore a écrit : I think the 488 Not acceptable here is occurring because the channel connecting through is not T.38 capable, that will be the

Re: [asterisk-users] PJSIP T.38 issues

2015-07-28 Thread Jean-Denis Girard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for your reply Larry. Le 27/07/2015 01:22, Larry Moore a écrit : I think the 488 Not acceptable here is occurring because the channel connecting through is not T.38 capable, that will be the IAX channel from iaxmomdem. This is what

Re: [asterisk-users] PJSIP T.38 issues

2015-07-27 Thread Larry Moore
I think the 488 Not acceptable here is occurring because the channel connecting through is not T.38 capable, that will be the IAX channel from iaxmomdem. I've not used PJSIP so cannot offer any advice regarding it however you may try to make iaxmodem connect through another context using

[asterisk-users] PJSIP T.38 issues

2015-07-26 Thread Jean-Denis Girard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi list, 2 weks ago I asked questions about PJSIP and T.38 but got no replies. I upgraded Asterisk to git as of yesterday (309dd2a), and I'm still having the same issues. In the trace below, I'm sending a fax from Hylafax server through iaxmodem on