<![CDATA[Multiple Server configuration - trunk issue]]>I have a client with two Asterisk Servers (both running Freepbx)

FOP2 is working well, showing status of callers on both systems very well.

The issue is with the status of the trunks (one in Australia labelled Dahdi-syd and the one in New Zealand called Dahdi-nz).

The Australian trunk is an 10 Channel ISDN/E1/T1 (Dahdi1-10), the New Zealand one is 3 PSTN lines (Dahdi 2-4).

The important parts of the configuration are below for both buttons.cfg and fop2.cfg. Naturally we are not using the auto-config due to the two servers.

The issue is, that all the calls are showing that they are going out via the Dahdi-nz (which they are not - checked).

Could you explain further what the server1 and server2 variables are and what they effect. As you can see, from your instructions, I have added them. How are they used? and should there be a matching server variable in the FOP2.cfg so that the FOP2 can differentiate which dahdi line belongs to which server.

Hope you can help.....

Regards

Bob

current configs following

Buttons.cfg

[DAHDI/1]
type=trunk
label=DAHDI-SYD
channel=DAHDI/2
channel=DAHDI/3
channel=DAHDI/4
channel=DAHDI/5
channel=DAHDI/6
channel=DAHDI/7
channel=DAHDI/8
channel=DAHDI/9
channel=DAHDI/10
server=1

[DAHDI/1]
type=trunk
label=DAHDI-NZ
channel=DAHDI/2
channel=DAHDI/3
channel=DAHDI/4
server=2

======================================
fop2.cfg

[general]
; Elastix_AU Server AMI definitions
manager_host=localhost
manager_port=5038
manager_user=fop2user
manager_secret=hill2climb
;event_mask=call,agent

; Elastix_NZ Server AMI definitions
manager_host=192.168.0.12
manager_port=5038
manager_user=fop2nzuser
manager_secret=wind2see
;event_mask=call,agent

; Daemon definitios
;listen_port = 4445
;restrict_host = www.asternic.org
;web_dir = /var/www/html/operator/fop2

; Global Config
language = en
poll_interval = 86400
poll_voicemail = 1
monitor_ipaddress = 0

master_key = 5678

; USER LIST
user=870:870:dial,transfer,hangup,pickup,record,meetme
user=860:860:dial,transfer,hangup,pickup,record,meetme
user=850:850:dial,transfer,hangup,pickup,record,meetme
user=561:561:dial,transfer,hangup,pickup,record,meetme
user=560:560:dial,transfer,hangup,pickup,record,meetme
user=562:562:dial,transfer,hangup,pickup,record,meetme
user=854:854:all
user=853:853:dial,transfer,hangup,pickup,record,meetme
user=852:852:dial,transfer,hangup,pickup,record,meetme
user=851:851:dial,transfer,hangup,pickup,record,meetme
user=815:815:dial,transfer,hangup,pickup,record,meetme
user=599:599:dial,transfer,hangup,pickup,record,meetme
user=563:563:dial,transfer,hangup,pickup,record,meetme
user=816:816:dial,transfer,hangup,pickup,record,meetme
user=813:813:dial,transfer,hangup,pickup,record,meetme
user=811:811:dial,transfer,hangup,pickup,record,meetme
user=564:564:dial,transfer,hangup,pickup,record,meetme
user=814:814:dial,transfer,hangup,pickup,record,meetme
user=520:520:dial,transfer,hangup,pickup,record,meetme
user=501:501:dial,transfer,hangup,pickup,record,meetme
;etc...

buttonfile=buttons.cfg

;#exec autoconfig-users-freepbx.sh

]]>http://localhost:4567/topic/108/multiple-server-configuration-trunk-issueRSS for NodeTue, 27 Oct 2026 04:01:12 GMTWed, 16 Sep 2009 22:34:27 GMT60<![CDATA[Reply to Multiple Server configuration - trunk issue on Thu, 17 Sep 2009 14:23:38 GMT]]>Thanks for the heads up Nicolas.

I was expecting this to be the answer, but wanted to make sure I wasn't missing anything obvious...

Regards

Bob

]]>http://localhost:4567/post/519http://localhost:4567/post/519Thu, 17 Sep 2009 14:23:38 GMT<![CDATA[Reply to Multiple Server configuration - trunk issue on Thu, 17 Sep 2009 12:08:00 GMT]]>Hi Bob,

This is an architectural limitation in FOP2. It hapens with any channel with the same name on different servers: a call in CHANNEL/NAME on Server 1 and another call in CHANNEL/NAME on server 2 will both match a button with CHANNEL/NAME no matter the server it is configured in the button file. The server in the button file is actually for tellling fop where to send action commands, but not to distinctively identified activity.

I might be able to make FOP2 aware of this situation in the future (not in the next release). I wanted to make fop2 super slim and fast, and because of that is that I am not taking into account the server a channel belongs too to account for status. Adding that will hit performance by a BIG factor, like in FOP1.

So, for monitoring DAHDI channels in multiple servers, or any other channel technology that shares the name between servers you will have to use two or more fop2 daemons. This is also possible and it should work fine. But you wont be able to display the buttons on the same fop2 screen unless you do some sort of heavy magic with dhtml.

Best regards,

]]>http://localhost:4567/post/518http://localhost:4567/post/518Thu, 17 Sep 2009 12:08:00 GMT