[cisco-voip] Connecting multiple clusters together

Micah Bennett mbennett at als-xtn.com
Wed Nov 19 11:35:23 EST 2008


Thanks for the doc.  Ill take a look at it.  

 

Is the reason for 6 ICTs because I will have an incoming and outgoing
between each location.  Basically an IN and OUT on each side of the
triangle.

 

Micah Bennett 
Telecommunications Admin 
Automated License Systems 



  _____  

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Wednesday, November 19, 2008 10:30 AM
To: Micah Bennett
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Connecting multiple clusters together

 

You can connect clusters together via PSTN gateway, e.g. T1s or via IP,
e.g. intercluster trunk.

I would investigate an intercluster trunk. Very easy to setup and you
add it to a route group. If you have more than two clusters, you can
still use an intercluster trunk, but then you have 6 trunks instead of
two, basically fully meshed. Still manageable, but more than 3 you
should consider a gatekeeper.

This page should help you out:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note0
9186a0080094729.shtml


---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"Bad grammar makes me [sic]" - Tshirt


----- Original Message -----
From: "Micah Bennett" <mbennett at als-xtn.com>
To: cisco-voip at puck.nether.net
Sent: Wednesday, November 19, 2008 10:05:58 AM GMT -05:00 US/Canada
Eastern
Subject: [cisco-voip] Connecting multiple clusters together




Are there any documents or can anyone comment on what is needed and how
you go about connecting multiple call manager clusters together. 

In the next few weeks and months I expect to be connecting to our new
parent company.  I believe they are on CCM 3.x.  We are on CCM 4.2(3).

They are using IPCC 3.x and we are using IPCC 4.x.  I know that they
have two offices using CCM.  I don't know if its one cluster or two
clusters.  I believe it is just one.  I don't know of any plans or need
to integrate the IPCC portions at this time, but I do believe we want to
establish office to office extension dialing as soon as possible.  

Here are some of the things I think I know.  

1.      We are going to need some type of connection to them.  I assume
this would be a T1 at minimum.  If it is one cluster, we should only
need one to the main location.  If there are two clusters we will need a
connection to both.  Our network is using Sprints MPLS cloud.  We should
be able to drop connections from those two new offices directly into the
MPLS cloud that we are already connected to. 

 

2.      Traffic between the locations will use G729 to get the best use
out of the smallest connection.  We do this between our existing two
locations.

3.      If they are using extension ranges that conflict with our
existing ranges, each office will need to do some type of translation to
avoid someone having to change extension ranges.  For example if they
have an ext 2352 and we have an ext 2352, we will need to assign a
leading digit to each office.  I might dial 6(2352) to get to them and
they would dial (7)2352 to get to me.

4.      Instead of routing calls to those offices extensions out to the
PSTN, I would route them across the connection to the other offices and
they would have routing set up to accept the digits I sent, and convert
them back to the proper extension for routing the call to the correct
location.

Am I on track so far, or is this totally wrong?

Thanks in advance.

Micah Bennett

Telecommunications Admin

Automated License Systems


_______________________________________________ cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081119/9ff40cb8/attachment-0001.html>


More information about the cisco-voip mailing list