[cisco-voip] Connecting two Cisco CCMs

[Ryan Ratliff]

True, but you were correct that the general rule is don't let any device call back to itself.  

-Ryan

On May 10, 2010, at 9:30 AM, Lelio Fulgenzi wrote:

> I guess this is better defined by using the word system, you don't want a system to have access to route patterns that send a call back to itself. 
> 
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it. 
>                               - LFJ (with apologies to Mr. Popeil)
> 
> 
> ----- Original Message -----
> From: "Lelio Fulgenzi" <lelio at uoguelph.ca>
> To: "Ryan Ratliff" <rratliff at cisco.com>
> Cc: cisco-voip at puck.nether.net
> Sent: Monday, May 10, 2010 9:19:05 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] Connecting two Cisco CCMs
> 
> The unwritten (?) rule to help with this, is to not let an inbound trunk (whatever it is) have access to a route pattern that would send a call back to itself.
> 
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it. 
>                               - LFJ (with apologies to Mr. Popeil)
> 
> 
> ----- Original Message -----
> From: "Ryan Ratliff" <rratliff at cisco.com>
> To: "Tim Foo" <kinusca at gmail.com>
> Cc: cisco-voip at puck.nether.net
> Sent: Monday, May 10, 2010 9:11:20 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] Connecting two Cisco CCMs
> 
> There is the SRND (http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns818/landing_uc_mgr.html) as well as the admin and system guides (http://cisco.com/en/US/products/sw/voicesw/ps556/prod_maintenance_guides_list.html).
> 
> If you are migrating users you need to be extremely careful about preventing call routing loops.
> 
> -Ryan
> 
> On May 10, 2010, at 4:03 AM, Tim Foo wrote:
> 
> Hi,
>  
> How to create the Intercluster Trunk and whats an ic-trunks.. is there any Cisco Documentation on this. Basically i want to use this to migrate the Users from an OLD Cluster to a new Cluster One Site at a time..
> 
>  
>  
>  
> On Sun, May 9, 2010 at 3:56 AM, cips <cisco at cips.nl> wrote:
> On both clusters create an inter cluster trunk pointing to the other cluster. Set up the appropriate dialplans using the ic-trunks.
>  
>  
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Tim Foo
> Sent: zondag 9 mei 2010 11:07
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] Connecting two Cisco CCMs
>  
> Hi,
>  
> I have a pair of  CCM clusters , One is on CCM 4.1 while teh other is on 7.x , how do I interconnect both the Clusters so that users on One custer can call teh users on aanother clusters. The two Clusters are in teh same locations.
>  
> 
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
> _______________________________________________ cisco-voip mailing list cisco-voip at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> _______________________________________________ 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/20100510/de70ec5a/attachment.html>