FOP2 Community Forum

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

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

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

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

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

Hi!
The OOH323 custom trunk is not appeared on FOP2
autoconfig-buttons-freepbx.sh output is:

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

but I can't see the appopriate trunk button

Did. However, because then what version of the module has not changed, it had to uninstall and reinstall it, with the loss of settings fop2 buttons, groups and users

Please update to the latest beta...

done
new autoconfig-buttons-freepbx.sh don't found field "external"

FOP2 Buttons is cloned with each reboot dialplan. After 3 reboots I get a triple set of all elements of the panel

OK! It's not a bug, it's a feature.

Thank you, Nicolas!

Hi, Nicolas
Now I can hangup whole trunk only via HANGUP button on topbar.
It would be nice feature to have a reset single channel from the context menu, similar to the CLI function "channel request hangup <CHANNELNAME>"

.... Be sure to have the "all" permission in both read/write in /etc/asterisk/manager.conf...

read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate

...Another issue that I see is the dial extension with the g0/ prefix. Not that is horrible, but that behavior is new, and I think is not good, as you dial a number, the g0 is used by the dial command only...

This issue does not affect the display of channel status button. Вut I don't see channel status while DAHDI-->SIP is ringing.
**DAHDI/i1/100 ringing to SIP/6030 screenshot
[url=http://www.flickr.com/photos/56594160@N02/5227634625/:ex7qglin]*http://farm6.static.flickr.com/5124/5227634625_0854707b1a_z.jpg*[/url:ex7qglin]

And now call is answered**
[url=http://www.flickr.com/photos/56594160@N02/5227632049/:ex7qglin]*http://farm6.static.flickr.com/5288/5227632049_e8f514956e_z.jpg*[/url:ex7qglin]

....If it works of some calls, it should work for others as long as you have DAHDI/ix as channel names. In any case send me the debug output as before for the other type of calls, look at the device names there.

ОК, I will send it soon. There is no indications while DAHDI/iN/YYY rings to SIP extension. The indication is appears when call is timed out and transfered to voicemail system.
** *EDIT: The indication is appears when I pickup the phone too, but not while phone ringing. **

And to make it clear to other users, this happens with CUSTOM DAHDI TRUNKS for ISDN, not for regular DAHDI usage... right?

I think it's not a CUSTOM DAHDI TRUNKS for ISDN, it's STANDARD DAHDI TRUNKS for ISDN (DIGIUM Wildcard TE122). But new version of DAHDI and LibPRI used in Asterisk 1.8 was changed for best q931 support. Therefore, such a system of naming ISDN channels is standard for all installations of Asterisk 1.8

Yes, it works, but for SIP->Dahdi calls only. There is no indication for DAHDI->SIP call until it has been transfered to voicemail. I see call indication within voicemail prompt.
Also, I think "DAHDI/i$ZAPNUM" hardcoded in autoconfig-freepbx-buttons.sh is not suitable for a mixed installation of analog and digital DAHDI cards.

done