digium TDM400 card - no incoming call routing

Discussion in 'General' started by kaynos, Feb 13, 2008.

  1. kaynos

    Joined:
    Oct 21, 2007
    Messages:
    18
    Likes Received:
    0
    new setup with 1.0. Outgoing calls work fine. Incoming calls play service unavailable message whether routing to extension, or just terminating call. Had the same problem in 0.9.2, but previous versions worked ok. All Zap channels show up in hardware detection and in FOP. Incoming calls are displayed in FOP and then the not in service message is displayed.

    -- Starting simple switch on 'Zap/1-1'
    -- Executing [s@from-pstn:1] NoOp("Zap/1-1", "No DID or CID Match") in new stack
    -- Executing [s@from-pstn:2] Answer("Zap/1-1", "") in new stack
    -- Executing [s@from-pstn:3] Wait("Zap/1-1", "2") in new stack
    -- Executing [s@from-pstn:4] Playback("Zap/1-1", "ss-noservice") in new stack
    -- <Zap/1-1> Playing 'ss-noservice' (language 'en')
    -- Executing [s@from-pstn:5] SayAlpha("Zap/1-1", "") in new stack
    == Auto fallthrough, channel 'Zap/1-1' status is 'UNKNOWN'
    -- Hungup 'Zap/1-1'

    ****zapata.conf ****

    ; Span 1: WCTDM/0 "Wildcard TDM400P REV E/F Board 1"
    ;;; line="1 WCTDM/0/0"
    signalling=fxs_ks
    callerid=asreceived
    group=0
    context=from-pstn
    channel => 1
    context=default

    ;;; line="2 WCTDM/0/1"
    signalling=fxs_ks
    callerid=asreceived
    group=0
    context=from-pstn
    channel => 2
    context=default

    ;;; line="3 WCTDM/0/2"
    signalling=fxs_ks
    callerid=asreceived
    group=0
    context=from-pstn
    channel => 3
    context=default

    ;;; line="4 WCTDM/0/3"
    signalling=fxs_ks
    callerid=asreceived
    group=0
    context=from-pstn
    channel => 4
    context=default




    Is there a context problem?

    Also, IRC chat doesn't seem to be working.
     
  2. DaveD

    Joined:
    Nov 12, 2007
    Messages:
    597
    Likes Received:
    0
    Try Changing the context to , context=from-zaptel and set incoming route to suit
     
  3. kaynos

    Joined:
    Oct 21, 2007
    Messages:
    18
    Likes Received:
    0
    I had previously changed that, but not restarted asterisk, only reloaded config and restarted zaptel. After restarting asterisk changing that context allowed incoming calls. Thank you.
     

Share This Page