Great one Drago, all sorted now :)
I notice this is in the EV planning doc now too:
"To solve multiple Mediation Servers interacting with the same gateway peer entity, you need to configure multiple virtual gateways. Each gateway would be associated with a different FQDN, which DNS would resolve to the same IP address."
This brings me onto the next relevant point.
I now have two SIP trunks configured (although not yet both live so can't test) and I'm wondering what happens with respect to otbound calls and failvoer/load balancing. For the oubound routes I have added both SIP trunks as Associated Gateways but I'm not sure how Lync selects the associated gateway for the routing, is it round robin load balanced, on failover or something else? If it's failover, what determines a failure i.e. TCP timeout, SIP rejection etc?
My gateways are each associated with different colocated mediation servers so I'm not sure if that has an impact too. Without the live trunks I can't test this, so hoping somebody has already been through this.
What I would really like is an outbound load balanced setup so that I make use of all the concurrent calls I can on each SIP trunk as I can then purchase two SIP trunks and share the concurrent call charges across both, rather than having one idle whilst still paying for all the concurrent call costs.
The next step after that will be working out what Global Crossing do with their inbound load balancing of calls,
Jed
