Feature access code on another cluster element

[VeeDubb65]

I have two 3300's in a cluster running current software.

Both cluster elements have the same FAC for Loudspeaker paging.

Both elements have a single loudspeaker paging port configured using the onboard, dedicated port, and set to zone 1.

From a set with the right CoS attached to either element, I can dial the FAC and connect to loudspeaker paging for that element.

What I want to do is connect to cluster element A's loudspeaker paging from a set connected to cluster element b. I tried just dialing the CEID+FAC, and that waited for more input until it timed out. Then I tried CEID+FAC+Zone, and my set just says "Error."

Suggestions?

[sunspark]

The paging form is shared (sds) between clusters elements?

[VeeDubb65]

The paging form is shared (sds) between clusters elements?

No. Since it references PLIDs I assumed that page wasn't even a valid option for SDS sharing, or what effect it would have if it was shared.

[sunspark]

1st thing to check. From extension hosted in the second mivb, are you able to call extension hosted in the first element .

[VeeDubb65]

1st thing to check. From extension hosted in the second mivb, are you able to call extension hosted in the first element .

Yes. I can dial back and forth without issue. This phone system has been in place for about 4 years at a business large enough to need multiple controllers. The only issue is the specific one I've asked about: accessing a feature access code (loudspeaker paging specifically) on different cluster element.

[VeeDubb65]

Nevermind. I've got it all sorted out.

I went back to my Cluster Elements form to double check and make sure I wasn't just dialing the wrong CE.

I was dialing the right CE, but I realized there were two numbers. Clust Element ID Digits, and also Feature DN.

When I dialed the Feature DN plus my FAV for loudspeaker paging it worked fine.

[sunspark]

Alright