As you know, you do not need to setup all of the parameters to get it to work.
<B>routedn</B> this a DN that is being used instead of external routing point in many oone connection. You do not need to use it.
<B>dnforunexpectedcalls</B> this one can be important depending on how you setup you environment. It is used by TServer when it receives a call on an external point that did not come from a different TServer. In other words, external point is reserved for calls between TServers. So when some idiot for some reason would place a call directly to your external routing point, TServer would then route it to DN you specify in this option. Be careful with this option if you have a really bad network delay!
<B>defaultdn</B> this is where you call would be dropped if your URS screws up and cannot figure out where to send the call. Note that there are also DefaultDN in Strategy definition, CDN, URS, TServer, Switch and PBX itself with the most precedence taken by the first object I mentioned. So, make sure you do not set it in more than one place. The best way is to leave it blank and have PBX set to handle defaults.
<B>translateaddry ype</B> don't know really, but never had to use it:) I guess it is when you want to have Genesys be aware if DN is local or not.
<B>extrouter_dn</B> this is set only if for some reason you would not want to use external routing points! DO NOT TOUCH IT, would be my suggestion.
<B> use ranslation </B> don't use it, unless you know how to add additional info to DN. In most cases, there is no need. I have only seen it used with Network Routing.
I have noticed that you have not mentioned coffeature, which for some reason is "false". Well, if you want your TServers to work, make sure you have it set to "true"
There are a lot of kool options that can allow you to do a lot of things, but my suggestion owuld be to get multisite working with a simplest possible layout and then move on from there
Vic
