<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1498" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>We're pretty much a one cluster shop here with a legacy PBX for areas that
do not have network connectivity. We've dabled with intercluster trunks into our
test server without any problems, but I'm looking to develop a 'design guide' of
sorts for any future inter-system communications that we may eventually look at,
most notably, a beta cluster we are setting up.</DIV>
<DIV> </DIV>
<DIV>I know that there is a general rule of thumb that says you should not allow
a system to access route patterns that would route a call back to itself, but
I'm wondering about some other issues:</DIV>
<UL>
<LI>How to grant/inherit trust from one system to another, both internal where
the trust is assumed and external, where the trust is, well, not always
there.</LI>
<LI>How to design the network, i.e. fully meshed systems or
piggy-backing?</LI>
<LI>How to design route pattern groups, i.e. based on where the source can go
or based on where the destination is?</LI></UL>
<DIV>While I do appreaciate any links, I would like to be able to talk to
someone who's worked with intersystem design.</DIV>
<DIV> </DIV>
<DIV>Hope someone out there can help....</DIV>
<DIV> </DIV>
<DIV>Lelio</DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>mob lawyer: your people insulted my brother.<BR>dr. house: what? romano in
the parmesan cheese shaker again?</DIV>
<DIV> </DIV>
<DIV> <BR></DIV></BODY></HTML>