Are you using the free version with 15 button limit? or did you create a group limiting the button display? If the button config is generated, you must see the button, unless your view is limited by any of the reasons I mention...

I am using full version, trunk button included in a group, but don't appear on panel.

What do you mean by "don't displayed on panel"?

The button IS NOT in the pannel

or

The button IS on the panel but it does not reflect trunk activity?

The button IS NOT in the pannel

You mean you do not see activity? Or the button does not display? What is the output for the trunk when running autoconfig-buttons-freepbx.sh script when you add the channel field as ooh323/um in the fop2 buttons admin page?

Real trunk button (OOH323/UM/$OUTNUM$) don't displayed on panel

[OOH323/UM/$OUTNUM$]
type=trunk
label=UM
queuecontext=from-queue
privacy=none
channel=OOH323/UM

In fop2 admin you can add the OOH323/UM string onto the channel field for the normal custom trunk, and it should work fine, without adding an additional fake trunk in freepbx. Did you try that ?

Yes, but trunk button don't displays on panel at all with or without channel field.

What fake trunk definition? Can you clarify?

The real custom trunk with OOH323/UM/$OUTNUM$ dial string don't displays on FOP2 and don't properly detected by autoconfig-buttons-freepbx.sh.
Then I created another custom trunk with OOH323/UM dial string but with no inbound and outbound routes attached to it.
Now I have button from that "fake" trunk and calls from real trunk on it

Hi Eugene,

So, is it working now? confused... :roll:

Yes, it is working, but with the fake trunk definition in freepbx.

Then your button definition OOH323/UM must work. However, trunk lines will only be shown if the channel is bridged, in the capture above, the ooh323 channel is on state ringing. If that does not change to up at some point, it will not be displayed in fop2. Is the state changing to up later on?

Channel              Location             State   Application(Data)             
OOH323/UM-80         (None)               Up      AppDial((Outgoing Line))      
DAHDI/i1/100-204     s@macro-dialout-trun Up      Dial(OOH323/UM/301,300,t)     

No activity on button while talking too.
I see that call on DAHDI trunk button, but not on OOH323.
And I don't like my trick with the fake trunk, I think there is a more attractive solution for a get trunk name from custom dial string
ADDED It's works!!! I ran fop2 in debug mode and then revert to normal.

Please do the "core show channels" when you have calls up, so we can now what device/channel name to use.

core show channels
Channel              Location             State   Application(Data)             
SIP/6030-000000e5    s@macro-dialout-trun Ring    Dial(OOH323/UM/300,300,t)     
OOH323/UM-10         300@from-pstn:1      Ringing AppDial((Outgoing Line))      

config now is [code][OOH323/UM/$OUTNUM$]
type=trunk
label=UM
queuecontext=from-queue
privacy=none
channel=OOH323/UM
[/code]
but no trunk button
Can I stripe $OUTNUM$ by autoconfig-buttons-freepbx.sh?
Added
I try to create fake trunk with OOH323/UM dial string. autoconfig-buttons-freepbx.sh detect it and make [code][OOH323/UM]
type=trunk
label=OOH323/UM
queuecontext=from-queue
privacy=none
[/code]
Now I can view the trunk button, but with no calls on it

I do not think that the custom definition is ok, not sure how ooh323 channel is named after the call is set, but I think that /$OUTNUM should be stripped...

$OUTNUM$ is a freepbx variable, calling number on outbound call.
channel looks like OOH323/TRUNKNAME on CLI