Label reverts to extension number, queue has name

fnbit

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.

fnbit

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.

fnbit

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

fnbit

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.

fnbit

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.

nicolas

FOP2 will rename button labels for queue member names if the extension/context configured for a button matches a Local/exten@context queue member.

fnbit

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.

fnbit

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).

fnbit

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.

nicolas

The last fop2 version lets you disable the queue filtering when clicking the queue button in presence.js, so you won't have that issue. As for the button renaming, it only happens when a queue member of type Local/xxx@yyy matches extesion=xxx and context=yyy in a button definition, no matter if a member name was set or not. And the hack/workaround to avoid renaming is changing the queuecontext as I already explained.

Best regards,

fnbit

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.

nicolas

FOP2 by default does not hide unregistered extensions. Does not hide invalid queue member names. If you tweak styles to hide/change presentation, then using some client/presentation features might bring them back to view, as those feature set/unset css properties like display:none; etc. So, what you see is actually expected, you hide something via css but using filters, that set/unset css properties, they are displayed back.

As for the label names, I have no idea. I told you when and why fop2 renames labels, but it seems it is not your case. You use your own autoconfiguration scripts, I do not know those scripts nor I know your configuration as a whole. A FOP2 button is NOT renamed in any other case, only when a Local queue member is added that matches the extension/queuecontext of the buttons.cfg definition.

It is not clear either WHEN does the change happen. Is it in runtime? or whenever you restart fop2 in different ways? Perhaps you have TWO set of configurations you are not aware of, one when starting fop2 as a service, and another when starting from command line. This is a *wild* guess as your configuration is yours and there is not much info about it.