[asterisk-users] T.38 not working - help needed with log interpretation

[Larry Moore]

On 11/12/2014 4:52 PM, Recursive wrote:
> Hello,
>
> at first, thanks for helping!
>
> In the meantime, I have done a lot of research and trial and error, and I could solve that specific problem. Obviously, the dialplan application "Answer" was playing a key role here. My original dialplan snippet (which produced that problem) was:
>

You may very well find getting T.38 working in your environment in a way 
you would like will consume a large amount of your time, you will also 
find yourself doing a lot of research. What you should have found out by 
now (or perhaps deduced) is that the T.38 is a standard that is varied 
thus one cannot be assured a T.38 solution will always work.

> exten =>  _00., 1, NoOp()
>    same =>  n, Set(FAXOPT(gateway)=yes)
>    same =>  n, Dial(SIP/${EXTEN}@27XgY8YwfI2S9NAg)
>    same =>  n, Hangup()
>
> The problem vanished when I changed that to:
>
> exten =>  _00., 1, NoOp()
>    same =>  n, Answer()
>    same =>  n, Progress()
>    same =>  n, Set(FAXOPT(gateway)=yes)
>    same =>  n, Dial(SIP/${EXTEN}@27XgY8YwfI2S9NAg)
>    same =>  n, Hangup()
>

One may assume this is your dialplan for the outgoing connection with 
which you want T.38 to be supported.

To obtain better assistance you will need to include information such as 
what the local T.38 endpoint is and how it connects to your system. If 
it is in fact a T.38 capable endpoint then you should setting 
FAXOPT(gateway) to no. having Answer() & Progress() for an outgoing T.38 
connection doesn't seem to make sense to me!

You should also include information relating to your SIP configuration 
(with appropriate obfuscations) for the connection to peer 
27XgY8YwfI2S9NAg as well as what T.38 options you have set in the 
general section of sip.conf.

Larry.