FOP2 Community Forum

@Fraser said:
/usr/local/fop2/fop2_server -v

It's also displayed on the home page of the admin panel http://<IP address>/fop2/admin

Only fop2_servers of 2.31.28 and above use TLS 1.2, so if you use 2.31.27 or lower, then you will need to upgrade your fop2_server otherwise things will stop working once Chrome self updates.

Wow!

Thank you for the quick reply. In my case, I cannot use the admin page since I manually configured everything. I run FOP2 on one server and point it to the PBX on another server.
The /usr/local/fop2/fop2_server -v command works fine.

This is a very helpful discussion and others can benefit from it, so whether the deloper or the users answer the question, it is still a useful resource.
One question I have: How do you tell which version of FOP2 is currently installed.
I THINK I have 2.31 installed and if so, based on above, I am good, but I'd like to confirm that (prior to Dec 31).
Is there a CLI command ?

@Ramblin said:
Let me use what you said back then and see if I can get that working. I'll let you know.

@nicolas
I have discovered something that may make sense to you and if so, could you please explain it to me?
When i I looked through your old post, you talked about adding channel descriptors that might be different than the ones in the button label.
So I tried changing the trunk names to see what that would do.
Well, in messing that up, I guess it made too many attempts with incorrect credentials on my trunk provider because I was booted - for about an hour.
When the trunk provider disabled the trunk, the trunk button on the FOP2 panel dimmed.
When I disabled the registration at my end, the trunk button on the FOP2 panel did not dim.
So apparently, only when the trunk is rejected by the trunk provider does the trunk button on the FOP2 panel dim - which is fine by me.
Does this make any sense to you and if so, can you explain why?

@Ramblin said:
@nicolas
I tried finding the old discussions on the Forum

I found the old exhange you and I had - back in 2013
forum.fop2.com/discussion/1919/unregistered-and-diabled-trunks-still-showing-on-fop2

It did remind me of some things I had forgotten, like the need to use a "real" extension - not a "fake" one created just to enable FOP2 to connect to Asterisk - if you wanted to see the toolbar at the top of the FOP2 Panel.

So I changed to using a real extension for signing in with FOP2 Panel and, sure enough, the Toolbar appears and it all works.

So you did try to help but I do not think I was knowledgable enough to know what to do with what you were saying.

Let me use what you said back then and see if I can get that working. I'll let you know.

@Ramblin said:
The Parking Lot button in the display Panel will light up and show there is a parked call when I send the call to the parking lot from the phone that originally picked up the call.
However, as soon as I hang up that phone, the Parking Lot button returns to nothing being shown.
The call is still parked and I can pickup the parked call by dialling 55556, as usual, but the Parking Lot button shows nothing while I am waiting for someone to pickup.

Problem solved, and it was not the fault of FOP2

I had been testing the functionality of the FOP2 Panel by dialing an Aastra phone and Parking the call.
When you use the built-in Park function of the Aastra phone, it creates a bridge between the incoming and outgoing calls (to the Parking Lot) instead of transferrring the incoming call to the parking lot. So when you hang up the Aastra phone, it must send a disconnect signal to FOP2.

When I instead used Blind Transfer from the Aastra phone to the Parking Lot, everything in FOP2 worked fine, with the Parking Lot button showing the call placed into the Parking Lot and continuing to show it there until the Parking Lot was picked up or timed out and transferred back to the phone.

So, moral of the story, use a blind transfer to go to the Parking Lot, NOT a bridge/conference.

Since I was only using FOP2 to monitor the status of my Lines/Trunk/Conferences/ParkingLot , I did not need the [fop2-park] context added to the dialplan on the Asterisk server, which for me is good since it allows me to keep the Asterisk server installation clean, which I like.

Thank you @nicolas for making this product and architecting it in a way that could be configured in non-standard (ie Wazo) installations.

@nicolas
Quite some time ago, when I installed FOP2 on another system, we exchanged emails about getting FOP2 to show the registration status of trunk like it shows the presence status of extensions (it dims when the trunk loses registration)
I tried finding the old discussions on the Forum but could not so I assume they were lost in the transition to the new forum - understandable since they were a while ago.
I am looking to install FOP2 on a new system (I will get a license when I get it working with the Demo version).
I have extensions and trunks properly showing their activity status and extensions showing when the extension is available or not (green or dimmed) and the trunks showing when they are active. But if a trunk loses registration, the trunk button stays green, not dimmed.
I am wondering if there is a EVENT I can add to the user configuration created in the AMI that would let the registration status be reflected in the button?
Something added to the list of eventfilters like

