Ticket #493 (closed Bugs: fixed)

Opened 7 years ago

Last modified 6 years ago

ZAP trunks do not show in FOP

Reported by: dswartz Assigned to:
Priority: minor Milestone: 2.1
Component: Web interface Version: 2.0.1
Keywords: Cc:
Confirmation: Distro:
Backend Engine: All Distro Ver:
Backend Ver: SVN Revision (if applicable):

Description (Last modified by RyanCourtnage) 

I have two IAX2 trunks and a ZAP trunk.  Only the first
two show in the panel.  I have deleted and recreated
the trunk to no avail.

Change History

03/31/06 18:05:39 changed by versodom 

Logged In: YES 
user_id=1486059

Add This:

[ZAP/1]
Position=54
Label=PSTN Trunk
Extension=-1
Icon=3

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

You can also get there under Tools then Configedit then 
select /var/www/html/panel in the bar at the top of the 
page and then finally click on op_buttons_custom.cfg
cut and past the above into the box. Then hit the update 
button below the window and the hit Re-Read Configs in the 
top bar. Bring up your FOP and it will be there.

03/31/06 20:25:58 changed by dswartz 

Logged In: YES 
user_id=23177

your workaround didn't work for me.  i'm running freepbx
2.0.1, so maybe that makes a diff?

03/31/06 21:48:04 changed by versodom 

Logged In: YES 
user_id=1486059

Try this:

[ZAP/1]
Position=54
Label=PSTN 
Extension=-1
Icon=3
Panel_Context=default

03/31/06 22:17:35 changed by dswartz 

Logged In: YES 
user_id=23177

No joy...

03/31/06 23:08:33 changed by tommy13v 

Logged In: YES 
user_id=1292254

Did you restart FOP after making the change?

03/31/06 23:13:10 changed by dswartz 

Logged In: YES 
user_id=23177

well, i feel stupid.  no, i didn't.  i reloaded asterisk.  i
kickstarted FOP and now it works.  thx!

04/05/06 23:32:25 changed by RyanCourtnage

  • description changed.

retrieve_op_conf_from_mysql.pl will parse zapata.conf to determine which zap trunks/channels should be written to the FOP config.

I'm 'guessing' that you are using A@H, and that your zap config is in the zapata-auto.conf file, and not in zapata.conf. Can you please verify?

04/10/06 16:01:26 changed by versodom

You are correct, the zap config is in the zapata-auto.conf. What is the best way to fix this?

04/10/06 18:57:03 changed by wozto1s

  • milestone set to 2.1.

04/10/06 18:58:06 changed by RyanCourtnage

retrieve_op_conf_from_mysql.pl needs to be patched so that it is recursive when reading zapata.conf

04/15/06 22:12:03 changed by wozto1s

  • owner deleted.
  • status changed from assigned to new.

04/18/06 00:17:27 changed by anonymous

I've noticed this seems to also happen when creating new IAX trunk :(

04/25/06 12:45:13 changed by RyanCourtnage

  • status changed from new to closed.
  • resolution changed from None to fixed.

fixed in svn. We now also parse zapata-auto.conf

01/08/07 14:46:42 changed by

  • milestone deleted.

Milestone 2.1 deleted

01/08/07 16:29:32 changed by vgster

  • milestone set to 2.1.