Issue after upgrading to 2.4.1.0

After I upgraded I now see a problem when adding a new ZAP extension. This is the result after I add another extension with ZAP/40. ZAP/32 was working fine.

– Starting simple switch on ‘Zap/32-1’
– Executing Set(“Zap/32-1”, “DID=8320001111”) in new stack
– Executing Goto(“Zap/32-1”, “s|1”) in new stack
– Goto (from-zaptel,s,1)
– Executing NoOp(“Zap/32-1”, “Entering from-zaptel with DID == 8320001111”) in new stack
– Executing Ringing(“Zap/32-1”, “”) in new stack
– Executing Set(“Zap/32-1”, “DID=8320001111”) in new stack
– Executing NoOp(“Zap/32-1”, “DID is now 8320001111”) in new stack
– Executing GotoIf(“Zap/32-1”, “1?zapok:notzap”) in new stack
– Goto (from-zaptel,s,8)
– Executing NoOp(“Zap/32-1”, “Is a Zaptel Channel”) in new stack
– Executing Set(“Zap/32-1”, “CHAN=32-1”) in new stack
– Executing Set(“Zap/32-1”, “CHAN=32”) in new stack
– Executing Macro(“Zap/32-1”, “from-zaptel-32|8320001111|1”) in new stack
– Executing NoOp(“Zap/32-1”, “Returned from Macro from-zaptel-32”) in new s tack
– Executing Goto(“Zap/32-1”, “from-pstn|8320001111|1”) in new stack
– Goto (from-pstn,8323326627,1)
– Executing NoOp(“Zap/32-1”, “Catch-All DID Match - Found 8320001111 - You probably want a DID for this.”) in new stack
– Executing Goto(“Zap/32-1”, “ext-did|s|1”) in new stack
– Goto (ext-did,s,1)
– Executing Set(“Zap/32-1”, “__FROM_DID=s”) in new stack
– Executing Gosub(“Zap/32-1”, “app-blacklist-check|s|1”) in new stack
– Executing LookupBlacklist(“Zap/32-1”, “”) in new stack
– Executing GotoIf(“Zap/32-1”, “0?blacklisted”) in new stack
– Executing Return(“Zap/32-1”, “”) in new stack
– Executing GotoIf(“Zap/32-1”, “0 ?cidok”) in new stack
– Executing Set(“Zap/32-1”, “CALLERID(name)=”) in new stack
– Executing NoOp(“Zap/32-1”, “CallerID is “” <>”) in new stack
– Executing Set(“Zap/32-1”, “__CALLINGPRES_SV=allowed_not_screened”) in new stack
– Executing SetCallerPres(“Zap/32-1”, “allowed_not_screened”) in new stack
– Executing Goto(“Zap/32-1”, “”) in new stack
== Spawn extension (ext-did, s, 8) exited non-zero on ‘Zap/32-1’
– Hungup ‘Zap/32-1’
– Starting simple switch on ‘Zap/32-1’
– Hungup ‘Zap/32-1’

All it does is give a fast busy when dialing out. Inbound still works fine. If I restore to a state prior to the addition of the new extension (ZAP/40) all works fine again. This seems to be part of the problem “Catch-All DID Match - Found 8320001111 - You probably want a DID for this.” This doesn’t show up when I restore and not add the ZAP/40 extension.

8320001111 was another number, it was changed to protect privacy.

Any help would be appreciated.

It had nothing to do with the upgrade. One of the guys entered in ZAP/40 in the channel line instead of just 40.
On reboot asterisk fails to start and dies with a syntax error. Just a suggestion maybe the code can parse the zapata file and instead of a free form text box it could be a drop down with a list of zap channels. This would prevent stupid syntax errors which cause asterisk to fail.

Please post this as a feature request in the bug tracker. IT will get lost here otherwise. To get to the Bug tracker, look on the left, click on Development Site, Report Bug.

Thanks.