eventfilter=!Event: ExtensionStatus
That is in the user definitions file for FOP2 ?

@Ramblin said:
... it does nothing with Conference ; the botton shows but it does not chage regardless of activity.

I have Conferences working now - not Parking yet (see above) - but to get Conferences working I had to enter the heading differently

[CONFERENCE/1]
type=conference
label=Conference 1
extension=50000
context=Internal

The key for the Conferences working was just putting [CONFERENCE/1] as the heading not [CONFERENCE/50000] as I had been doing with the extensions and trunks.

Now if I can only get Parking to work ...

An update
With or without the fop2-park context added to the dialplan, I am able to have a button "see" the initial act of Parking a call with the button configuration in buttons_custom.cfg as

[PARK/parkinglot-1]
type=park
label=Parking Lot
extension=55555
context=parkedcalls

(parkinglot-1 was used when I monitored asterisk with "asterisk -rvvv")
(extension=55555 is the parking lot identifier with one slot)

When I do this, the Parking Lot button in the display Panel will light up and show there is a parked call when I send the call to the parking lot from the phone that originally picked up the call.
However, as soon as I hang up that phone, the Parking Lot button returns to nothing being shown.
The call is still parked and I can pickup the parked call by dialling 55556, as usual, but the Parking Lot button shows nothing while I am waiting for someone to pickup.

Does this give any clue why the ParkingLot button is not working as it should?

Keep in mind, I did NOT run any installation script after the MAKE command and all my configuration is done by manually editing configuraiton files on the server running FOP2. I am using FOP2 to monitor a Wazo (Xivo) installation so no FreePBX modules or script are usable on this installation..
Also keep in mind that FOP2 is on one server and Wazo is on another server, if that creates a difference. The connection is being made and the extensions and trunks are properly showing usage on the panel, but I wanted to point this out in case it is relevant to the solution.

Help?

I am trying FOP2 (v2.31.27) on a Debian 10 OS with ASterisk 17.
I cannot use the installation script since the systme in Wazo (Xivo fork) so I am trying the fully manual configuration after untarring and "make"ing the installation.
I have FOP2 runing on a remote server with the
/usr/local/fop2/fop2_server --test confirming Connection is OK
I can launch the Panel and it will properly show the stutus of Extensions and Trunks
However, it does nothing with Parking Lot or Conference ; the botton shows but it does not chage regardless of activity.
I did read the README and did try adding a fop2-park context on the asterisk server but no change.
I have treid every compbination I could think of for both CONFERENCE and PARK in the buttons_custom.cfg file but nothing seems to work.
Is there someting else I am supposed to do / add / edit to make Praking Lot and Conference monitoring work?
R

I am looking to install FOP2 on a Wazo (Xivo) system which is based on Debian 10 and uses PostgreSQL as the underlying database.
Are there any issues installing and using FOP2 with a PostgreSQL database?

Same question here. As I assume exists with most users. Thanks for asking.

If you want to log the manager output for debug, you can set the options line in /etc/sysconfig/fop2 like this
OPTIONS="-d -X 15 -l /tmp"

I changed (temporarily, that quickly started adding up to quite a log file) the settings in /etc/sysconfig/fop2 to the above and restarted fop2

The output.log populated very quickly but the error.log got no entries.

The entries in the output.log for Mktg_5 were

127.0.0.1       <- Event: PeerEntry
127.0.0.1       <- Channeltype: SIP
127.0.0.1       <- ObjectName: Mktg_5-in
127.0.0.1       <- ChanObjectType: peer
127.0.0.1       <- IPaddress: {IP_address_of_provider}
127.0.0.1       <- IPport: 5060
127.0.0.1       <- Dynamic: no
127.0.0.1       <- AutoForcerport: no
127.0.0.1       <- Forcerport: yes
127.0.0.1       <- AutoComedia: no
127.0.0.1       <- Comedia: yes
127.0.0.1       <- VideoSupport: yes
127.0.0.1       <- TextSupport: no
127.0.0.1       <- ACL: no
127.0.0.1       <- Status: OK (17 ms)
127.0.0.1       <- RealtimeDevice: no
127.0.0.1       <- Description: 
127.0.0.1       <- Server: 0

