[asterisk-users] digium fax: can't indicate condition 19?
Scott L. Lykens
slykens at verimedservices.com
Tue Sep 29 10:46:36 CDT 2009
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-
> bounces at lists.digium.com] On Behalf Of David Backeberg
> Sent: Monday, September 21, 2009 10:42 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [asterisk-users] digium fax: can't indicate condition 19?
>
> On Mon, Sep 21, 2009 at 9:26 PM, sean darcy <seandarcy2 at gmail.com>
> wrote:
> > In my attempts to set up digium fax I get an odd warning:
> >
> > -- Executing [s at Capture-Fax:2] ReceiveFAX("SIP/173-b53023e8",
> > "/var/spool/asterisk/fax/20090921_1806.tif") in new stack
> > -- Channel 'SIP/173-b53023e8' receiving fax
> > '/var/spool/asterisk/fax/20090921_1806.tif'
> > [Sep 21 18:06:37] WARNING[5149]: chan_sip.c:5561 sip_indicate: Don't
> > know how to indicate condition 19
> > -- Channel 'SIP/173-b53023e8' fax session '7' started
> >
> > Is there some list of these conditions? Should I care?
>
> I get a lot of fax messages that seem extraneous so I usually ignore
> them. There is already an open ticket want an SVN fix for one that I
> found particularly annoying. I'm talking about one that repeatedly
> talks about a missing segment or something like that, and it happens a
> gazillion times per fax. A gazillion being "way more than I want it
> to".
>
> Did the fax come through okay? If yes I recommend ignoring the error
> unless you want to be particularly diligent and dig through the bug
> tracker to see if it's already been fixed.
I am getting the same error as the OP when trying to receive a fax with a T.38 capable provider. The fax never comes through and usually fails with No Carrier from the sender.
There does not appear to be a relevant bug in the tracker.
As we are eliminating our PRI soon I am trying to get faxing via T.38 working properly. I'm not interested in running Callweaver next to Asterisk just to support fax. :/
Any insight into this error would be greatly appreciated.
Thanks!
sl
More information about the asterisk-users
mailing list