Post a Reply
2416 views

2 probs, fop2 unregisters and anonymous call when capturing

  1. 10 years ago

    servo

    16 Jul 2014

    So I have these 2 separate issues, and it would be great if someone could enlighten me.

    First: couple months ago I changed the server name from the generic localhost.localdomain to another name, since then, when the server has to be restarted for whatever reason I end up having to re-register FOP2. Sometimes the service just stops (very rare, only happened twice), and asks for registration once I start it back again.

    Second: When someone uses FOP2 to capture a call on another extension, it ends up changing the number which originally appeared correctly to "anonymous", not sure if it is meant to work like this or if there's something in the configuration that is not set up right.

    Overall I'm very happy with FOP2, its just these two things that keep bugging me, any advice or help would be greatly appreciated.
    Thanks.

  2. admin

    16 Jul 2014 Administrator

    If your hostname changes with every reboot, then you will lose registration. What is the ouutput from:

    /usr/local/fop2/fop2_server --test

    when you lose it? Does the license error includes (h) ? If so, then your hostname change is not "fixed", somehow the hostname on the server is being changed on every reboot (or at least changed since the last registration was made). So, having a stable hostname should solve that issue.

    As for the callerid on pickup, fop2 does not change callerids in any way. If it pickups a call it uses the Pickup manager action (that does not take callerid as a parameter). And whatever clid you see on buttons you see it because it appears on the AMI events themselves. FOP2 does not have "anonymous" on its code, that came from Asterisk events. Maybe a call pickup messed with the callerid internally in asterisk and the AMI events shows it as "anonymous"... it is hard to tell. The only way to verify would be by capturing the AMI events by setting debug level 15 to the fop2 server, and then inspecting the log and see those events after the pickup is done.

  3. servo

    16 Jul 2014

    Thanks for answering so quickly,

    This is the output:

    [root@voip ~]# /usr/local/fop2/fop2_server --test
    Flash Operator Panel 2 - Valid License (1)
    /usr/local/fop2/autoconfig-buttons-freepbx.sh: line 17: [: too many arguments
    Connection to manager OK!

    Its really weird, because it doesn't seem change the hostname or restart, or at least not that I have noticed, ill take another look at it but I have not changed it since the first time that I mentioned.

    Now when I lose the licence, I don't really see any errors, it just shows me the "free trial" version of FOP2 with up to 15 (?) buttons, that's when I notice something is wrong.

    On the second topic, I guess it might not be related to FOP2 since it doesn't change anything as you stated, thanks for clarifying that for me.

  4. admin

    17 Jul 2014 Administrator

    Run --test when you notice that it reverts to demo mode, and check the output at that moment.

    You should have notice that error on line 17, you can fix it by following instructions from this post:

    View Post 3587

    Best regards,

  5. servo

    21 Jul 2014

    Hi, been waiting for the weekend to restart the server manually and provide the output, and yes it gives me the (h) error.

    [root@voip ~]# /usr/local/fop2/fop2_server --test
Flash Operator Panel 2 - Invalid license for this install (h). Demo Mode
Connection to manager OK!

    I changed the name again, from voip.domain.local to just voip

    After that, I tried a few times to re-register, but its now giving me an error saying: "Serial code not available for registration!"

    Not sure what to do about that right now.

  6. admin

    21 Jul 2014 Administrator

    You cannot --register without --revoke done first. So, try --revoke, and then --register.

    And check why your hostname is being changed after every boot, it should remain the same.

or Sign Up to reply!