127.0.0.1       <- Event: PeerEntry
127.0.0.1       <- Channeltype: SIP
127.0.0.1       <- ObjectName: Mktg_5-out
127.0.0.1       <- ChanObjectType: peer
127.0.0.1       <- IPaddress: {IP_address_of_provider}
127.0.0.1       <- IPport: 5060
127.0.0.1       <- Dynamic: no
127.0.0.1       <- AutoForcerport: no
127.0.0.1       <- Forcerport: yes
127.0.0.1       <- AutoComedia: no
127.0.0.1       <- Comedia: yes
127.0.0.1       <- VideoSupport: yes
127.0.0.1       <- TextSupport: no
127.0.0.1       <- ACL: no
127.0.0.1       <- Status: OK (17 ms)
127.0.0.1       <- RealtimeDevice: no
127.0.0.1       <- Description: 
127.0.0.1       <- Server: 0

This was the same as the entries for the other channels (for which I had NOT yet added the extra channel in the fop2 admin) and no errors/outages were reported even though the registry did show No Authentication.

I don't know where to go now.

I was wondering if the timing settings were such that the Peer never realized the trunk was out, but:

• I had the same settings in the previous (fop1) system that did show trunk registration failures
• the registry settings are immmediately being seen
• I had left the (non-registered) state as is for 15 minutes so I thought that would allow any delays to be recognized

Something is different between ours systems though, since you are getting yours to work, so FOP2 is certainly capable of it. It just is not doing it with my configuration. All the other functinality is working (Extensions grey out when not connected, Conference, Park, Trunks show properly when being used, Toollbar Icon commands work, ...)

One thing I did try: On Mktg_8-out (another trunk, that the outbound routes are configured to use as the first one for local calls) I entered a bad secret in the Rgistration string and the Sip Registry recognized the trunk as Not Authenticated, yet, when I made a local call, Mktg_8-out was still used and the call was completed.

Then I entered a bad secret in the Oubound Settings, the Inbound settings and the Registration string and the Mktg_8-out trunk did NOT process the call; it passed to Mktg_7-out (as it is supposed to).

However, in neither case, did the error.log get any entries.

Is this helping to zero in on the issue?

If you have TWO separate names, one for inbound, one for outbound, you will have to specify the other/missing one in the channel field in the fop2 buttons freepbx admin page.
Example in fop2 buttons.cfg:

[SIP/Mktg_5]
type=trunk
...
...

If you have events received with SIP/Mktg_5-out, they will not match as they are in fact a different channel. So, add an extra channel, like:

[SIP/Mktg_5]
type=trunk
channel=SIP/Mktg_5-out
...
...

I think you may be on to something, but I am not sure I fully understand the solution (sorry for being dense)

Here is my FreePBX setup for trunk Mktg 5
http://docs.ayuda.ca/Mkgt_5-Trunk.jpg

When I tried to make the Trunk Name (Outgoing settings) and the Context Name (Incoming Settings) the same, I got an error message saying

Trunk Name and User Context cannot be set to the same value

so Ieft them as is, with the
Trunk Name (Top setting): Mktg 5
Outgoing Settings / Trunk Name: Mktg_5-out
Incoming Settings / User Conttext : Mktg_5-in

I added, using the FreePBX -> Other -> FOP2 Buttons, the additional Mktg_5-in Channel to my SIP?Mktg_5-out trunk and then

• rebuilt the buttons.cfg file using /usr/local/fop2/autoconfig-buttons-freepbx.sh > /usr/local/fop2/buttons.cfg
• restarted fop2 using service fop2 restart
  and I now have, in my buttons.cfg file the following entry for SIP/Mktg_5-out

[SIP/Mktg_5-out]
type=trunk
label=SIP/Mktg_5-out
queuecontext=from-internal
privacy=none
channel=SIP/Mktg_5-in
rtmp=0

I entered a bad secret in the registration settings for the Mktg 5 trunk and within a minute, the registration was reflected as bad, but the Trunk button did not change. I also noticed that I did not have any extra buttons in the panel for the Inbound trunk (should I have extra buttons for the additional channel?).

I noticed in your example, you used SIP/Mktg_5 not SIP/Mktgt_5-out in your trunk definition. I have "Mktg 5" as my (free-text) Trunk name but Mktg_5-out and Mktg_5-in as my outbound and inbound setting names. When I run the autoconfigure with

/usr/local/fop2/autoconfig-buttons-freepbx.sh > /usr/local/fop2/buttons.cfg

