Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failing to call some extensions in a cluster.

Status
Not open for further replies.

Tinos

Technical User
Nov 5, 2014
710
BW
Hi all.

I have two 3300s that are clustered.3300(A) can call all the extensions on 3300(B) however 3300(B) can call most of the extensions on (A) except for 5 extensions that display INVALID when being called.
These extensions exist and are on the same extension number range with those being called successfully.
What could be causing this and how can it be fixed?
Thank you.
 
are the extensions listed as "Local Only"?
at the maintenance commands type "Locate number XXXX"

is your numbering plan set as 4-digits? if so, is ALL of your extensions set as 4-digits - and also you cluster IDs.
 
I don't have any Local Only extensions. All extensions are 4 digit length.
CEID is 6 digits.
Locate number XXXX on the 3300 were it exists returns positive but on the other 3300 it cant be located.
 
Locate Number XXXX tells you what exactly

It should tell you that it is an RDN with CEID Digits cccccc

Does it?

**********************************************
Any intelligent fool can make things bigger and more complex… It takes a touch of genius – and a lot of courage to move in the opposite direction.
 
Do those numbers clash with any of the cluster elements or routing digits?

********************************************************************************

Eighty percent of success is showing up
 
I ended up adding the extensions in the ARS digits dialled explicitly.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top