On 12/2/19 11:52 AM, Joshua C. Colp wrote:> 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.OK, so I did that and my logs are really busy now. However, a search through them doesn't find the phone number that I am faxing to. Are you sure that it needs to be answered before it starts logging? Logging only when something works isn't much of a debugging tool. -- D'Arcy J.M. Cain Vybe Networks Inc. http://www.VybeNetworks.com/ IM:darcy at Vex.Net VoIP: sip:darcy at VybeNetworks.com
On Tue, Dec 3, 2019 at 4:53 PM D'Arcy Cain <darcy at vybenetworks.com> wrote:> On 12/2/19 11:52 AM, Joshua C. Colp wrote: > > 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. > > OK, so I did that and my logs are really busy now. However, a search > through them doesn't find the phone number that I am faxing to. > > Are you sure that it needs to be answered before it starts logging? > Logging only when something works isn't much of a debugging tool. >The way an Originate works is that upon answer the channel is directed to the dialplan at the given target. Since your dialplan has a verbose message, the verbose message would only be executed upon dialplan execution which would then only occur as a result of being answered. Have you tried narrowing it down at all? Using the CLI to do a test "channel originate" using the same dial string? Have you looked at what comes back from AMI as a result of the Originate to see if it shows anything? -- 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/20191203/ebb12469/attachment.html>
On 12/3/19 3:04 PM, Joshua C. Colp wrote:> > 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=555555121 > Have you tried narrowing it down at all? Using the CLI to do a test > "channel originate" using the same dial string? Have you looked at what > comes back from AMI as a result of the Originate to see if it shows > anything?First of all, I really appreciate the help. So I tried this in the CLI: (everything is on one line) channel originate SIP/outgoing/5556667777 extension=sendfax at LocalSets faxfile=/path/to/tiff/file priority=1 But I got "SendFAX requires an argument". I tried various things but I am poking around in the dark. Can you suggest an actual CLI command based on those options that I can try? Also, is there some way to have the AMI interface send back the same errors? All I get from the socket now is "Asterisk Call Manager/5.0.1". Thanks again. -- D'Arcy J.M. Cain Vybe Networks Inc. http://www.VybeNetworks.com/ IM:darcy at Vex.Net VoIP: sip:darcy at VybeNetworks.com