it automatically picks up the Mktg_5-out name.
Is that an issue?

I am guessing we are close and I appreciate you sticking with me on this; I hope I can "get it" quickly.

FOP2 shows sip peer status, including trunks.
Best regards,

Nicolas,

I get the fact that FOP2 shows sip peer status , NOT sip registry status.

What I do not understand is why FOP1 showed the trunk when it went unregistered but FOP2 does not.
Did something change between fop1 and FOP2?

I literally copied/pasted the trunk (and extension) settings from the old (64-bit CentOS 6.2, Asterisk 1.8, FreePBX 2.9, fop1) system to the new (64-bit CentOS 6.4, Asterisk 11, FreePBX 2.11, FOP2) system and on the fop1 system, when the trunk went out of registration, the trunk button "dimmed" but on the FOP2 system it does not change colour.

It may be that the same peer settings for the trunk or the same AMI settings are no longer sending the same status messages out, but I do not know how to check this.
Can you advise?

I have experimented on numerous trunks, but I will share with you the settings for one trunk (private info replaced by {content}) that I got by running

asterisk -rx 'sip show peer Mktg_5-out'

which produced

  * Name       : Mktg_5-out
  Description  :
  Secret       : <Set>
  MD5Secret    : <Not set>
  Remote Secret: <Not set>
  Context      : from-pstn
  Record On feature : automon
  Record Off feature : automon
  Subscr.Cont. : <Not set>
  Language     :
  Tonezone     : <Not set>
  AMA flags    : Unknown
  Transfer mode: open
  CallingPres  : Presentation Allowed, Not Screened
  Callgroup    :
  Pickupgroup  :
  Named Callgr :
  Nam. Pickupgr:
  MOH Suggest  :
  Mailbox      :
  VM Extension : *97
  LastMsgsSent : 0/0
  Call limit   : 0
  Max forwards : 0
  Dynamic      : No
  Callerid     : "" <>
  MaxCallBR    : 150 kbps
  Expire       : -1
  Insecure     : port,invite
  Force rport  : Yes
  Symmetric RTP: Yes
  ACL          : No
  DirectMedACL : No
  T.38 support : No
  T.38 EC mode : Unknown
  T.38 MaxDtgrm: -1
  DirectMedia  : No
  PromiscRedir : No
  User=Phone   : No
  Video Support: Yes
  Text Support : No
  Ign SDP ver  : No
  Trust RPID   : No
  Send RPID    : No
  Subscriptions: Yes
  Overlap dial : Yes
  DTMFmode     : rfc2833
  Timer T1     : 500
  Timer B      : 32000
  ToHost       : {provider_FQDN}
  Addr->IP     : {privider_IP_address}:5060
  Defaddr->IP  : (null)
  Prim.Transp. : UDP
  Allowed.Trsp : UDP
  Def. Username: {phone number}
  SIP Options  : (none)
  Codecs       : (ulaw)
  Codec Order  : (ulaw:20)
  Auto-Framing :  No
  Status       : OK (18 ms)
  Useragent    :
  Reg. Contact :
  Qualify Freq : 60000 ms
  Keepalive    : 0 ms
  Sess-Timers  : Accept
  Sess-Refresh : uas
  Sess-Expires : 1800 secs
  Min-Sess     : 90 secs
  RTP Engine   : asterisk
  Parkinglot   :
  Use Reason   : No
  Encryption   : No

Do you see anything in this setup that would prevent "sip show peers" from getting a failed trunk through to FOP2?

Well I found how to get to the web panel, I cant believe it doesnt tell you this anywhere I had to guess at it
http://ip_address_of_freepbx_server/fop2

You must not have tried very hard to find it

On the first page of the User Manual, the very first instruction - Login - explains that to you

pretty simple really.

Before you trash the documentation - which I find incredibly detailed and useful for a product being offered for free (up to 15 buttons) and only $40 (for unlimited buttons) - you may want to make the effort to actually read the documentation.

Nicolas has created a fantastic piece of software and provides excellent documentation and online support.

when I log in with xt and password it just sits there saying
"one moment please...connecting to server attempt number ...."

I had this as well.

Potential issuse (all covered in the documentation):

• Port 4445 not allowed (firewall issue preventing flash)
  disable your firewall and try it; if this lets it work, check your firewall settings
