[cisco-voip] Debug on Inter-Cluster Trunk

[Lelio Fulgenzi]

This is a common issue when all the subscribers in the cluster are not 'linked' to the subscribers in the other cluster.

Bascially, when you create an inter-cluster link, you have to create it on the publisher of cluster A to each of the subscribers of cluster B and vice versa. 3.3 (I believe) and higher allows you to create one link and add up to 3 extra IP addresses.

This should fix it tickety-boo.


--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
...there's no such thing as a bad timbit...

  ----- Original Message ----- 
  From: Christopher M. Bomba 
  To: cisco-voip at puck.nether.net 
  Sent: Wednesday, March 14, 2007 4:26 PM
  Subject: [cisco-voip] Debug on Inter-Cluster Trunk


  I have two CCM clusters.

  Cluster A

  Cluster B

  They are connected via inter-cluster trunk.  Cluster B is also connected to a PBX using a 6608 blade.

  CCM A ---ICT--- CCM B ---6608--- PBX

  When a phone from CCM A calls a PBX phone I get CLID and Name.  When a PBX phone calls a phone on CCM A I only get CLID.  Is there a way to run a debug on a trunk to see what is being sent from cluster to cluster?

  Thanks,

  Chris

  _______________________________________________
  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/20070314/768d6198/attachment-0001.html