[asterisk-gui] Can't Receive a call

[Bob Crandell]

I fixed trunk_2 under Globals in extensions.conf.  When I went to fix the context for [trunk_1], I found it was already there.  Why what I pasted in here is different I don't know.  Here is what it looks like now:
[trunk_1]
context = DID_trunk_1
trunkname = CBTrunk  ; GUI metadata
busydetect = yes
busycount = 3
busypattern = 500,500
ringtimeout = 8000
answeronpolarityswitch = no
hanguponpolarityswitch = no
callprogress = no
progzone = us
usecallerid = yes
cidstart = ring
pulsedial = no
cidsignalling = bell
flash = 750
rxflash = 1250
mailbox = 6002
callerid = asreceived
dahdichan = 1,2,3,4,5,6,7
group = 1
hasexten = no
hasiax = no
hassip = no
registeriax = no
registersip = no
trunkstyle = analog
disallow = all
allow = all
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 1
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 2
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 3
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 4
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 5
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 6
gui_volume = 3  ; GUI metadata
signalling = fxs_ks
gui_fxooffset = 0  ; GUI metadata
rxgain = 2
txgain = 0.0
channel = 7

After these changes, I restarted Asterisk16 then rebooted the computer.  Still no joy.  Here is the log from an incoming call:
   -- Starting simple switch on 'DAHDI/1-1'
    -- Executing [s at 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 16 16:07:38] NOTICE[4919]: chan_dahdi.c:7490 ss_thread: Got event 18 (Ring Begin)...
[Jul 16 16:07:40] NOTICE[4919]: chan_dahdi.c:7490 ss_thread: Got event 2 (Ring/Answered)...
    -- Executing [s at DID_trunk_1:1] ExecIf("DAHDI/1-1", "1?SetCallerPres(unavailable)") in new stack
[Jul 16 16:07:40] WARNING[4919]: 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'

Thanks for your help
Bob


>>> Matt Sales <msales at gmail.com> 7/16/2009 12:16 PM >>>
I think I see your problem. In users.conf you need to add context=DID_trunk_1 for [trunk_1]. It currently has no context to Asterisk doesn't know what to do with calls coming in on channels 1-7. Once you add that, calls will then land in the [DID_trunk_1] context in extensions.conf where you have your time based rules.
Also, in extensions.conf under [globals] you need to change the trunk_2 varialbe from trunk_2 = DAHDI/trunk_2 to trunk_2 = DAHDI/g2.
Good Luck

On Thu, Jul 16, 2009 at 1:05 PM, Bob Crandell <bob at assuredcomp.com> wrote:


Here is System and Users:


/etc/dahdi/system.conf