[asterisk-users] Handoff dial control to dialplan after AMI Originate

Grant Bagdasarian GB at cm.nl
Wed Jun 19 07:08:17 CDT 2013


I used a combination of failed and the h extension to get the dialplan to do what I want.

Thanks for the help guys!

From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Satish Barot
Sent: Wednesday, June 19, 2013 1:25 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Handoff dial control to dialplan after AMI Originate


On Wed, Jun 19, 2013 at 4:00 PM, Grant Bagdasarian <GB at cm.nl<mailto:GB at cm.nl>> wrote:
Why can't I execute any more dialplan after the Dial application? The scenario is when the Dial application dials the recipient but the recipient doesn't answer. The AMI will never go into the originateDialProcessor because the call was never answered. So I expect the Dialplan to continue after the Dial application has reached its timeout.

From: asterisk-users-bounces at lists.digium.com<mailto:asterisk-users-bounces at lists.digium.com> [mailto:asterisk-users-bounces at lists.digium.com<mailto:asterisk-users-bounces at lists.digium.com>] On Behalf Of Grant Bagdasarian
Sent: Wednesday, June 19, 2013 11:24 AM

To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Handoff dial control to dialplan after AMI Originate

I fixed it. The problem is just as I assumed; once the call is answered the dialplan goes into what's defined in Context/Exten/Prio of the Originate action.

I changed the Context/Exten/Prio in the action and pointed it to something else. Now it works.

Action: Originate
Channel: Local/outbound1 at originateDialContext
CallerID: 00311234567
Context: originateDialProcessor
Exten: outbound1
Priority: 1
Variable: recipient=0031612345678
Timeout: 10000

[originateDialContext]
exten => outbound1,1,Wait(1)
exten => outbound1,n,Set(recipient=${recipient})
exten => outbound1,n,Dial(SIP/${recipient}@originateChannel)

[originateDialProcessor]
exten => outbound1,1,Wait(1)
exten => outbound1,n,NoOp(${DIALSTATUS})
exten => outbound1,n,Hangup

From: asterisk-users-bounces at lists.digium.com<mailto:asterisk-users-bounces at lists.digium.com> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Lenz Emilitri
Sent: Wednesday, June 19, 2013 10:10 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Handoff dial control to dialplan after AMI Originate

Looks correct to me....

2013/6/19 Grant Bagdasarian <GB at cm.nl<mailto:GB at cm.nl>>
Hello,

I'd like to use the AMI interface to originate a call to a context in a dialplan, and handoff the dial control to the context.

Whenever I execute the below action, the recipient does ring, but when I answer it dials the recipient again. I believe this is because once answered the system is going to execute the Context/Exten/Prio in the Originate action?

Action: Originate
Channel: Local/outbound1 at originateDialContext
CallerID: 00311234567
Context: originateDialContext
Exten: outbound1
Priority: 1
Variable: recipient=0031612345678
Timeout: 10000

[originateDialContext]
exten => outbound1,1,Wait(1)
exten => outbound1,n,Set(recipient=${recipient})
exten => outbound1,n,Dial(SIP/${recipient}@originateChannel)

Anyone have an idea how to fix this?

--

You need a special extension 'failed' in a context originateDialProcessor to catch the control when call doesn't get answered in first leg.
[originateDialProcessor]
exten => outbound1,1,Wait(1)
exten => outbound1,n,NoOp(${DIALSTATUS})
exten => outbound1,n,Hangup

exten => failed,1,NoOp(----- CALL DIDN'T GET ANSWERED IN FIRST LEG -----)
--Satish Barot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20130619/66d80958/attachment-0001.htm>


More information about the asterisk-users mailing list