[asterisk-users] exited non-zero on 'Zap/1-1' in macro ...

[Steve Totaro]

On Mon, Apr 7, 2008 at 8:38 AM, Brian J. Murrell <brian at interlinx.bc.ca> wrote:
> I have a macro which I call when I want to ring the house phones.  So
>  for example, when a Zap line rings it enters the dialplan in the
>  "inbound-pots" context which is as follows:
>
>  [inbound-pots]
>  exten => s,1,Set(CDR(accountcode)=...)
>  exten => s,n,Macro(check-incoming)
>  exten => s,n,Goto(inbound-house,s,1)
>
>  [inbound-house]
>  exten => s,1,Macro(dialhouse)
>  exten => s,n,Hangup
>
>  [macro-dialhouse]
>  ; Do 'things' here when we want to dial the house,
>  ;
>  exten => s,1,NoOp(${CALLERID(name)}|${CALLERID(num)}|${DATETIME}|${CALLERIDNUM}|${CALLERIDNAME})
>  exten => s,n,System(/usr/local/bin/callerid "${CALLERID(num)}" "${CALLERID(name)}")
>  exten => s,n,Dial(${HOUSE}&${OFFICE}&${BRIANEXTS},30,tw)
>  exten => s,n,Goto(s-${DIALSTATUS},1)
>  exten => s-ANSWER,1,Noop("ANSWERED")
>  exten => s-ANSWER,n,MacroExit()
>  exten => _s-,1,Goto(general-voicemail,s,1)
>  exten => h,1,Hangup
>  exten => i,1,Hangup
>
>  What happens on the console on every single call termination from the
>  Zap line is this:
>
>     -- Executing [s at inbound-house:1] Macro("Zap/1-1", "dialhouse") in new stack
>     -- Executing [s at macro-dialhouse:1] NoOp("Zap/1-1", "...|...|||") in new stack
>     -- Executing [s at macro-dialhouse:2] System("Zap/1-1", "/usr/local/bin/callerid "..." "..."") in new stack
>     -- Executing [s at macro-dialhouse:3] Dial("Zap/1-1", "SIP/house&SIP/brian&SIP/pc|30|tw") in new stack
>     -- Called house
>     -- Called brian
>     -- Called pc
>     -- SIP/house-08437510 is ringing
>     -- SIP/pc-084937a0 is ringing
>     -- Got SIP response 486 "Busy Here" back from 10.75.22.200
>     -- SIP/brian-084953a0 is busy
>     -- SIP/house-08437510 answered Zap/1-1
>   == Spawn extension (macro-dialhouse, s, 3) exited non-zero on 'Zap/1-1' in macro 'dialhouse'
>   == Spawn extension (macro-dialhouse, s, 3) exited non-zero on 'Zap/1-1'
>     -- Executing [h at macro-dialhouse:1] Hangup("Zap/1-1", "") in new stack
>   == Spawn extension (macro-dialhouse, h, 1) exited non-zero on 'Zap/1-1'
>     -- Hungup 'Zap/1-1'
>
>  So the question is why the "exited non-zero on 'Zap/1-1'" messages?  I'd
>  really like to get rid of them so that a non-zero exit is really
>  something bad to pay attention to.
>
>  b.
>

Just ignore it.  Exit on non-zero just means Hangup.  Maybe set
verbose 0 will make you feel better.

Thanks,
Steve Totaro