Issue After Install Dahdi

Home » Asterisk Users » Issue After Install Dahdi
Asterisk Users 8 Comments

i need your help regarding some issue related to the outband calls

i have installed Asterisk 1.4.32 with dahdi and i have 1 card diguim with 2
ports when i try to call my phone number all time i receive message busy number

this error just with g1.

with g2 there is no problem i can call without issue

can anyone see the CLI and tell me what is the problem

thanks and regards

== Parsing ‘/etc/asterisk/asterisk.conf’: Found
== Parsing ‘/etc/asterisk/extconfig.conf’: Found Connected to Asterisk currently running on SRVRADI
O (pid = 4147)
Verbosity is at least 3
— Executing [0661049303@agents:1] Set(“SIP/223-00000021”,
R0460587”) in new stack
— Executing [0661049303@agents:2] Dial(“SIP/223-00000021”,
9303|30”) in new stack
— Requested transfer capability: 0x00 – SPEECH
— Called g1/0661049303
— Moving call (DAHDI/3-1) from channel 3 to 2.
[Oct 21 17:43:27] WARNING[4264]: chan_dahdi.c:9438 pri_fixup_principle:
Can’t mo
ve call (DAHDI/3-1) from channel 3 to 2. It is already in use.
[Oct 21 17:43:27] WARNING[4264]: chan_dahdi.c:9558
pri_find_fixup_principle: Spa
n 1: PRI requested channel 1/2 is not available.
— Hungup ‘DAHDI/3-1’
== Everyone is busy/congested at this time (1:0/0/1)
— Executing [0661049303@agents:3] Hangup(“SIP/223-00000021”, “”) in new sta
== Spawn extension (agents, 0661049303, 3) exited non-zero on
— Executing [h@agents:1] GotoIf(“SIP/223-00000021”, “0?3:2”) in new stack
— Goto (agents,h,2)
— Executing [h@agents:2] AHEventsProxy(“SIP/223-00000021”,
ATE_CALL::::1382377407”) in new stack AHEventsProxy: Channel [SIP/223-00000021]. Data
— chan is SIP/223-00000021
AHEventsProxy: Send To CtiServer: socket:[89]. message:[41,1382377407^^^^stcrpb
— Executing [h@agents:3] Hangup(“SIP/223-00000021”, “”) in new stack
== Spawn extension (agents, h, 3) exited non-zero on ‘SIP/223-00000021’
— SIP/224-00000020 is ringing SRVRADIO*CLI>
Disconnected from Asterisk server Executing last minute cleanups

8 thoughts on - Issue After Install Dahdi

  • A VERY OLD and beyond EOF version. If you MUST, due to some driver issue, use Asterisk 1.4, then please use 1.4.44
    Otherwise I suggest you move to something more current, either version 1.8.current or beyond. Also, CLI says 1.4.43, your message says 1.4.32 ???

    Some examination of chan_dahdi and your dialplan would help someone give you some assistance. Is this a fresh install, or one that has been working for years?

    What Digium card?

    John Novack

    Salaheddine Elharit wrote:

  • hello yes this is a fresh install

    trunkgroup => 1,16
    spanmap => 1,1,1

    #include dahdi-channels.conf


  • If group 2 works the way you want it to, then it must be configured correctly;
    meaning you just need to configure group 1 to match group 2. So, *make a backup copy* of your chan_dahdi.conf first, in case this goes horribly wrong and you can’t even remember where you started from, and try:

    ;switchtype=euroisdn switchtype=qsig
    ;signalling=pri_cpe signalling=pri_net callgroup=1
    immediate=no channel => 1-15,17-31

    Then power the server off and on, to make sure DAHDI and Asterisk restart from scratch.

    If that works, congratulations, you’ve fixed it. However, I don’t think it will. “switchtype=euroisdn” and “signalling=pri_cpe” are the correct settings for plugging into an ISDN-30 exchange line. “pri_net” makes the card behave as though it was the exchange end (like FXS on steroids).

    Can you post the contents of /etc/dahdi/system.conf ?

  • 2013/10/22, A J Stiles :


    thanks for your response i have try to do this but the issue still the same

    NB: the group 1 is for the first provider and the secend is for the secend provider

    if the issue still the same can i call my provider becouse for the inbound call is ok bat the issue is for the outban calls

    below etc/dahdi/system.conf

    # Autogenerated by /usr/sbin/dahdi_genconf on Thu Oct 17 12:37:31 2013
    # If you edit this file and execute /usr/sbin/dahdi_genconf again,
    # your manual changes will be LOST.
    # Dahdi Configuration File
    # This file is parsed by the Dahdi Configurator, dahdi_cfg
    # Span 1: TE2/0/1 “T2XXP (PCI) Card 0 Span 1” (MASTER)
    # termtype: te bchan=1-15,17-31

    # Span 2: TE2/0/2 “T2XXP (PCI) Card 0 Span 2”
    # termtype: te bchan2-46,48-62

    # Global data

    loadzone = fr defaultzone = fr

    thanks and regards

  • hi

    the issue has been solved after change the span from span =1,1,0,ccs,hdb3
    to span =1,0,0,ccs,hdb3
    thanks for everyone

    2013/10/22 Salaheddine Elharit

  • Salaheddine,

    Just a comment here: I’m not sure who your spans are connected to but, it is highly unlikely that this changed is what fixed your problem. I think it’s more likely that the process of reloading something else actually fixed it. What you are doing here is telling span 1 to provide (or ignore)
    timing to the other end. If it’s the case that you’re connected to a public e1 pri provider, this probably isn’t the correct configuration and will likely cause further problems like slips and alarms. If it’s connected to something internal to your business, (like a channel bank), then it’s fine.

  • ok thanks for your comment i really appreciate it

    best regards

    2013/10/23 Russ Meyerriecks

  • Hello

    i check the dahdi-channels.conf

    in span 1 when i use it like below i can do my outband calls without issue

    ; Span 1: TE2/0/1 “T2XXP (PCI) Card 0 Span 1” (MASTER)
    context=from-pstn switchtype = euroisdn signalling = pri_cpe channel => 17-31
    context = default group = 63

    but when i add in channel 1-15 like: channel => 1-15,17-31

    i receive all the time this message

    chan_dahdi.c:9438 pri_fixup_principle: Can’t move call (DAHDI/3-1) from channel 3 to 2. It is already in use.

    WARNING[4264]: chan_dahdi.c:9558 pri_find_fixup_principle: Span 1: PRI
    requested channel 1/2 is not available.

    could you please help me

    thanks and regards

    2013/10/24 Salaheddine Elharit