FOP2 Community Forum

Hi Ronald, You can run the autoconfig-buttons-freepbx.sh config script in the linux console and check its output. A Trunk button should list every channel on the pri with "Channel=" directives, something like: [ZAP/1] type=trunk label=My Pri channel=ZAP/2 channel=ZAP/3 .. If your modification was done in half, you might get something like: [ZAP/1] type=trunk label=My Pri channel=DAHDI/2[/color:3js302xk] And that will fail to monitor ZAP/2. I am just guessing, but that might be the issue you are having. Best regards, -- Nicolás

Ok thanks for the info. I thought it would work, and I do the same thing today with the original FOP. My preference is to connect to port 80 thru ssh as well, as opposed to ssl. This way, I only open port 22 and tunnel/encrypt everything thru that port and the PBX interface is not directly exposed to the Internet.

If its asterisk segfaulting, then you will have to follow their guidelines to submit the issue to their bugtracking system. What I can recommend is to test with a more recent asterisk version that might have already fixed that segfault. If the segfault is in fop2_server, then I would need to see the error when it crashes. You can start fop2_server from command line instead of an init script to watch for the error. Best regards, -- Nicolás