No trunks in FOP

[horses]

In the flash operator panel, trunks are not shown. Everything else is but that. I have searched here, FreePBX and the archives at asternic.org and haven't found a solution.

This is a recently installed piaf and all updates have been done. The only trunk I have is g0. I should see the four zaps there but do not. I have made calls through them its just no info in FOP.

Anyone have any clue how to fix it?

tk

 

[sanitycheck]

That happened to me when I installed Orgasmatron on a system without the Digium card installed, installing and configuring the card later. It just happened again on a new test Orgasmatron system where the card was not fully seated (setup couldn't see card).

I wonder if there is a way to have the flash panel rebuild the trunk list.

 

[foneman]

Some of us are having the same issue in the thread genzaptelconf?

We are also looking for answers/solutions

 

[sanitycheck]

Better question: Does the Orgasmatron release properly detect and add zap trunks to the flash panel if a zap card (any zap card) is installed during the installation?

Orgasmatron is a Mondo backup restore. If no zap card was installed in the system from which the original Mondo backup was made, maybe zap trunks never will show up. Your one shot to detect the card was spent during the initial setup of the master system from which the Orgasmatron image was made.

Which leads us back to: How can you get the flash panel to re-detect the trunks?

 

[jroper]

Hi

I've not really had the time to look into this in any detail as to why it is not working as advertised, however, there is a workaround.

instructions:-

nano /var/www/html/panel/op_buttons_custom.cfg

add the lines below, where ZAP is the technology, and 1 is the name of the trunk.

[zap/1]
Position=54
Label="Line 1"
Extension=-1
Icon=3
Panel_Context=default

[zap/2]
Position=55
Label="Line 2"
Extension=-1
Icon=3
Panel_Context=default

And so on.

Save the file. (ctrl x y)

Give it asterisk ownership

chown asterisk:asterisk /var/www/html/panel/op_buttons_custom.cfg

And you should be good to go.

Yours

Joe

 

[sanitycheck]

That solution works great. Thanks!

I see the "Position=" section needs to be checked against buttons already set in op_buttons_additional.cfg, so as not to have one icon written over another. I just started the Position= numbers in op_buttons_custom.cfg at the next open number in that section.

I had 4 (voip) trunks already appearing at 53, 54, 55, and 56 in "additional." I added my one zap pots trunk to Position=57, which placed it at position 5, bottom of the list, after the other 4 trunks.

 

[horses]

Perhaps that was it.

Maybe it was an initial detection of the card issue. I did have that, had to physically remove it then re-install it to gen it. Anyway, added the above to op_buttons_additional.cfg. I didn't have the custom.cfg. Anyway they show. I just need to get over there and plug in a line and see if it gives info now.

tk

 

[horses]

lost the changes

In an upgrade I lost the changes so I suppose the above file was overwritten. If I create custom.cfg is it already included somewhere else so it will get loaded or do I need to add it someplace?

tk

 

[jroper]

Hi

/var/www/html/panel/op_buttons.cfg has a #include at the top of the file to /var/www/html/panel/op_buttons_custom.cfg although on the installation I looked at, op_buttons_custom.cfg had not been created and included.

There is a file /var/www/html/panel/op_buttons_additional.cfg that is generated by FreePBX, and as with all _additional files with FreePBX, it is re-written after every FreePBX reload.

If you create the channels in FreePBX one at a time, e.g. zap/1 zap/2 etc, then they seem to appear on the FOP, but if you leave it as default g0, then it is not created. Which is probably a good thing, as showing 1 channel (g0) when there are in fact four channels is not going to be very helpful in FOP.



Joe

 

[horses]

That seems to have worked. Still have to go plug a line into it and see if the data comes through.
Mine was left at default g0. Strange under the old system I have running with g0 that it did show the four channels.
Thanks for the help

tk

 

[foneman]

Worked

I did not have the op_button_custom-cfg file so I copied the additional.cfg and renamed it to custom, removed all the other buttons except for the ZAP and viola, it worked...but am still having a SERIOUS issue of updating and such. When I run an update, it changes the zapata-channels.conf from
;;; line="1 WCTDM/0/0 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
context=default

TO
;;; line="1 WCTDM/0/0 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=default
and none of my ZAP DID inbound routes work. I have not run any updates since I just made the change so I wlll verify over the weekend to see if adding the custom.cfg file makes a difference.

 

[jroper]

Genzaptelconf does this which is run with update-fixes

 

[foneman]

Causes a BIG mess

Well, this causes a BIG MESS. If I run genzaptelconf -v, it changes the context which makes my inbound routes not work. I went all day Fri with call being asnwered by "I'm sorry, that number is not in service" as I use zap DID routing. Can this be changed back to not do this? I have run update-fixes several times and am not getting the desired results. Now that I know, I can always go and make the changes back manually but I have clietns out there and to have to do this to every machine when I run updates, is not effecient.

 

[jroper]

The problem is being addressed. Meanwhile, a work around is to copy the contents of your zapata-channels.conf into zapata.conf at the end of the file, and comment out #include = zapata-channels.conf and #include = zapata-auto.conf if it exists.

joe

 

[foneman]

As always

Thanks Joe and the rest of the Piaf gang. As always, much appreciated.