Gentlemen,
Any idea how to solve the problem of failed fax calls?
Thanks,
David
----- Original Message ----
From: David <[EMAIL PROTECTED]>
To: Users Mailing List - Non-Commercial Discussion
<[email protected]>
Sent: Tuesday, September 11, 2007 9:46:00 AM
Subject: Re: [Callweaver-users] T.38 FEC
Hi,
OK, So by disabling all the FEC related fields in the udptl.conf file and
activating the redundancy, it works. I wonder if there's a manual that explains
the content of this file and which SDP fields can be modified by it. Right now,
I'm sending this, but only very few of the fields are configurable through the
file:
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): root 4042 4043 IN IP4 192.168.1.6
Session Name (s): session
Connection Information (c): IN IP4 192.168.1.6
Time Description, active time (t): 0 0
Media Description, name and address (m): image 17636 udptl t38
Media Attribute (a): T38FaxVersion:0
Media Attribute (a): T38MaxBitRate:14400
Media Attribute (a): T38FaxFillBitRemoval:0
Media Attribute (a): T38FaxTranscodingMMR:0
Media Attribute (a): T38FaxTranscodingJBIG:0
Media Attribute (a): T38FaxRateManagement:transferredTCF
Media Attribute (a): T38FaxMaxBuffer:400
Media Attribute (a): T38FaxMaxDatagram:400
Media Attribute (a): T38FaxUdpEC:t38UDPRedundancy
Now, I have another problem. Some faxes are not received. I made several calls
and in the log trace, the only difference I found between successful calls and
failed ones is the order of these tasks:
Good Call:
-- Executing SipT38SwitchOver("SIP/WS00-bae7", "")
Sep 10 21:35:16
NOTICE[966670]: channel.c:669 opbx_channel_perform_set_t38_status: Setting t38
status to 1 at chan_sip.c:16741
-- Executing RxFAX("SIP/WS6500-bae7",
"/usr/local/var/spool/callweaver/fax/1/1189452914.10.tif,debug,ecm")
Sep 10 21:35:16 NOTICE[163848]: channel.c:669
opbx_channel_perform_set_t38_status: Setting t38 status to 2 at chan_sip.c:4783
-- Executing Hangup("SIP/WS6500-bae7", "")
Another Good Call:
-- Executing SipT38SwitchOver("SIP/WS00-12cd", "")
Sep 10 22:41:58 NOTICE[1114126]: channel.c:669
opbx_channel_perform_set_t38_status: Setting t38 status to 1 at chan_sip.c:16741
-- Executing RxFAX("SIP/WS6500-12cd",
"/usr/local/var/spool/callweaver/fax/4/1189456917.12.tif,debug,ecm")
Sep 10 22:41:58 NOTICE[163848]: channel.c:669
opbx_channel_perform_set_t38_status: Setting t38 status to 2 at chan_sip.c:4783
Failed Call:
-- Executing SipT38SwitchOver("SIP/WS00-28a3", "")
Sep 10 21:32:00 NOTICE[901134]: channel.c:669
opbx_channel_perform_set_t38_status: Setting t38
status to 1 at chan_sip.c:16741
Sep 10 21:32:01 NOTICE[163848]: channel.c:669
opbx_channel_perform_set_t38_status: Setting t38 status to 2 at chan_sip.c:4783
-- Executing RxFAX("SIP/WS6500-28a3",
"/usr/local/var/spool/callweaver/fax/4/1189452719.9.tif,debug,ecm")
-- Executing Hangup("SIP/WS6500-28a3", "")
Another Failed Call:
-- Executing SipT38SwitchOver("SIP/WS00-b752", "")
-- Executing RxFAX("SIP/WS6500-b752",
"/usr/local/var/spool/callweaver/fax/4/1189456681.11.tif,debug,ecm")
Sep 10 22:38:03 NOTICE[1032206]: app_rxfax.c:499 rxfax_audio: Switching to
generator mode
Questions:
1. What are t38 status values 1 & 2 representing?
2. Is there a problem in the code that causes the application not to run the
tasks in the proper order?
3. What's "generator mode"?
Thanks,
David
----- Original Message ----
From: Max CtRiX <[EMAIL PROTECTED]>
To: Users Mailing List - Non-Commercial Discussion
<[email protected]>
Sent: Monday, September 10, 2007 5:40:45 PM
Subject: Re: [Callweaver-users] T.38 FEC
Max CtRiX ha
scritto:
> Steve Underwood ha scritto:
>> David wrote:
>>> Hello list,
>>>
>>> Does anyone know if it's possible to disable FEC, when sending T.38
>>> reINVITE and if yes, how?
>>>
>>> A carrier we're working with doesn't support it (only redundancy).
>> The should not be an option for this. This is something which is
>> negotiated, and should sort itself out automatically. If you have found
>> a case where the negotiation isn't working, please file an error report,
>> with a log file showing what happens.
>>
>
> Particularly, on incoming calls it's automatic.
> On outgoing calls, the preferred behaviour is managed in udptl.conf.
>
i should shut up today.
It's the opposite of what i wrote.
Max
_______________________________________________
Callweaver-users mailing
list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
____________________________________________________________________________________
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
