Member
Last active 9 years ago
The queue filtering is a desired trait. The greyed out offline extensions showing up when clicked isn't (and not going away).
I don't understand the queue aspect. They login through QueueAddMember and show up as
RND Room (SIP/2551 from SIP/2551) (ringinuse disabled) (dynamic) (Unavailable) has taken no calls yet
and
[SIP/2551]
type=extension
extension=2551
context=sip
label=RND Room
mailbox=2551@default
when queue is shown. It works up until a restart.
We do not use Local/Extension channels for queues.
Also lastly clicking a queue and then unclicking it changes the interface to show once hidden offline extensions. (greyed out). This UI inconsistency is something I will need to fix as well.
I had asked in live chat. Here is my other issues as well. After the restart all extensions show again, even offline ones. As before using ./fop2_server --logdir ./ --debuglevel 3 corrects both issues and then starting with /etc/init.d/fop2 start fixed the issue (until next restart).
Again a restart has removed the names. The queue names are not using Local/exten@context. They are dynamically joined and use the Users Full Name.
And ignore my last last statement. I was able to hide unregistered extensions but clicking a queue and then unclicking it shows the grayed out extensions.
Please ignore my last statement I solved the unregistered display from this post:
http://forum.fop2.com/803-hide-offline-extensions/0
I am still curious why it occasionally shows extensions as labels though, I have seen this before on another client's install.
Also on an unrelated note how do I hide unregistered extensions? Current peer status is UNKNOWN, does it have to be UNREACHABLE? I am not sure how to do this with qualify in sip.conf
Odd behaviour. I stopped the service, restarted it with ./fop2_server --logdir ./ --debuglevel 3 and checked the panel. It had names. I killed it and started it with /etc/init.d/fop2 start and now the labels are correct. I am trying to reproduce the issue but get different results.
My main concern is it reverting over time.
Hi,
I am running 2.28 on asterisk 11-cert6.
I use a script called buttons_astcli.sh to generate my button file. It outputs:
[root@asterisk fop2]# sh buttons_astcli.sh
[SIP/1151]
type=extension
extension=1151
context=sip
label=User One
mailbox=115@default
[SIP/115]
type=extension
extension=115
context=sip
label=User One
mailbox=115@default
It is called from autobuttons.cfg which also contains some static entries
When I reload fop2 all users are labeled as extension numbers. Eventually (unknown why) they change to names. My queue is populated with names as well.
I can pm screenshots but as the system has personal info on it cannot do it here.
Hi,
Haven't installed FOP2 since 2.26. Was pleasantly surprised to see some new changes with 2.28 and installed it on a new phone system last night.
CentOS6
Vanilla Asterisk 11.6-cert6
I ran into some issues I though I should share (and my workarounds). I followed the installation docs on the fop2.com site.
I ended up going back to my autogen scripts to populate the interface as well as the users (and my custom button/group files) that I use for other installs. I just wanted to share any experience with you guys.
I like the manager interface either way and look forward to it maturing. I prefer the autogen method but I am a consultant so giving power to the client to make changes is always good.
I also am interested in the plugins listed in the manager interface. Can they be purchased or installed separately?
Also what does Final mean on the download page? Are you working on 3.0 now?
Thanks
F&B IT