Jerry Geis wrote:
> I am using asterisk 1.4.21 with outgoing call files.
>
> I am call a line that is busy as you can see below.
> How can my AGI ask what the status of the last call was
> so I can tell if there was NO ANSWER or it was BUSY?
>
> Thanks,
>
> Jerry
>
>    -- Attempting call on SIP/401 for 
> [EMAIL PROTECTED]:1 (Retry 1)
>    -- Got SIP response 486 "Busy" back from 192.168.1.161
>       > Channel SIP/401-15aa5ab0 was never answered.
>    -- Executing [EMAIL PROTECTED]:1] AGI("OutgoingSpoolFailed", 
> "smvoice") in new stack
>    -- Launched AGI Script /var/lib/asterisk/agi-bin/smvoice
>  == Spawn extension (smvoice-dialout, failed, 1) exited non-zero on 
> 'OutgoingSpoolFailed'
> [Aug  7 09:20:56] NOTICE[11272]: pbx_spool.c:341 attempt_thread: Call 
> failed to go through, reason (5) Remote end is Busy
>
>
I am trying to inquire ${DIALSTATUS} from both the agi and the dial plan 
and it is not set.

exten => failed,1,noop(${DIALSTATUS})
exten => failed,2,agi(smvoice,-digium_failed)


  -- Attempting call on SIP/401 for 
[EMAIL PROTECTED]:1 (Retry 1)
    -- Got SIP response 486 "Busy" back from 192.168.1.161
       > Channel SIP/401-15ac2dd0 was never answered.
    -- Executing [EMAIL PROTECTED]:1] NoOp("OutgoingSpoolFailed", 
"") in new stack
    -- Executing [EMAIL PROTECTED]:2] AGI("OutgoingSpoolFailed", 
"smvoice|-digium_failed") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/smvoice
  == Spawn extension (smvoice-dialout, failed, 2) exited non-zero on 
'OutgoingSpoolFailed'


As you can see above the call was BUSY, the dialplan should be showing 
${DIALSTATUS}
and it is empty. What am I not doing to get the resulting dial status?

Thanks,

Jerry


_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to