[cisco-voip] IP Trunk

Candace Holman Candace_Holman at harvard.edu
Mon May 3 16:23:05 EDT 2004


Wes,

Thank you very much!  Nice explanation too.  I corrected the 3.2 h323 
gateway to use the AllPhonesCSS and everything works now.

Candace

At 04:08 PM 5/3/2004, Wes Sisk wrote:
>Candace,
>
>I know of no means to "share" the partitions+css between the clusters, the
>signaling just is not there.
>
>The ability to call a speicific DN on the destination cluster is determined
>by the CSS assigned to the incoming device on the destination cluster.
>
>In your 3.2 cluster, you created an h323 gateway using either h225 or
>Inter-Cluster Trunk.  The CSS that you assigned to that device determines
>which DN's are availalbe to be dialed from the 3.3 cluster.
>
>/Wes
>
>
> > -----Original Message-----
> > From: Candace Holman [mailto:Candace_Holman at harvard.edu]
> > Sent: Monday, May 03, 2004 3:18 PM
> > To: Wes Sisk; cisco-voip at puck.nether.net
> > Subject: RE: [cisco-voip] IP Trunk
> >
> >
> > Wes,
> >
> > It works now, almost.
> >
> > I set up two test phones, a 7960 registered to the CM 3.2 and a 7970
> > registered to the CM 3.3.  Both are in an AllPhones partition, and each
> > trunk can call the AllPhonesCSS calling search space.  Each CM has
> > identical definitions for AllPhones and AllPhonesCSS.
> >
> > It works fine to call from a 7960 on CM 3.2 to a 7970 on CM 3.3, but it
> > does not work for the 7970 to call the 7960, *unless* I take the 7960 out
> > of the partition and mark the partition as None.
> >
> > It seems somewhat flakey that I can share partitions and calling search
> > space definitions between two clusters just by naming them exactly the
> > same.  Is there something else that must be done to extend partition and
> > calling search space definitions between clusters?  Or should
> > this just work?
> >
> > Thanks,
> > Candace
> >
> >
> > At 05:58 PM 4/12/2004, Wes Sisk wrote:
> > >Check the CCM 3.0(5) release notes for an interesting note about
> > how ICT's
> > >must be configured in CCM 3.0, 3.1 and 3.2.
> > >
> > >In 3.3 things change.  What do you see in CCM traces?  Is the h225 setup
> > >leaving the originating cluster?  Any messages in the destination cluster
> > >CCM traces?  How many servers in each cluster?
> > >
> > >/Wes
> > >
> > > > -----Original Message-----
> > > > From: cisco-voip-bounces at puck.nether.net
> > > > [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Candace Holman
> > > > Sent: Monday, April 12, 2004 5:45 PM
> > > > To: cisco-voip at puck.nether.net
> > > > Subject: [cisco-voip] IP Trunk
> > > >
> > > >
> > > > I'm trying to set up an IP trunk between a 3.2.2 and 3.3.3
> > cluster.  It
> > > > doesn't work.  They don't connect.  I set up the 3.2.2 as an H323
> > > > intercluster trunk and the 3.3.3 as an IP trunk.  There's not
> > much on CCO
> > > > for troubleshooting this.  Any references from the group?
> > > >
> > > > Candace
> > > >
> > > > _______________________________________________
> > > > cisco-voip mailing list
> > > > cisco-voip at puck.nether.net
> > > > https://puck.nether.net/mailman/listinfo/cisco-voip



More information about the cisco-voip mailing list