eNoisy

Member

Last active 10 years ago

  1. 10 years ago
    Mon Jan 6 05:53:41 2014
    eNoisy started the conversation Revoking License.

    Good afternoon,

    i had a license installed on one PBX which got damaged. I cannot run the command to revoke the license on the working machine, what options do I have?

    Thanks,
    Juan

  2. 12 years ago
    Tue Oct 9 03:14:57 2012
    eNoisy started the conversation Phone book with existent database/table.

    Hi,

    I have all my contacts in a particular table called "contacts" in the database "asteriskcdrdb".
    I use this table for the CID lookup source.

    Is there anyway to tell the FOP2 phonebook to work with this existent information?
    What do I need to modify?

    Thanks In Advance
    Juan

  3. Wed Oct 3 02:27:50 2012

    Perfect!
    Thank you!

  4. Tue Oct 2 07:11:56 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

  5. Fri Sep 28 03:58:05 2012
    eNoisy posted in Need to transfer license.

    Solved. Please disregard this post.

  6. Fri Sep 28 03:50:11 2012
    eNoisy started the conversation Need to transfer license.

    Hi Nicolas,

    I have decommissioned our office's PBX as we upgraded hardware and the Elastix version.
    I just wanted to know how to transfer the FOP2 license onto the new PBX.

    Thank you,
    Juan

  7. Thu Sep 27 01:12:39 2012
    eNoisy started the conversation Monitoring DAHDI trunks properly (System 1).

    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

  8. Wed Sep 26 15:16:13 2012

    Hola Nicolás,

    Creo que antier te envié un reply en el que mencioné otro equipo y una configuración distinta, el cual tiene instalada una Openvox 100P. En caso de que sí la hayas recibido, peuedes incluirla en el post completo para seguirle el hilo a todo correctamente.
    Según tu última respuesta es claro que estás mezclando info de los dos sistemas de los cuales he posteado en el mismo post.

    Realmente nos ha parecido muy bueno el producto y con excelente presentación. Sin embargo la existencia de ciertos errores tiene un poco descontentos a nuestros clientes ya que ellos necesitan poder usar correctamente todas las funciones que se ofrecen y están "disponibles" para ellos poder usar en el programa.

    Agradeceríamos enormemente que por favor nos ayudaras a corregirlas. Si es posible sería excelente si pudieras concretar algun momento en el que nos puedas colaborar remotamente y yo poder simular las llamadas si es necesario.

    Los 3 problemas que tenemos son:

    1. No poder usar el whisper mode en una maquina de nuestra oficina.
    2. No poder mostrar los dahdi trunks correctamente en botones independientes. Elastix 1.6 y 2.3.
    3. Cuando se parquean llamadas, es posible hacerlo solo en 2.3 y no en 1.6. En 2.3 luego de parquear la llamada no es posible volverla a contestar.

    Gracias
    Juan

  9. Wed Sep 26 05:57:55 2012

    I already checked that option and in this PBX's case the channels names are in the DAHDI/X format.

    See 'core show channels' result below with two calls going on...

    EMS*CLI> core show channels
    Channel Location State Application(Data)
    DAHDI/5-1 (None) Up AppDial((Outgoing Line))
    IAX2/260-324 s@macro-dialout-trun Up Dial(DAHDI/5/04abcdefgh|300|TW
    SIP/211-0925cba0 (None) Up AppDial((Outgoing Line))
    DAHDI/1-1 s@macro-dial:7 Up Dial(SIP/201&SIP/211&SIP/212&S
    4 active channels
    2 active calls

  10. Mon Sep 24 01:29:31 2012

    Hi Nicolas,

    Thanks for your reply.

    I already tried what you suggested and using the channel names that are shown on 'core show chanels' does not make any difference.

    I just tried the option 'autoconfig-buttons-freepbx.sh' and these are the results (see below results for the DAHDI trunk buttons only - in tyhe order thay appear). It looks like that for some reason the trunk buttons get several channels assigned automatically.
    Any suggestion on how to correct this?

    [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/1]
    type=trunk
    label=ZAP/1
    queuecontext=from-internal
    privacy=none
    email=splitme- DAHDI/1
    seq: invalid floating point argument: DAHDI/1
    Try `seq --help' for more information.
    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

View more