rcanavan

Member

Last active 12 years ago

  1. 12 years ago
    Sun Mar 11 01:31:17 2012

    Found this post: View Post 1208

    I am now showing the channels, but it is not showing up properly.

    Eg. I have a trunk which uses channels 1-47 ( private PRI ) and a trunk that uses channels 49-71 ( PRI from telco ).

    All channels appear to be coming in via the 1-47 trunk on the FOP2 panel now.

    EDIT: Upon further review it seems that Asterisk is not reporting the proper DAHDI channel in use. I make a call out which goes out via DAHDI channel 49, however it is reporting it under DAHDI/i3.

    I can only figure that Asterisk is grouping the trunks via an interface number.

    Due to this, I changed in FOP2 buttons to use 1-2 for the first two trunk lines ( two links spanned on one group ) and 3 for the last.

    This does not appear to work ( one of the trunk buttons light up but does not associate properly to the correct trunk ).

    EDIT: To single out the line in FOP2admin - Buttons, you need to set it to 3-3, otherwise it will generate the lines as if going from 1 to 3. This appears to have resolved the issue.

  2. Sun Mar 11 00:39:51 2012

    FYI - I removed the FOP2admin module and reinstalled ( 1.2.10 ).

    I added the line in php.ini max_input_vars = 2500 so that I could post the buttons form properly as the newer version of PHP only permits up to 1000 by default.

    I ran the autoconfig-buttons-freepbx.sh and the DAHDI lines do not appear to be showing up correctly still.

  3. Sat Mar 10 23:59:43 2012

    I have upgraded from Asterisk 1.6 to Asterisk 1.8 and found that the DAHDI channels do not show anymore as well. I have upgraded to FOP2 2.25 with the admin 1.2.10. When running autoconfig-buttons-freepbx.sh I get the DAHDI channels coming back without the i.

    Is there a setting I am missing in getting this back working?

  4. 13 years ago
    Wed Feb 2 21:31:20 2011
    rcanavan started the conversation Option to log panel activites.

    Ran into a situation where a user was being added to a queue. Not sure why this happened or who did it.

    This prompted the idea of having a log of activities of who did what when.

    This can be useful for tracking channel spy events, queue add / remove, call transfers, dials, etc.

    This log can also be used to show how often the panel is being used and for what purposes.