Aunque la esperada versión de Asterisk 1.8 no verá la luz hasta dentro de muy pocos meses, nos empiezan a llegar algunas novedades sobre las mejoras que se están preparando entre ellas la incorporación de una mejora considerable en el soporte de Fax (principalmente el soporte de T.38) que en Asterisk 1.4 era bastante rudimentario (únicamente permitía pasar paquetes T.38 mediante SIP e incluso tenía ciertas incompatibilidades en función del tipo de gateway que se utilizara), y en Asterisk 1.6 se mejoró un poco aunque seguía sin ser todo lo que realmente se esperaba de él (la implantación de Steve Underwood con la creación del spandsp y de algunos módulos extras permitieron mejorar este soporte, aunque no era todo lo que en un principio se esperó que fuera) y se espera que en Asterisk 1.8 se pueda contar con un soporte completo de faxes(tanto de T.30 -la forma habitual a través de audio- como de T.38 -digitalizando el fax y permitiendo una confirmación de recepción lo que aseguraría el envío y la recepción de faxes entre dispositivos que utilizan este protocolo-).
Kevin P. Flemming anunciaba el otro día que varios desarrolladores de Digium se habían puesto manos a la obra para plantear y empezar a desarrollar un soporte en condiciones para los faxes (pese a que utilizar faxes, es y seguirá siendo, una tecnología totalmente obsoleta y que debería desaparecer).
Gracias a la experiencia obtenida por el desarrollo del módulo comercial Fax for Asterisk de Digium que mejora considerablemente la velocidad y la calidad de envío y recepción de faxes (que por cierto, parece ser que ya es compatible con sistemas de 64bits), Asterisk 1.8 contará con una implementación similar utilizando un stack propio de forma que este soporte sí se pueda licenciar como un producto GPL y pueda integrarse en la próxima versión de Asterisk.
De forma que, aunque en Asterisk 1.6 el soporte de Faxes es ya bastante bueno, Asterisk 1.8 contará con un soporte mucho mejor y que hará las delicias de aquellos usuarios que utilicen faxes.
Mostrando las entradas con la etiqueta Fax. Mostrar todas las entradas
Mostrando las entradas con la etiqueta Fax. Mostrar todas las entradas
lunes, 26 de abril de 2010
Release de Digium's Fax For Asterisk 1.2
Hola luego de varios días de no publicar nada de Voz Ip y Asterisk hoy volvemos con varios post con respecto a este tema, espero que los disfruten los hallen de utilidad, aquí esta la versión en ingles la verdad me dió pere traducir la madre jajajaja
In Digium’s continuing quest to deliver you, our users of Free Fax For Asterisk, and our customers of Fax For Asterisk, with the best possible solution, we are pleased to announce the availability of version 1.2 of…(drum roll without suspense) Fax For Asterisk.
How has this version improved? Why, with new features, of course, hence the title of this blog post.
New features include:
DAHDI Buffer Policy Implementation -Currently requiring the trunk version of Asterisk, in addition to the 1.2 release of Fax For Asterisk, new dialplan functions to allow the setting of buffer policies to prevent fax failures on higher latency systems, e.g.:
exten => 1234,Set(CHANNEL(buffers)=”12,half”)
where “12? represents a number of buffers (each buffer is 20ms), configurable between 4 and 32, and where “half” represents the policy implementation, configurable as “immediate,” “full,” or “half.”
To use, simply set your buffer policy in your dialplan before any send/receive fax operation across a DAHDI channel.
SIP Fax Detection Options -At present, also requiring the trunk version of Asterisk in addition to the 1.2 release of Fax For Asterisk, new options are available related to T.38 session initiation. Older releases of Fax For Asterisk only detect T.38 fax upon the receipt of CNG. In practice, we’ve discovered that a number of T.38 providers send T.38 invites immediately, and never send CNG to initiate a T.38 session. Thus, the faxdetect option in sip.conf can now be set to:
no – To disable all fax detection
cng – To trigger fax detection based on the receipt of a CNG tone
t38 – To trigger fax detection based on the receipt of a SIP T.38 invite, without CNG tone
yes – To trigger fax detection based on the receipt of either a CNG tone or a SIP T.38 invite.
These changes should improve our compatibility with the wild, wild west of T.38 implementations.
New CLI Commands -New Asterisk command line interface commands are available to display the settings configured in res_fax and res_fax_digium, simply run:
fax show settings
to see your current settings.
Asterisk CLI Type Column -A “Type” column is now displayed when “fax show sessions” is run on the Asterisk CLI, informing the user whether the fax is of type “G.711? or of type “T.38.”
ECM Configuration per Provider / Peer & Configuration Moved -Error correction mode may now be configured on a per provider / peer basis. This proves useful in the case that a provider does not implemented T.38 ECM properly. Digium has observed that ECM must be disabled for T.38 faxing to work properly with Gafachi.
Configuration of error correction mode has moved from res_fax_digium.com into the res_fax.conf configuration file. Note that the default setting is still to enable ECM.
SendFax initiate T.38 re-invite -Digium observed that a number of providers or far-end systems did not send a T.38 re-invite and instead waited for the local system (Asterisk) to send it instead. The SendFax application now supports the “z” option to enable this feature. If the “z” option is set during a SendFax, then res_fax will initiate the T.38 re-invite if it is not received in 10 (ten) seconds from the far end. Digium observed that the “z” option must be used for T.38 faxing to work properly with Gafachi.
Send / ReceiveFax G.711 Fallback mode -A new fallback option “f” has been added to the SendFax and ReceiveFax applications. In the event that T.38 negotiation fails, enabling this option will cause Asterisk to revert to audio fax mode. Digium has observed this is required for some providers, like BroadVox, who provide T.38 for inbound faxing, but accept only audio faxing for outbound.
Please note that audio faxing over the Internet is very unreliable, and Digium cannot provide support for fax failures due to poor Internet connections.
New Debugging utilities -In order to make debugging easier, we’ve added two new command line capture options, one for audio faxes and one for T.38 faxes.
For audio capture, do “set fax g711cap on” in the Asterisk CLI and a stereo wav file will be created for each fax session. The resulting files will be saved in /var/log/asterisk/g711cap. To stop capture, do “set fax g711cap off.”
For T.38 capture, do “set fax t38cap on” in the Asterisk CLI and a Wireshark compatible pcap file will be created for each fax session. The resulting files will be saved in /var/log/asterisk/t38cap. To stop capture, do “set fax t38cap off.”
Ready to upgrade? Run right over to the Fax For Asterisk Download Selector and grab the new release.
In Digium’s continuing quest to deliver you, our users of Free Fax For Asterisk, and our customers of Fax For Asterisk, with the best possible solution, we are pleased to announce the availability of version 1.2 of…(drum roll without suspense) Fax For Asterisk.
How has this version improved? Why, with new features, of course, hence the title of this blog post.
New features include:
DAHDI Buffer Policy Implementation -Currently requiring the trunk version of Asterisk, in addition to the 1.2 release of Fax For Asterisk, new dialplan functions to allow the setting of buffer policies to prevent fax failures on higher latency systems, e.g.:
exten => 1234,Set(CHANNEL(buffers)=”12,half”)
where “12? represents a number of buffers (each buffer is 20ms), configurable between 4 and 32, and where “half” represents the policy implementation, configurable as “immediate,” “full,” or “half.”
To use, simply set your buffer policy in your dialplan before any send/receive fax operation across a DAHDI channel.
SIP Fax Detection Options -At present, also requiring the trunk version of Asterisk in addition to the 1.2 release of Fax For Asterisk, new options are available related to T.38 session initiation. Older releases of Fax For Asterisk only detect T.38 fax upon the receipt of CNG. In practice, we’ve discovered that a number of T.38 providers send T.38 invites immediately, and never send CNG to initiate a T.38 session. Thus, the faxdetect option in sip.conf can now be set to:
no – To disable all fax detection
cng – To trigger fax detection based on the receipt of a CNG tone
t38 – To trigger fax detection based on the receipt of a SIP T.38 invite, without CNG tone
yes – To trigger fax detection based on the receipt of either a CNG tone or a SIP T.38 invite.
These changes should improve our compatibility with the wild, wild west of T.38 implementations.
New CLI Commands -New Asterisk command line interface commands are available to display the settings configured in res_fax and res_fax_digium, simply run:
fax show settings
to see your current settings.
Asterisk CLI Type Column -A “Type” column is now displayed when “fax show sessions” is run on the Asterisk CLI, informing the user whether the fax is of type “G.711? or of type “T.38.”
ECM Configuration per Provider / Peer & Configuration Moved -Error correction mode may now be configured on a per provider / peer basis. This proves useful in the case that a provider does not implemented T.38 ECM properly. Digium has observed that ECM must be disabled for T.38 faxing to work properly with Gafachi.
Configuration of error correction mode has moved from res_fax_digium.com into the res_fax.conf configuration file. Note that the default setting is still to enable ECM.
SendFax initiate T.38 re-invite -Digium observed that a number of providers or far-end systems did not send a T.38 re-invite and instead waited for the local system (Asterisk) to send it instead. The SendFax application now supports the “z” option to enable this feature. If the “z” option is set during a SendFax, then res_fax will initiate the T.38 re-invite if it is not received in 10 (ten) seconds from the far end. Digium observed that the “z” option must be used for T.38 faxing to work properly with Gafachi.
Send / ReceiveFax G.711 Fallback mode -A new fallback option “f” has been added to the SendFax and ReceiveFax applications. In the event that T.38 negotiation fails, enabling this option will cause Asterisk to revert to audio fax mode. Digium has observed this is required for some providers, like BroadVox, who provide T.38 for inbound faxing, but accept only audio faxing for outbound.
Please note that audio faxing over the Internet is very unreliable, and Digium cannot provide support for fax failures due to poor Internet connections.
New Debugging utilities -In order to make debugging easier, we’ve added two new command line capture options, one for audio faxes and one for T.38 faxes.
For audio capture, do “set fax g711cap on” in the Asterisk CLI and a stereo wav file will be created for each fax session. The resulting files will be saved in /var/log/asterisk/g711cap. To stop capture, do “set fax g711cap off.”
For T.38 capture, do “set fax t38cap on” in the Asterisk CLI and a Wireshark compatible pcap file will be created for each fax session. The resulting files will be saved in /var/log/asterisk/t38cap. To stop capture, do “set fax t38cap off.”
Ready to upgrade? Run right over to the Fax For Asterisk Download Selector and grab the new release.
Suscribirse a:
Entradas (Atom)