Have you created incoming calling rules via the GUI for the analog trunk? Looks like it's hitting the s extension in teh DID_trunk_1 context in extensions.conf.
On Thu, Jul 9, 2009 at 11:42 AM, Bob Crandell <[email protected]> wrote: > Ryan, > > Ok. With that change we can call out now. > > Are you ready for this? ... Now we can't receive calls. > Here is the log: > Connected to Asterisk 1.6.0.9 currently running on PBX (pid = 14120) > Verbosity was 3 and is now 6 > -- Starting simple switch on 'DAHDI/1-1' > -- Executing [...@did_trunk_1:1] ExecIf("DAHDI/1-1", > "0?SetCallerPres(unavailable)") in new stack > -- Auto fallthrough, channel 'DAHDI/1-1' status is 'UNKNOWN' > -- Hungup 'DAHDI/1-1' > -- Starting simple switch on 'DAHDI/1-1' > [Jul 9 08:35:52] NOTICE[14167]: chan_dahdi.c:7490 ss_thread: Got event 18 > (Ring Begin)... > [Jul 9 08:35:54] NOTICE[14167]: chan_dahdi.c:7490 ss_thread: Got event 2 > (Ring/Answered)... > -- Executing [...@did_trunk_1:1] ExecIf("DAHDI/1-1", > "1?SetCallerPres(unavailable)") in new stack > [Jul 9 08:35:54] WARNING[14167]: app_setcallerid.c:69 > setcallerid_pres_exec: SetCallerPres is deprecated. Please use > Set(CALLERPRES()=unavailable) instead. > -- Auto fallthrough, channel 'DAHDI/1-1' status is 'UNKNOWN' > -- Hungup 'DAHDI/1-1' > -- Starting simple switch on 'DAHDI/1-1' > [Jul 9 08:36:04] NOTICE[14168]: chan_dahdi.c:7490 ss_thread: Got event 18 > (Ring Begin)... > [Jul 9 08:36:06] NOTICE[14168]: chan_dahdi.c:7490 ss_thread: Got event 2 > (Ring/Answered)... > -- Executing [...@did_trunk_1:1] ExecIf("DAHDI/1-1", > "1?SetCallerPres(unavailable)") in new stack > -- Auto fallthrough, channel 'DAHDI/1-1' status is 'UNKNOWN' > -- Hungup 'DAHDI/1-1' > -- Starting simple switch on 'DAHDI/1-1' > [Jul 9 08:36:16] NOTICE[14169]: chan_dahdi.c:7490 ss_thread: Got event 18 > (Ring Begin)... > [Jul 9 08:36:18] NOTICE[14169]: chan_dahdi.c:7490 ss_thread: Got event 2 > (Ring/Answered)... > -- Executing [...@did_trunk_1:1] ExecIf("DAHDI/1-1", > "1?SetCallerPres(unavailable)") in new stack > -- Auto fallthrough, channel 'DAHDI/1-1' status is 'UNKNOWN' > -- Hungup 'DAHDI/1-1' > PBX*CLI> > Is this the current GUI? > Asterisk GUI-version : SVN-branch-2.0-r4962 > > Thanks > Bob > > >>> Ryan Brindley <[email protected]> 7/8/2009 5:02 AM >>> > Bob, > Yes, you would be lookin at extensions.conf and under the [global] context > for a line that starts with 'trunk_1='. > You can find your real info in users.conf. Look for your trunk context > ([trunk_1] most likely) and then the group= variable and then go change your > trunk_1 variable described earlier to "trunk_1=DAHDI/g<group number>". > > -- > Ryan Brindley > Digium, Inc. | Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > main: +1 256-428-6000 fax: +1 256-864-0464 > Check us out at: http://digium.com & http://asterisk.org > > ----- Original Message ----- > From: "Bob Crandell" <[email protected]> > To: "Asterisk GUI project discussion" <[email protected]> > Sent: Tuesday, July 7, 2009 9:07:35 PM GMT -05:00 US/Canada Eastern > Subject: Re: [asterisk-gui] Busy > > Ryan, > > I'm supposed to be editing extensions.conf right? > > How can I tell what the real info is supposed to be? > > Thanks > Bob > > >>> Ryan Brindley <[email protected]> 7/7/2009 1:58 PM >>> > Bob, > Your problem is when the macro tries to dial DAHDI/trunk_1/5105555, if you > look at the top of the page under your globals, your 'trunk_1' context > should probably be something like 'trunk_1=DAHDI/trunk_1' that isn't correct > and I believe was fixed in a recent commit when the GUI when under some > heavy testing. If you haven't already I'd recommend deleting that trunk and > re-creating it (assuming you're using a recent checkout of the GUI). If you > have already done that, check http://issues.asterisk.org 's Asterisk-GUI > project for open issues related to your issue or open a new issue and we'll > get it resolved. > > For now, to verify that this is in fact the problem (even though I'm pretty > sure it is) you can change your trunk_1 variable to be whatever your real > info is "DAHDI/g1" or whatever. > > -- > Ryan Brindley > Digium, Inc. | Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > main: +1 256-428-6000 fax: +1 256-864-0464 > Check us out at: http://digium.com & http://asterisk.org > > ----- Original Message ----- > From: "Bob Crandell" <[email protected]> > To: "Asterisk GUI" <[email protected]> > Sent: Tuesday, July 7, 2009 3:32:22 PM GMT -05:00 US/Canada Eastern > Subject: [asterisk-gui] Busy > > Hi, > > I'm almost ready to take this thing live and have just one more hurdle to > beat. Any outbound call from any extension gets a busy signal. We can call > each other's extensions. We can receive calls from outside. We just can't > make calls. > > Here is this: > Asterisk Build: > Asterisk/1.6.0.9 > Asterisk GUI-version : SVN-branch-2.0-r4962 > > This from the log: > Verbosity was 3 and is now 6 > -- Starting simple switch on 'DAHDI/9-1' > [Jul 7 12:28:33] WARNING[4754]: chan_dahdi.c:2010 dahdi_enable_ec: Unable > to enable echo cancellation on channel 9 (No such device) > -- Executing [95105...@dlpn_cbplan:1] Macro("DAHDI/9-1", > "trunkdial-failover-0.3,DAHDI/trunk_1/5105957,,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/trunk_1/5105555") in new stack > [Jul 7 12:28:33] WARNING[4754]: chan_dahdi.c:9331 dahdi_request: Unable to > determine channel for data trunk_1/5105555 > [Jul 7 12:28:33] WARNING[4754]: app_dial.c:1468 dial_exec_full: Unable to > create channel of type 'DAHDI' (cause 0 - Unknown) > == Everyone is busy/congested at this time (1:0/0/1) > -- Executing [[email protected]:2] > GotoIf("DAHDI/9-1", "0 > 0 ?1-CHANUNAVAIL,1:1-out,1") in new stack > -- Goto (macro-trunkdial-failover-0.3,1-out,1) > -- Executing [[email protected]:1] > Hangup("DAHDI/9-1", "") in new stack > == Spawn extension (macro-trunkdial-failover-0.3, 1-out, 1) exited > non-zero on 'DAHDI/9-1' in macro 'trunkdial-failover-0.3' > == Spawn extension (DLPN_CBPlan, 95105555, 1) exited non-zero on > 'DAHDI/9-1' > -- Hungup 'DAHDI/9-1' > I don't know what it means. Is this a problem with Asterisk? Is there > someplace in the GUI I can go to fix it? > > 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 >
_______________________________________________ --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
