<![CDATA[Trunk Weirdness]]>I've got 71 DAHDI channels, split in to 2 groups. I want each group to show as a tunk button in FOP2. I believe I have the syntax correct in buttons.cfg:

[DAHDI/1]
type=trunk
label=T1-PRI1
channel=DAHDI/2
channel=DAHDI/3
...
channel=DAHDI/22
channel=DAHDI/23

[DAHDI/25]
type=trunk
label=T1-A&M-Wink1
channel=DAHDI/26
channel=DAHDI/27
channel=DAHDI/28
...
channel=DAHDI/70
channel=DAHDI/71
channel=DAHDI/72

However, in FOP2 I get 3 trunk buttons. One is just labeled "DAHDI", and the other 2 are both labeled "T1-A&M-Wink1". I placed an outbound call that went out on DAHDI/72 and it showed up like this:

http://linus.webboise.com/imghost/pics/2cec7e819a668d974c3b8cea54edeaed.png

Am I doing something wrong?

-Chris

]]>http://localhost:4567/topic/187/trunk-weirdnessRSS for NodeTue, 27 Oct 2026 04:39:13 GMTSat, 28 Nov 2009 22:39:53 GMT60<![CDATA[Reply to Trunk Weirdness on Mon, 30 Nov 2009 16:01:11 GMT]]>Just wanted to post the resolution in case anyone else runs in to the same problem.

In fop2.cfg I had specified 'buttonfile=buttons.cfg' to use my hand-edited button file, and was using #exec autoconfig-users-freepbx.sh to automatically generate the users. The autoconfig-users-freepbx.sh script also contains an exec to generate a button file. I commented out the exec line in autoconfig-users-freepbx.sh, and now it is working as expected.

]]>http://localhost:4567/post/842http://localhost:4567/post/842Mon, 30 Nov 2009 16:01:11 GMT<![CDATA[Reply to Trunk Weirdness on Mon, 30 Nov 2009 01:12:19 GMT]]>Hi,

Can you send me your entire buttons.cfg ? asternic AT gmail .

Best regards,

]]>http://localhost:4567/post/841http://localhost:4567/post/841Mon, 30 Nov 2009 01:12:19 GMT