Post a Reply
4269 views

Monitoring DAHDI trunks properly (System 1)

  1. 12 years ago

    eNoisy

    27 Sep 2012

    Hi.

    I decided to start this new post as obviously all the info from the different systems was mixed up in my previous post [url:bz960r3b]http://www.fop2.com/forum/View Post 1418[/url:bz960r3b]

    Starting from Scratch then...

    Elastix: 1.6-12
    FreePBX: 2.5.2.2
    Asterisk: 1.4.26.1
    Hardware: Openvox 110P (The E1 link only has 10 channels/lines)

    -----------------------------------------------------------------------------------------------------------------
    All the calls made on channels 1 to 9 are displayed only in the ZAP/9 button
    The calls made on channel 10 is displayed correctly on the Zap/10 button

    See results for the 10 DAHDI trunks when running /usr/local/fop2/autoconfig-buttons-freepbx.sh:
    ...
    [ZAP/1]
    type=trunk
    label=ZAP/1
    queuecontext=from-internal
    privacy=none
    email=splitme-1
    channel=DAHDI/1
    channel=ZAP/1
    rtmp=0

    [ZAP/10]
    type=trunk
    label=ZAP/10
    queuecontext=from-internal
    privacy=none
    email=splitme-10
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    channel=DAHDI/6
    channel=ZAP/6
    channel=DAHDI/7
    channel=ZAP/7
    channel=DAHDI/8
    channel=ZAP/8
    channel=DAHDI/9
    channel=ZAP/9
    channel=DAHDI/10
    channel=ZAP/10
    rtmp=0

    ...

    [ZAP/2]
    type=trunk
    label=ZAP/2
    queuecontext=from-internal
    privacy=none
    email=splitme-2
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    rtmp=0

    [ZAP/3]
    type=trunk
    label=ZAP/3
    queuecontext=from-internal
    privacy=none
    email=splitme-3
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    rtmp=0

    [ZAP/4]
    type=trunk
    label=ZAP/4
    queuecontext=from-internal
    privacy=none
    email=splitme-4
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    rtmp=0

    [ZAP/5]
    type=trunk
    label=ZAP/5
    queuecontext=from-internal
    privacy=none
    email=splitme-5
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    rtmp=0

    [ZAP/6]
    type=trunk
    label=ZAP/6
    queuecontext=from-internal
    privacy=none
    email=splitme-6
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    channel=DAHDI/6
    channel=ZAP/6
    rtmp=0

    [ZAP/7]
    type=trunk
    label=ZAP/7
    queuecontext=from-internal
    privacy=none
    email=splitme-7
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    channel=DAHDI/6
    channel=ZAP/6
    channel=DAHDI/7
    channel=ZAP/7
    rtmp=0

    [ZAP/8]
    type=trunk
    label=ZAP/8
    queuecontext=from-internal
    privacy=none
    email=splitme-8
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    channel=DAHDI/6
    channel=ZAP/6
    channel=DAHDI/7
    channel=ZAP/7
    channel=DAHDI/8
    channel=ZAP/8
    rtmp=0

    [ZAP/9]
    type=trunk
    label=ZAP/9
    queuecontext=from-internal
    privacy=none
    email=splitme-9
    channel=DAHDI/1
    channel=ZAP/1
    channel=DAHDI/2
    channel=ZAP/2
    channel=DAHDI/3
    channel=ZAP/3
    channel=DAHDI/4
    channel=ZAP/4
    channel=DAHDI/5
    channel=ZAP/5
    channel=DAHDI/6
    channel=ZAP/6
    channel=DAHDI/7
    channel=ZAP/7
    channel=DAHDI/8
    channel=ZAP/8
    channel=DAHDI/9
    channel=ZAP/9
    rtmp=0

    -----------------------------------------------------------------------------------------------------------------
    Results for 'core show channels' when making a call on the DAHDI/5 trunk

    Channel Location State Application(Data)
    DAHDI/5-1 (None) Up AppDial((Outgoing Line))
    IAX2/260-4912 s@macro-dialout-trun Up Dial(DAHDI/5/04xxxxxxxx|300|TW

    NOTE: All the trunks report same format DAHDI/X-1
    ----------------------------------------------------------------------------------------------------------------

    Configuring the field "Zap/Dahdi Channels (Eg: 1-24)" for each trunk under FreePBX - FOP2 Buttons:

    If I put just the channel number for every trunk it monitors as described above!
    Trunk: OUT_X
    Label: ZAP/X
    Zap/Dahdi Channels (Eg: 1-24): X

    If I put DAHDI/X for every trunk as suggested by you on many posts, it does not monitor any trunk at all

    ------------------------------------------------------------------------------------------------------------------

    I tried configuring the file fop2.cfg and uncommented ;buttonfile=buttons.cfg

    I wrote all the button configuration into the file buttons.cfg and modified the trunk buttons as follows (Is this correct???). Restarted service fop2, logged into the GUI and all the buttons are duplicated (No monitoring at all for the DAHDI trunks)

    [ZAP/1]
    type=trunk
    label=ZAP/1
    queuecontext=from-internal
    privacy=none
    email=splitme-1
    channel=DAHDI/1
    channel=ZAP/1
    rtmp=0

    [ZAP/10]
    type=trunk
    label=ZAP/10
    queuecontext=from-internal
    privacy=none
    email=splitme-10
    channel=DAHDI/10
    channel=ZAP/10
    rtmp=0

    ...

    [ZAP/2]
    type=trunk
    label=ZAP/2
    queuecontext=from-internal
    privacy=none
    email=splitme-2
    channel=DAHDI/2
    channel=ZAP/2
    rtmp=0

    [ZAP/3]
    type=trunk
    label=ZAP/3
    queuecontext=from-internal
    privacy=none
    email=splitme-3
    channel=DAHDI/3
    channel=ZAP/3
    rtmp=0

    [ZAP/4]
    type=trunk
    label=ZAP/4
    queuecontext=from-internal
    privacy=none
    email=splitme-4
    channel=DAHDI/4
    channel=ZAP/4
    rtmp=0

    [ZAP/5]
    type=trunk
    label=ZAP/5
    queuecontext=from-internal
    privacy=none
    email=splitme-5
    channel=DAHDI/5
    channel=ZAP/5
    rtmp=0

    [ZAP/6]
    type=trunk
    label=ZAP/6
    queuecontext=from-internal
    privacy=none
    email=splitme-6
    channel=DAHDI/6
    channel=ZAP/6
    rtmp=0

    [ZAP/7]
    type=trunk
    label=ZAP/7
    queuecontext=from-internal
    privacy=none
    email=splitme-7
    channel=DAHDI/7
    channel=ZAP/7
    rtmp=0

    [ZAP/8]
    type=trunk
    label=ZAP/8
    queuecontext=from-internal
    privacy=none
    email=splitme-8
    channel=DAHDI/8
    channel=ZAP/8
    rtmp=0

    [ZAP/9]
    type=trunk
    label=ZAP/9
    queuecontext=from-internal
    privacy=none
    email=splitme-9
    channel=DAHDI/9
    channel=ZAP/9
    rtmp=0

    Thank you

  2. admin

    28 Sep 2012 Administrator

    Hi,

    You are misreading posts and configuring channel ranges incorrectly. You are not posting what is the actual channel range YOU wrote on fop2 buttons in freepbx for the DAHDI trunks, but according to the output, you are doing something like this:

    ZAP/1 - Channel Range 1-1
    ZAP/2 - Channel Range 1-2
    ZAP/3 - Channel Range 1-3

    Or something to that effect. By doing so, you are in fact duplicating channels on subsequent button configurations. So you have ZAP/1 button monitoring DAHDI/1, then you have a ZAP/2 button that is monitoring TWO channels DAHDI/1 and DAHDI/2 and so on.

    If you want to monitor them individually, why are you specifying a channel range then? The range is for grouping several channels into one button, that is the very definition of a trunk. One trunk/channel that will recollect many possible calls (or branches).

    What you did in buttons_custom by hand is correct, but you do not have to do a manual configuration without disabling an automatic configuration first, or you will end up with TRIPLE button settings.

    If you have a button in fop2 that monitors channel A, then you have another button that monitors channel A, then you have several other buttons that monitor channel A, then the only button that will work is the last one. I mentioned this also on a previous post.

    So, stop doing manual configurations, remove all manual settings if you did anything. And then go back to the FOP2 buttons page, remove ALL channel ranges for your DAHDI / ZAP lines, apply changes... then run autoconfig-buttons-freepbx.sh and inspect the output.

    You have to see DAHDI/1 in only ONE button, the first, and so on for the rest of the channels, and it will work as you expect.

    I think I said also that we are every day available on the live help, via chat we can reach to this point in 10 minutes, while writing this long posts both for you and for me takes much more, is confusing at best and does not bring us to a good port, at least not quickly.

    Best regards,

  3. eNoisy

    2 Oct 2012

    Hi Nicolas.

    Thanks for your reply.

    I have the best interest in solving this issue with the online help, however as you might recall I mentioned that I live in Australia, so you can imagine how the difference in time zones have made it impossible for me to find someone online while I am awake. If I knew at what times you are usually online (something I already asked before...) it would be much easier for me to stay awake and be able to find you online! :)

    While we manage to chat online...

    I don't know why you are assuming I'm configuring range of channels. It's all being configured automatically when I run the autoconfig-buttons-freepbx.sh script.

    What you did in buttons_custom by hand is correct, but you do not have to do a manual configuration without disabling an automatic configuration first, or you will end up with TRIPLE button settings.

    How do I disable the automatic configuration?

    So, stop doing manual configurations, remove all manual settings if you did anything. And then go back to the FOP2 buttons page, remove ALL channel ranges for your DAHDI / ZAP lines, apply changes... then run autoconfig-buttons-freepbx.sh and inspect the output.

    The result I posted is from a system with a freshly fop2 installation. I simply executed the autoconfig-buttons-freepbx.s and then went to the FreePBX buttons option and assigned channels to each button as I already explained:

    Trunk: OUT_X
    Label: ZAP/X
    Zap/Dahdi Channels (Eg: 1-24): X

    Being X a single number

    Once again thank you.
    Juan

  4. admin

    2 Oct 2012 Administrator

    Hi,

    In the zap channel fields you must put a range, if you want just ONE channel then the range is

    1-1
    2-2
    3-3

    Try that, then run autoconfig-buttons-freepbx.sh and inspect the output.

  5. eNoisy

    3 Oct 2012

    Perfect!
    Thank you!

or Sign Up to reply!