[asterisk-gui] Can't Receive a call

Bob Crandell bob at assuredcomp.com
Tue Jul 21 11:15:13 CDT 2009


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 [92068392 at DLPN_DP1:1] Macro("DAHDI/9-1", "trunkdial-failover-0.3,DAHDI/g1/2068392,,trunk_1,") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:1] GotoIf("DAHDI/9-1", "0?1-fmsetcid,1") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:2] GotoIf("DAHDI/9-1", "0?1-setgbobname,1") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:3] Set("DAHDI/9-1", "CALLERID(num)=") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:4] GotoIf("DAHDI/9-1", "0?1-dial,1") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:5] Set("DAHDI/9-1", "CALLERID(all)=") in new stack
    -- Executing [s at macro-trunkdial-failover-0.3:6] Goto("DAHDI/9-1", "1-dial,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-dial,1)
    -- Executing [1-dial at macro-trunkdial-failover-0.3: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-gui/attachments/20090721/339fc86a/attachment.htm 


More information about the asterisk-gui mailing list