[asterisk-users] Faxes stopped working - AMI issue?

[Joshua C. Colp]

On Wed, Nov 27, 2019 at 3:31 PM D'Arcy Cain <darcy at vybenetworks.com> wrote:

> I recently upgraded from Asterisk 13.19 to 16.6.1.  Everything is
> working fine with a few minor tweaks except outgoinf fax.  Incoming
> works fine.
>
> I do outgoing faxing through an AMI call.  Here is the output from the
> security log:
>
> [Nov 27 06:16:05] SECURITY[101222] res_security_log.c:
>
> SecurityEvent="ChallengeSent",EventTV="2019-11-27T06:16:05.566-0500",Severity="Informational",Service="SIP",EventVersion="1",AccountID="alex",SessionID="0x80ba54820",LocalAddress="IPV4/UDP/
> 98.158.139.74/5060",RemoteAddress="IPV4/UDP/72.143.94.110/5060
> ",Challenge="215351b4"
> [Nov 27 06:16:05] SECURITY[101222] res_security_log.c:
>
> SecurityEvent="SuccessfulAuth",EventTV="2019-11-27T06:16:05.591-0500",Severity="Informational",Service="SIP",EventVersion="1",AccountID="alex",SessionID="0x80ba54820",LocalAddress="IPV4/UDP/
> 98.158.139.74/5060",RemoteAddress="IPV4/UDP/72.143.94.110/5060
> ",UsingPassword="1"
>
> So I know that AMI is listening and I can talk to it.  Here is the main
> log"
>
> [Nov 27 06:16:00] VERBOSE[101155] asterisk.c: Remote UNIX connection
> [Nov 27 06:16:00] VERBOSE[101245] asterisk.c: Remote UNIX connection
> disconnected
> [Nov 27 06:16:01] VERBOSE[101244] manager.c: Manager 'asterisk' logged
> on from 127.0.0.1
>
> The AMI command, after the login, looks like this:
>
> Action: Originate
> Channel: SIP/outgoing/%%(destination)s
> Context: LocalSets
> CallerID: Vybe Consulting Inc Fax Service <5555551212>
> Exten: sendfax
> Priority: 1
> Timeout: 30000
> Variable: faxfile=%%(faxfile)s
> Variable: uid=%%(uid)s
> Variable: destination=%%(destination)s
> Variable: sender_name=Vybe Consulting Inc Fax Service
> Variable: sender_num=5555551212
>
> Those "%%" strings get replaced by real data.  My sendfax extension has
> a bunch of stuff but the very first line is this:
>
> exten => sendfax,1,Verbose(0,FAX ${faxfile} to ${destination})
>
> So, regardless of what follows, shouldn't I be seeing that message in my
> logs?
>

Only if it was actually answered. You'd need to dig deeper by looking at
the SIP trace itself (sip set debug on) to see if an attempt was made and
what occurred.

-- 
Joshua C. Colp
Senior Software Developer
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20191202/abbc1f11/attachment.html>