• (If using Firefox) Firefox insecrure websocket protection
  in firefox, typoe about:config into the URL bar and then change network.websocket.allowInsecureFromHTTPS to true
  restart firefox and try again

If these don't work, read the rest of the documentation, including FAQ

I do not do this purely to be nice to Nicolas. I am trying to save Nicloas from spending time on answering questions that are answered in his documentaiton so he can spend the time to answer my questions

The FOP1 panel used to show when the trunk went unregistered

Is there some coed I could take from that and try to integrate with FOP2?

I know I am harping on one bit of funcitonality here, but it was the ability of FOP1 to show when trunks went unregistered that allowed me to resolve an issue with a trunk service provider. They initially denied any issue at their end but by using FOP1's ability to dispaly trunk status, I was able to track the status and get the provider to fix (although never admit to ) the error on their end.

So I am hoping to retain that functionality in FOP2

FOP2 is a great piece of software and does many things FOP1 did not do. I am hoping to keep the one thing FOP1 did do that at this point it appears FOP2 does not do.

check "sip show peers" for your trunks

I disabled the trunk and then ran

asterisk -rx 'sip show registry'

just to make sure it was disabled and yes, it was.

I then went and ran

asterisk =rx 'sip show peers'

and it showed no problems

But the trunk was unusable

I waited for 10 minutes with the trun in a disablled status but it made no difference:

• sip show registry continued to show the SIP trunk as not Registered
• sip show peers continued to show no problems

The trunk was not usable for the 10 minutes that is was not registered, but FOP2 showed it as fine (using sip show peers)

Is there a way to get sip show peers to show the non-functioning trunK?
If not, is there a way to get the panel to reflect sip show registry as well as sip show peers?

R

We are many hours a day available at the live help, sometimes that is the best way to fix configuration issues.
If you do not see action buttons is because you are logged with an extension that is NOT listed in the extension

With your help, I think I just discovered an undocumented feature
I had manually established a user (I disabled the auto-config of users) in the fop2.cfg file (say johndoe) as
user=<johndoe>:<password>:all
to be the generic user who could monitor all extensions, trunks, ...

This allowed me to have "johndoe" act as a system administrator to diagnose connection status and issues. It might even be an outside contractor who does not have an extension. It really does not matter.

Now that I know about the need to have the user be an actual extension, I realize that the "johndoe" user could be intentionally set up for someone you want to have read-only status to the panel. No control icons, just read-only. Nice feature actually.

So yes, now that I have established, as a user, one of the legitimate extensions (mine), I can see the toolbar with the icons.
I need now to figure out how to do the lsiten and whisper feature so I can coach a new call centre employee, but I'll dig into that.

Thank you.
One item resolved - and yes, the root cause was user issue .

However, I still am not able to get the trunk button to show in the panel when the SIP trunk goes unregistered.
I signed in as the real extension user and manually disabled the trunk.
When I ran

asterisk -rx 'sip show registry'

it did properly show the trunk as Not Registered / No Authentication

Host                                    dnsmgr Username       Refresh State                Reg.Time                 
...
sip06.unlimitel.ca:5060                 N      5195940055         120 No Authentication                             
...
17 SIP registrations.

but the trunk button in the FOP2 panels stayed green througout.
I left the trunk in a Not Registered state for 5 minutes in case there was a lag issue with FOP2 or something, but no change - the button stayed green.

I hear you that the FOP2 panel uses AMI and I am using CLI commands, but the net is that the trunk loses registration so I would have expected the panel button to realize that.
When an extension is not registered, it greys out (regardeless of what user I sign in with), but not the trunks.

So maybe it is time to try a live interaction.
I am in the Eastern Standard Time zone.
Where are you and what would be a good time to try and use the live interaction?

Thanks for your help on this; it is a great piece of software and I'd like to get the configuration working fully.

I had the same issue

THen I realized that after I had sorted by buttons, I did not Sbmit the Changes -> Appliy Config

Did you do that and refresh your browser / clear the browser cache?

2. I did NOT run the
   /usr/local/fop2/generate_override_contexts.pl -write
   script, but it says this is not required; that it is an option if you want tighter FreePBX configuration
   RIchard

I did run
/usr/local/fop2/generate_override_contexts.pl -write
which did edit the files as described

I then restarted fop2 - no change
I then rebooted the system - no change

I still have:

• trunks not reflecting a loss of registration
• no icons in the Toolbar

I really like the FOP2 system design (heck I just bought 2 licenses); I'd like to get it fully functional