Re: FAX on H.248/MEGACO

"Gunnar Hellstrom" <[email protected]>
Newsgroups gmane.ietf.megaco
Message-ID <000a01c8f59e$60081740$211ea8c0@GunnarH>
H.248.2 also has the details on fax detection / T.38 procedure.
 
 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
[email protected]
Sent: Thursday, July 31, 2008 5:13 PM
To: [email protected]
Subject: Re: [Megaco] FAX on H.248/MEGACO


Appendix III (H.248 call establishment procedure examples for
facsimile-capable media gateways) from T.38 Spec should have what you are
looking for. I am looking at draft in force (04/2007).

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
Andre Rosa Stefanini
Sent: Thursday, July 31, 2008 10:02 AM
To: [email protected]
Subject: [Megaco] FAX on H.248/MEGACO



Hi,

 

I've been asked about something not clear on specs: When a MG receives fax
and/or modem tones on RTP port, it should change the codecs in order to
allow tones to be passed in a correct way to be decoded as a fax or modem in
the other side. There are some options (i.e. using G.711 or T.38). This way,
the MG which detected the fax tone must set up a new codec. For this, we
have two options: automatic or negotiated. 

It's not clear on RFC which of these options is mandatory for the MG, or if
both of them. Could you help me with this?

Would someone could provide call-flows regarding fax/modem detection?

 

Thanks,

ANDRE

 

 

 



__________ NOD32 3311 (20080730) Information __________

Detta meddelande dr genomsvkt av NOD32 Antivirus.
http://www.nod32.com

_______________________________________________
Megaco mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/megaco
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.