Hi Ralph.
Well, there are 6 controllers in the cluster, but all the phones in all locations are registered to one controller (over metro-e).
The phones in question are all 5330e's, and they're in the same physical building as the primary controller that everybody's registered to. All three are connected directly to the controller via a StreamLine PoE, then right to the same switch as the controller itself, and the PRI is also in this building, so there's no WAN or metro-e traversal to speak of. In fact, they're within about ten feet of each other and all programmed effectively the same. (Same tenant, same zone, etc.) I did, however, just notice that the one ringing first has a manual zone assignment whereas the others are default, but they're still in the same zone regardless, since the default is zone 1. Curious if that might actually have something to do with it...
The release level is 6.0 SP3, active software load is 12.0.3.16.
The calls in question are either coming into the DID for that ring group, or being transferred to it from the receptionist (who is also in the same building.)
Thanks,
-dg
I've seen two occasions where I've seen what I would call a "cascading" ring.
Once was caused by a secondary dialtone being enable for the leading ARS digit for interpbx routing. Cluster Element ID Digits.
The second time was caused by a network issue where packets were being delayed across the WAN. It was only the control packets and not RTP.
How many systems are in your cluster?
What software rev are you at?
What type of phones are you using?
Are they run across a WAN?
Ralph