[Asterisk-Dev] Fax support?

[Bruce Ferrell]

Noodling around on the ITU site, google and packetizer, it would appear 
T.38 is pretty tightly tied to H.323 as a "codec" (ITU puts it in there 
with 261/263/723.1 etc)

I suspect under SIP it would have to show up as a modem 
passthrough/relay over G.711

Steve Underwood wrote:
> Bruce Ferrell wrote:
> 
>> Good thing I don't give into knee jreck reactions... Too often.
>>
>> T.38 really is a type of codec isn't it.  Odd that I'd never looked at 
>> it that way.
> 
> 
> Yes and no. The audio-to-data part is structurally little different from 
> any voice compression codec. T.38 includes UDP and TCP wire protocols, 
> though. These do not fit the model of a codec. I think T.38 supports 
> needs to be in 2 parts - a codec and a channel. This should be good for 
> the future, since a variant using RTP has been proposed. That would 
> allow the T.38 codec part to work with the normal RTP stuff in * later on.
> 
> Regards,
> Steve
> 
>> Thanks  JerJer
>>
>> Jeremy McNamara wrote:
>>
>>> Leo D'Angelo wrote:
>>>
>>>> Hi Steve,
>>>>
>>>> Thanks for the response.  I agree with your assessment that t.38 
>>>> should be a
>>>> codec not a channel.  I was actually thinking of simply adding it as 
>>>> a codec
>>>> to the openh323 channel already provided with *...
>>>>
>>>> I don't know enough about the structure of * (yet) to figure out how 
>>>> a sip
>>>> request for a t.38 codec would work if I implemented t.38 as part of 
>>>> the
>>>> h.323 channel...  Any advice?  Maybe it really needs to be a separate
>>>> codec...
>>>
>>>
>>>
>>> It wouldn't.  Implement it as a separate codec in asterisk.
>>>
>>>
>>> Jeremy McNamara
>>
>>
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>