Nicolas,

Thank you for that explanation. I now have a clearer understanding as to what to expect with FOP2. Unfortuately, I have no working experience with FOP1 so I realize that I am starting at a huge deficit. I want you to know that I have absolutely no issue with purchasing multiple daemons for my multiple servers, but even in this way, I don't see how I will be able to have a single screen that will show me all of my SIP trunks across my servers without simply taking the time to rename each and every trunk in a unique way. Given the value of your product in presenting the "big" picture, it is well worth my time in doing so.

On the other note, I do not know if you have completed or are interested in working through the auto configure script for third lane single or multi-tenant (MTE). If you are, then please allow me to help you in any way I can, including giving you access to a configured box with this software preinstalled.

I look forward to meeting you this year at Astricon and/or VON, both of which I will be attending with Josh.

Yours,
Harold Bondy

BTW,

I know you worked earlier in the week with Josh on my setup and I am very thankful for your efforts. I think the product is great. FYI, if you need access, I am running 1.6.1.0 Asterisk with Third Lane Multi-tenant and would love a script to import extensions and trunks. I have lots of both and can provide SSH to you if you would like.

Thanks Again
Harold

Sorry, but I am confused here. The example you showed was that DHADI/go on server 1 would resolve correctly over DHAH/g0 on server 2 if you explicitly specificed servers in the button.cfg file. WHat is different between the example above and using SIP/MAINTRUNK on both servers and applying the same explicit server=x definition in the button file?

Well, there sort of is a need to somehow separate the sections in a multi-user/multi-tenant setup (similar to departments). It would be nice to group all of the tenant A extensions together. Now, I know that I can simply just keep them in order in the button.cfg file, but the ability to put in subheadings like Extensions - Tenant 1, then Extensions - Tenant 2, etc... would be nice.

Otherwise the product is great.

Your example for viewing multiple servers says you need several instances in your fop2.cfg file. I am assuming that because the actual server x line is commented out that it is not meant to be in a "context" type [server 1] line.

However, I am finding with trunks (at least) that if I have the same name trunk in multiple servers (I do) (ie. SIP/MAINTRUNK) that even with the server=n line in the button.cfg file, FOP does not display properly. What is the answer to this?

Thanks
Harold