I have fought this similar issue in the past. At this point, I really only have 1 other suggestion. I would delete your DAHDI trunks via the GUI. Then once that's done, go through users.conf and extensions.conf and make sure the trunks were actually deleted. I seen the GUI not clean up users.conf and extensions.conf very well in the past when deleting. Then re-create the trunks. If you don't want to do that maybe someone else on the list will chime in.
On Wed, Jul 22, 2009 at 3:18 PM, Bob Crandell <[email protected]> wrote: > Hi Matt, > > No worries. Jobs have that unfortunate side affect. > > The extension didn't exist 'cause I'm dumb. I created that account and now > the invalid extension error is gone. However incoming calls still don't > ring through to it and they don't go to voice mail either. This used to > work. It's almost as if an update stepped on it or there is a missing > piece. > > Thanks > Bob > > >>> Matt Sales <[email protected]> 7/21/2009 06:17 PM >>> > Hi Bob, sorry for the late response. I started a new job this week which > has put me behind in keeping up with the mailing list. This error is stating > that the call is getting dumped in the [DID_trunk_1] context, s extension, > priority 1 in extenstions.conf but the s extension priority 1 doesn't exist > so it's falling back to the s extension in the [default] context but that > doesn't exist either. Do you have anything listed under [DID_trunk_1] in > extensions.conf > > > On Tue, Jul 21, 2009 at 12:15 PM, Bob Crandell <[email protected]> > wrote: > > Hi All, > > I'm still struggling with this. I wiped the Asterisk install and put back > just enough to be able to make a call. Here is the log of an incoming call: > > -- Starting simple switch on 'DAHDI/1-1' > == Starting DAHDI/1-1 at DID_trunk_1,s,1 failed so falling back to exten > 's' > == Starting DAHDI/1-1 at DID_trunk_1,s,1 still failed so falling back to > context 'default' > [Jul 21 07:39:55] WARNING[10180]: pbx.c:3783 __ast_pbx_run: Channel > 'DAHDI/1-1' sent into invalid extension 's' in context 'default', but no > invalid handler > -- Hungup 'DAHDI/1-1' > -- Starting simple switch on 'DAHDI/1-1' > [Jul 21 07:40:04] NOTICE[10181]: chan_dahdi.c:7490 ss_thread: Got event 18 > (Ring Begin)... > [Jul 21 07:40:06] NOTICE[10181]: chan_dahdi.c:7490 ss_thread: Got event 2 > (Ring/Answered)... > == Starting DAHDI/1-1 at DID_trunk_1,s,1 failed so falling back to exten > 's' > == Starting DAHDI/1-1 at DID_trunk_1,s,1 still failed so falling back to > context 'default' > [Jul 21 07:40:06] WARNING[10181]: pbx.c:3783 __ast_pbx_run: Channel > 'DAHDI/1-1' sent into invalid extension 's' in context 'default', but no > invalid handler > -- Hungup 'DAHDI/1-1' > -- Starting simple switch on 'DAHDI/1-1' > [Jul 21 07:40:20] WARNING[10182]: chan_dahdi.c:7634 ss_thread: CallerID > returned with error on channel 'DAHDI/1-1' > == Starting DAHDI/1-1 at DID_trunk_1,s,1 failed so falling back to exten > 's' > == Starting DAHDI/1-1 at DID_trunk_1,s,1 still failed so falling back to > context 'default' > [Jul 21 07:40:20] WARNING[10182]: pbx.c:3783 __ast_pbx_run: Channel > 'DAHDI/1-1' sent into invalid extension 's' in context 'default', but no > invalid handler > -- Hungup 'DAHDI/1-1' > > Here is an outbound call that worked: > -- Starting simple switch on 'DAHDI/9-1' > -- Hungup 'DAHDI/9-1' > -- Starting simple switch on 'DAHDI/9-1' > -- Executing [92068...@dlpn_dp1:1] Macro("DAHDI/9-1", > "trunkdial-failover-0.3,DAHDI/g1/2068392,,trunk_1,") in new stack > -- Executing [[email protected]:1] GotoIf("DAHDI/9-1", > "0?1-fmsetcid,1") in new stack > -- Executing [[email protected]:2] GotoIf("DAHDI/9-1", > "0?1-setgbobname,1") in new stack > -- Executing [[email protected]:3] Set("DAHDI/9-1", > "CALLERID(num)=") in new stack > -- Executing [[email protected]:4] GotoIf("DAHDI/9-1", > "0?1-dial,1") in new stack > -- Executing [[email protected]:5] Set("DAHDI/9-1", > "CALLERID(all)=") in new stack > -- Executing [[email protected]:6] Goto("DAHDI/9-1", > "1-dial,1") in new stack > -- Goto (macro-trunkdial-failover-0.3,1-dial,1) > -- Executing [[email protected]:1] Dial("DAHDI/9-1", > "DAHDI/g1/5551212") in new stack > -- Called g1/5551212 > -- DAHDI/1-1 answered DAHDI/9-1 > -- Native bridging DAHDI/9-1 and DAHDI/1-1 > [Jul 21 09:10:39] ERROR[10595]: cdr_csv.c:306 csv_log: Unable to re-open > master file /var/log/asterisk//cdr-csv//Master.csv : No such file or > directory > -- Hungup 'DAHDI/1-1' > == Spawn extension (macro-trunkdial-failover-0.3, 1-dial, 1) exited > non-zero on 'DAHDI/9-1' in macro 'trunkdial-failover-0.3' > == Spawn extension (DLPN_DP1, 92068392, 1) exited non-zero on 'DAHDI/9-1' > -- Hungup 'DAHDI/9-1' > > Question: > An outbound call uses DAHDI/9-1. Shouldn't an inbound call use DAHDI/9-1 or > DAHDI/1-9? > > Thanks > > > > Bob Crandell > Assured Computing, Inc. > 541-868-0331 > ComputerBase USA > 541-349-0404 > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-gui mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-gui > > > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-gui mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-gui >
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-gui mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-gui
