Last active 6 months ago
Thanks for the clarification.
I tried it, but still nothing appears in the FOP2 webclient, except the normal popup for an incoming call.
-- Executing [21@internal-phones:2] UserEvent("SIP/16_yeal-00000047", "ALERT,Family: alert,Channel: SIP/21_snom,Value: Urgent test for you~error~10") in new stack
Can you please give a real world example for the new alert plugin from 2.31.06?
I tried this:
same => n,UserEvent(FOP2CUST,Family: alert,Urgent test for you!^info&10)
But the syntax is possibly not correct.
Any update on this?
I would also like to see this feature.
thanks --register has now worked (after manual revocation) with the new server-binary version for AstLinux. The license sticks now on my testbox (64-bit)!
I rebooted 4 times including upgrading, downgrading and upgrading again. Thanks a lot for your quick help. I hope this new server version still works with non AstLinux systems. It would be great to have this addition in the next official FOP2 version.
OK, I created a ticket.
I tried it, but I cannot revoke or again register it:
License Revoke (or Activiation) -------------- Enter your serial code: xxxx Serial code not available for revocation on this machine!
Update: I upgraded from 2.31.01 to version 2.31.02 now, but still cannot revoke the license. And your new testversion always run as Lite version without revoking, so I cannot test the new version. But version 2.31.02 (official version) behaves better on reboots now.
OK. So why don't you simply check for a second partition if the first is FAT16? It it always there, has a label of "ASTURW" and it is ext2.
If you like, you can also check for AstLinux: if "/etc/astlinux-release" exists, the system is running AstLinux. With version 2.28 the license system worked fine on all of my customer boxes. Can it have to to with 32-/64-bit, we recently switched new systems to 64-bit?
Can you not check for the MAC-address of the NIC instead? This is static.
The revoke script would need a working internet connection, right? But sometimes the customer reboots because of problems with the internet, so this would not be a foolproof solution.
The partition UUIDs stay always the same after rebooting or upgrading (UUIDs faked):
/dev/sda1: SEC_TYPE="msdos" LABEL="RUNNIX" UUID="abcd-efg" TYPE="vfat"
/dev/sda2: LABEL="ASTURW" UUID="12345-67890" TYPE="ext2"
/dev/sda3: LABEL="ASTKD" UUID="23456-78901" TYPE="ext2"
Hi, I am using the AstLinux Linux/Asterisk distribution together with FOP2.
The distribution is firmware based. When I update AstLinux and reboot, FOP2 is then unregistered most of the time (after registering again it usually works then).
This is very annoying for my/your paying customers (and for me as well).
This problem didn't happen with v.2.28. I remember a similar FOP2 support case of one of my customers (MGOL-027050 from March 2016). It had something to do with EXT2/3 partitions.
On AstLinux the first partition is always a FAT16 partition (with the bootloader and system image), but the 2nd (and optional 3rd) partition(s) are always EXT2 formatted. The hard disk itself does not change after installation. Here it is explained:
Update: FOP2 2.31.01 is also sometimes unregistered after a simple reboot!
When you activate "Clickable Numbers" then you can dial e.g. phone numbers from websites, which are often listed in international format e.g. "+49 40 123456" without the plus sign this could also be a local number in Hamburg, Germany. In Germany we don't use the NANP (with fixed lengths) but have dynamic length numbers.
Since the Chrome Extension has no conversion rules, the only way is to do the filtering in Asterisk (e. g. "exten => _+ZXXX.,1,NoOp()").
Can it be the Chrome extension strips the leading "+" sign, when dialing international numbers (e.g. +49 40 1234567) ? Also in conjunction with the Dial Prefix in the configuration. That makes it difficult to route the route in Asterisk.