Any comment on that?

Among all user rights, diial,hangup,meetme,pickup,record,spy,transfer,transferexternal,queuemanager,queueagent,phonebook,chat,preferences,hangupself,recordself,voicemailadmin,broadcast,sms,smsmanager

None of them enable the access to call history, I must put the right "all" to permit that, but I dont want to give access to all the feature since not all of them are supported by my PBX and I don't want them to spy or anything else.

Do you have any other rights that is not listed in fop2.cfg?

Or a method to set the right to "all" then disable certains like : user=299:1234:all,!spy

Every context in "setup" is in uppercase, although I always enter my contexts in lowercase...

33|SETTINGS|XXX|noExtenInLabel|false
9|SETTINGS|GENERAL|noExtenInLabel|true

I remember having issue with some originate before where FOP2 try to call the context in asterisk in uppercase and the originate failed because of that.

I change it manualy and now it work : update setup set value = 'true' where context = 'XXX' and parameter = 'noExtenInLabel';

Thanks for the sqlite thing, I see others setting I can check, like the language who is set to fr_FR in general but still "en" in my context.

http://your_server.com/fop2/admin/pagebs.fop2settings.php

page 2 noExtenInLabel => yes

I dont have any option to chose the context

I use the "enableDragTransfer" option and it work fine for default and my context.

After making some tests with your latest version 2.31.06, I finaly understand why noExtenInLabel doesnt work for certain and work for others.

If you configure your users/buttonfile in the "general" context of /usr/local/fop2/fop2.cfg and call your fop2 : http://your_server/fop2, it work fine

BUT...

If you configure your fop2 to be multi-tennant and configure your users/buttonfile in a custom context, exemple :

[blablabla]
user=blablabla1000:5555:all
buttonfile=buttons_blablabla.cfg

then call you fop2 with the custom context : http://your_server/fop2/?context=blablabla

The noExtenInLabel doesnt work anymore, even if your activate it in the admin menu or in the presence.js file.

I tried 418-123-4567*890 and 418-123-4567,890 and in both case, FOP2 remove the non numeric caracter and tried to send 4181234567890

-- PROCESS_FLASH_COMMAND origen 38 accion dial destino 4186680745245 password XXXXXXXXXXXXXXX
VALIDAR USUARIO XXXXXXX@XXXXXXXX
validate password using key XXXXXXXXXXXXXXXXXXXXXX
VALIDAR USUARIO XXXXXXXXX OK con clave regular

127.0.0.1 -> Action: Originate
127.0.0.1 -> Channel: Local/XXXXXX@XXXXXXX
127.0.0.1 -> Exten: 4181234567890
127.0.0.1 -> Context: XXXXXXXX
127.0.0.1 -> Priority: 1
127.0.0.1 -> CallerID: test <XXX>
127.0.0.1 -> Variable:
127.0.0.1 -> Async: True

127.0.0.1 <- Response: Error
127.0.0.1 <- Message: Extension does not exist.

I want to use the google chrome extension to dial numbers via a web page but some of my numbers have en extension after it like XXXXXXXXXX*XXX or XXXXXXXXXX,XXX.

Only the first part is detected.

Is there a way to make to full number clickable? Or maybe in the future, have an option to put a custom regex for the number detection?

I search for a way to know to license number of an active FOP2 but it dont seem to be any.

If you can tell me a command for fop2_server or fop2 CLI to show the license number or I can send to you my licence number so you can tell me the IP address attach to it.

Thank you.