Re: [Callweaver-users] R: hello

[voipbuster]

hi again, in fact the problem was not t38 but alaw... They didn't accept Alaw, that's solved. Now the problem is t38, they acccept t38 but it fails when callweaver is set with "t38udptlsupport=yes" with "t38udptlsupport=no" it works. I am not a good debugger, but if you tell me what I have to do to give you a debug trace usable, I will send it to you the result. Fyi, the gateway is Teles. Tell me what commands or debug options I need, and you will have a trace. With just udptl debug, I have 2 messages send by callweaver with no answers from the gateway. At least with a private email, I can give you access to the server on ssh, it's a test server, no worries :) tell me more to help. Kind regards, VB Steve Underwood a écrit : voipbuster wrote: hi, solved for my side... It was a provider problem not accepting T38, I just have switched to another provider and now it works correctly. In fact, my application is fax2mail and mail2fax. I have send and receive more tha 30 faxes each way, working like a charm. If a switch to T.38 was rejected by the provider, the call should have continued using audio for faxing. If it didn't, we would be interested in seeing some logs to try to work out why. Steve _______________________________________________ Callweaver-users mailing list Callweaver-users@callweaver.org http://lists.callweaver.org/mailman/listinfo/callweaver-users

_______________________________________________
Callweaver-users mailing list
Callweaver-users@callweaver.org
http://lists.callweaver.org/mailman/listinfo/callweaver-users