[cisco-voip] Connecting multiple clusters together

[Wilusz, Mike]

Inter-cluster trunk

 

Mike Wilusz, CCNA

Networking Systems Programmer

Price Chopper Supermarkets / The Golub Corporation

 

 

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Micah Bennett
Sent: Wednesday, November 19, 2008 10:14 AM
To: Ryan Ratliff; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Connecting multiple clusters together

 

Ryan

 

Thanks for the info.  I am not familiar with all the acronyms.  Can you
tell me what ICT means.

 

Micah Bennett 
Telecommunications Admin 
Automated License Systems 
3055 Lebanon Rd, Ste 2301 
Nashville, TN  37214 
Extension: 2357 
Office: 615-263-4066 
Mobile: 615-207-0318 
Email: micah.bennett at als-xtn.com <mailto:micah.bennett at als-xtn.com>  
Website: www.als-xtn.com <http://www.als-xtn.com>  

________________________________

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Wednesday, November 19, 2008 9:10 AM
To: Micah Bennett; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Connecting multiple clusters together

 

Looks like you've got the basics down.  If the connection between
offices is data then just create an ICT pointing to the servers in the
other cluster (and do the same on their side) and use a route pattern to
route calls via the ICT.   Make sure the IP routing works to their
servers and from their voice vlan to yours and you'll be good to go.
For QOS between them ICT calls are just like H.323.

 

-Ryan 

 

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Micah Bennett
Sent: Wednesday, November 19, 2008 10:06 AM
To: cisco-voip at puck.nether.net
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081119/fb82b849/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 50929 bytes
Desc: image001.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20081119/fb82b849/attachment-0001.jpe>