I have two freepbx SIP trunks, and a ZAP trunk (dahdi actually), to my verizon landline. The SIP trunks show up fine in FOP, but the ZAP trunk shows up as “MyLabel”. Looking in the /var/www/html stuff, I see this:
[CODE]
[Zap/*]
Label="MyLabel"
Extension=-1
Icon=3
Panel_Context=default
Position=54
[SIP/fpbx-1-nnnnnn]
Position=55
Label="fpbx-1-nnnnnn"
Extension=-1
Icon=3
Panel_Context=default
[SIP/fpbx-2-mmmmmm]
Position=56
Label="fpbx-2-mmmmmm"
Extension=-1
Icon=3
Panel_Context=default
[/CODE]
The trunk name in the freepbx config is “Verizon”. Any ideas why it does the above?
I would look in /usr/local/fop2 at autoconfig-buttons-freepbx.php and see what it is creating for buttons…
FreePBX erroneously assumes that FOP does not parse comments in chan_dahdi.conf. Quite to the contrary, it ignores the “;#” and proceeds with parsing “;FOP-operator”
The last “comment” happens to be “;# ;AMPWILDCARDLABEL(x):MyLabel” which instructs FOP to create a generic “MyLabel” trunk to reflect all “other”, i.e. not enumerated as extensions that far, Zap/* channels. I meant “Zap/*” since this is hard coded…
I developed a patch to fix that and other FOP Zap/DAHDI trunk buttons generation problems. See http://www.freepbx.org/trac/ticket/4462 for more technical details.
-Vladimir