| Cache писал(а): |
отчетик  встал нормально на 1.4.12. spandsp4pre9 ... |
Спасибо за отчет, сейчас переведу и отправлю на тррекер. Интересны естественно только результаты по G.711 =)
| Цитата: |
| Receivefax кодек g721 |
Шо це за зверь?
_________________
SuSE 10.1 / Asterisk-trunk / Celeron 1000 / chan_misdn (HFC)
Linksys PAP2T / SPA941 / SPA3102 / SPA2102
| IgorG писал(а): | ||
| |
| Цитата: |
| Receivefax кодек g721 |
Шо це за зверь?
так же 2 приложения отправки и приема факсов send и reseive
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
| Cache писал(а): |
| так же 2 приложения отправки и приема факсов send и reseive |
Не, он наверное про 721-й кодек спрашивал
_________________
Trixbox 2.2.x (Asterisk 1.4.11) / FXO шлюзы (Dynamix, OvisLink, Planet, etc) / разные IP-телефоны (OvisLink, Grandstream, Dynamix, Nokia, Cisco ATA-186, etc)
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
| Цитата: |
| steveu wrote: http://bugs.digium.com/view.php?id=10815#71517 The functionality for a T.38 gateway is completely different from the termination applications, so gateway operation seems a poor fit in the current code. What we did in Callweaver is to provide a new application - app_t83gateway.c - that is a bit like app_dial.c, but monitors for a T.38 call. When one is seen, it switches from simply passing audio/video/whatever through, to acting as a T.38 gateway. In this mode it receives and transmits audio on the PSTN side, and receives and transmits T.38 packets on the IP side. Of course, like rxfax and txfax, spandsp is doing 99% of the work, and app_t38gateway.c is very simple interface code. You need something in the system to actually figure out when a call requires T.38 facilities, and tries to negotiate it with the far end, through SIP, H.323 or MGCP. Remember that the called end is the one which is supposed to initiate this negotiation. Exactly how to add it to the system is left as an exercise for the reader.  |
прям как я только разжевал)))
| Cache писал(а): |
| он должен быть реализован вообще в ядре астериска по моему а в канале менять состояние только переменных по которым остальным приложениям ориентироваца. |
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
_________________
SuSE 10.1 / Asterisk-trunk / Celeron 1000 / chan_misdn (HFC)
Linksys PAP2T / SPA941 / SPA3102 / SPA2102
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
| Цитата: |
| Ok, it took a bit longer but here is the new version. New version available in 3 different alternatives: * v2-app_fax.c - just the new version of app_fax.c for these who already have makefile/configure/etc patched * v2-app_fax.c.patch - is just a unified diff of app_fax.c for those who want to see changes (or to apply them) * v2-full.patch - the full patch to be applied to freshly checked out asterisk-addons trunk (updated for latest trunk revision) The only significant change is adition of requested FAXSTATUS+FAXERROR variables which are set by the application. Dialplan may check these in order to do something in case of success/failure. After some thought and advices from other people on asterisk-dev list I made the application to work the following way: * If fax is sent ok, application sets FAXSTATUS=SUCCESS and returns successfully (dialplan execution continues) * If there were some problems with the fax data (no fax for example) but the channel still up and ok, application sets FAXSTATUS=FAILED and returns successfully (dialplan execution continues) * If there are problems with channel (like user hangup), application sets FAXSTATUS=FAILED and returns -1 which makes Asterisk to immediately abort dialplan execution. Note that in the last case, dialplan code immediately following SendFAX/ReceiveFAX won't be executed. If you wamt to perform some action in any failure including channel hangup, you better not placing the code after the SendFAX/ReceiveFAX but place it in the 'h' extension instead. This extension gets executed on the hangup. You will have access to all FAX* variables there. Something like: [faxcontext] exten = 100,1,ReceiveFAX(.......) exten = 100,n,Hangup exten = h,1,Noop(This will be executed regardles fax received Ok or user hung up) exten = h,n,Noop(FAXSTATUS = ${FAXSTATUS}) (Note that you may need to update Asterisk trunk to 88209 in order to make 'h' extension working - see issue 11146) I encourage everrybody interested to test new version. |
_________________
Trixbox 2.2.x (Asterisk 1.4.11) / FXO шлюзы (Dynamix, OvisLink, Planet, etc) / разные IP-телефоны (OvisLink, Grandstream, Dynamix, Nokia, Cisco ATA-186, etc)
а я тут к нему т38 прикручиваю немного канчено не так риалезовано у него вызов обработки факсов универсально но не правильно не много
кстати Игорь у тебя есть его контакт??
и кто хочет помочь в организации полноценой пожержки т38 в астериск???
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360
_________________
SuSE 10.1 / Asterisk-trunk / Celeron 1000 / chan_misdn (HFC)
Linksys PAP2T / SPA941 / SPA3102 / SPA2102
_________________
Ubuntu-Server 6.06 /Asterisk 1.4.12/app_fax /spandsp4pre11
Digium TDM400/NateksNetworks VC115-2/Polycom IP301 SP /Snom 360