PSTN to SIP/PSTN but SIP to PSTN fails

Discussion in 'General' started by 64_Bit_Hacker, Oct 12, 2010.

  1. 64_Bit_Hacker

    Joined:
    Oct 12, 2010
    Messages:
    12
    Likes Received:
    0
    Hi Guys/Girls/Quadrupeds ;-),

    I have got an interesting predicament. I have scoured the forums and the web, but to no avail. Any help or insight would greatly be appreciated.

    Quick History:

    Elastix core version 1.6.2.10
    Server has SIP trunk. Calls are coming in and out over it just fine.

    Users:
    I have multiple users on SIP and PSTN.

    PSTN is handled by two YSTDM8xx REV E Boards with FXS modules. Now PSTN users can phone other PSTN users on the network, they can also phone SIP users and make calls to external numbers. SIP users can do the same except they cannot phone PSTN users.

    I am getting a Channel unavailable on the PSTN user to which the SIP call is being passed.

    Interesting thing:

    I see this on my SIP:

    dialparties.agi: Methodology of ring is 'none'
    -- dialparties.agi: Added extension 10 to extension map
    -- dialparties.agi: Extension 10 cf is disabled
    -- dialparties.agi: Extension 10 do not disturb is disabled
    dialparties.agi: EXTENSION_STATE: 0 (NOT_INUSE)
    dialparties.agi: Extension 10 has ExtensionState: 0

    but on PSTN I get an extenionstate of 4?

    dialparties.agi: Methodology of ring is 'none'
    -- dialparties.agi: Added extension 17 to extension map
    -- dialparties.agi: Extension 17 cf is disabled
    -- dialparties.agi: Extension 17 do not disturb is disabled
    dialparties.agi: EXTENSION_STATE: 4 (UNAVAILABLE)
    dialparties.agi: Extension 17 has ExtensionState: 4

    Pasting some info below:

    dahdi show channels

    Chan Extension Context Language MOH Interpret Blocked State
    pseudo default default In Service
    1 from-internal default In Service
    2 from-internal default In Service
    3 from-internal default In Service
    4 from-internal default In Service
    5 from-internal default In Service
    6 from-internal default In Service
    7 from-internal default In Service
    8 from-internal default In Service
    9 from-internal default In Service
    10 from-internal default In Service
    11 from-internal default In Service
    12 from-internal default In Service

    Example Channel:

    The odd thing here is that signalling shows as FXO, but the web gui and chan_dadi indicates FXS. Also on a side note, where can I set the default 'law' to g729 from ulaw?

    dahdi show channel 1

    Channel: 1
    File Descriptor: 18
    Span: 1
    Extension:
    Dialing: no
    Context: from-internal
    Caller ID: 13
    Calling TON: 0
    Caller ID name: device
    Mailbox: 13@device
    Destroy: 0
    InAlarm: 0
    Signalling Type: FXO Kewlstart
    Radio: 0
    Owner: <None>
    Real: <None>
    Callwait: <None>
    Threeway: <None>
    Confno: -1
    Propagated Conference: -1
    Real in conference: 0
    DSP: no
    Busy Detection: no
    TDD: no
    Relax DTMF: no
    Dialing/CallwaitCAS: 0/0
    Default law: ulaw
    Fax Handled: no
    Pulse phone: no
    DND: no
    Echo Cancellation:
    128 taps
    (unless TDM bridged) currently OFF
    Wait for dialtone: 0ms
    Actual Confinfo: Num/0, Mode/0x0000
    Actual Confmute: No
    Hookstate (FXS only): Onhook

    cat chan_dahdi.conf

    [channels]
    context=from-pstn
    signalling=fxs_ks
    rxwink=300 ; Atlas seems to use long (250ms) winks
    usecallerid=yes
    hidecallerid=no
    callwaiting=yes
    usecallingpres=yes
    callwaitingcallerid=yes
    threewaycalling=yes
    transfer=yes
    canpark=yes
    cancallforward=yes
    callreturn=yes
    echocancel=yes
    echocancelwhenbridged=no
    faxdetect=incoming
    echotraining=800
    rxgain=0.0
    txgain=0.0
    callgroup=1
    pickupgroup=1

    ;Uncomment these lines if you have problems with the disconection of your analog lines
    ;busydetect=yes
    ;busycount=3


    immediate=no

    #include dahdi-channels.conf
    #include chan_dahdi_additional.conf

    As you can see below, I think it's because my state shows as unavailable.

    core show hint 1
    10@ext-local : SIP/10&Custom:DND10 State:InUse Watchers 0
    13@ext-local : DAHDI/1&Custom:DND13 State:Unavailable Watchers 0
    14@ext-local : SIP/14&Custom:DND14 State:Idle Watchers 0
    15@ext-local : DAHDI/2&Custom:DND15 State:InUse Watchers 0
    16@ext-local : DAHDI/3&Custom:DND16 State:Unavailable Watchers 0
    17@ext-local : DAHDI/4&Custom:DND17 State:Unavailable Watchers 0
    18@ext-local : DAHDI/5&Custom:DND18 State:Unavailable Watchers 0
    19@ext-local : DAHDI/6&Custom:DND19 State:Unavailable Watchers 0

    dahdi_scan

    [1]
    active=yes
    alarms=OK
    description=YSTDM8xx REV E Board 9
    name=WCTDM/8
    manufacturer=YEASTAR
    devicetype=YSTDM8xx REV E
    location=PCI Bus 02 Slot 01
    basechan=1
    totchans=8
    irq=169
    type=analog
    port=1,FXS
    port=2,FXS
    port=3,FXS
    port=4,FXS
    port=5,FXS
    port=6,FXS
    port=7,FXS
    port=8,FXS
    [2]
    active=yes
    alarms=OK
    description=YSTDM8xx REV E Board 9
    name=WCTDM/8
    manufacturer=YEASTAR
    devicetype=YSTDM8xx REV E
    location=PCI Bus 02 Slot 02
    basechan=9
    totchans=8
    irq=233
    type=analog
    port=9,FXS
    port=10,FXS
    port=11,FXS
    port=12,FXS
    port=13,none
    port=14,none
    port=15,none
    port=16,none

    Thx
    Carl [​IMG]
     
  2. 64_Bit_Hacker

    Joined:
    Oct 12, 2010
    Messages:
    12
    Likes Received:
    0
    Hi Guys,

    I might have posted this in the wrong section. Please excuse. Me = Elastix Forum Noob.

    Thx
    Carl
     

Share This Page