Telephone Directory - 3300 4.1 SP1

[12345kevin]

We've just upgraded to 4.1 sp1 and the customer has reported that they are unable to program "external" telephone directory entrys with numbers that are in the "ARS" All existing similar entries that were there prior to the upgrade are still there !

The error shown is "No matching entry found"

We've probably missed something, although we've been through the release notes and anything else we can find !

Any idea's ?

 

[bobcheese]

I have tested this on a lab system. It worked fine for me. However I was able to replicate the problem. Here is what I found:

Your legnth of number in tel dir must match the number of digits specified in ARS excatley. If the ARS is 90207 & 7 to follow the tel dir entry must be 12 numbers long. If it is only 11 you get that error message.

Hope this helps

 

[12345kevin]

Most of the ARS entries have the correct number of digits to follow, or are set to unknown.

Have also tried putting the complete number in the ARS, but still getting the error ?

 

[LoopyLou]

What did you upgrade from?

There may be no i in team but there are three f's in fudge off.

 

[SXWizard]

I had this exact same problem this week on a new 4.1 system. It turns out that the system needs a PNI number programmed in the network element form for external tel dir entries to work. From the system Help file:

The Primary Node ID is used to route calls to other non-cluster elements in the network. Enter a value of up to seven digits in length.
Only the local network element PNI is manageable from this field, and only if the local network element does not belong to a cluster.
A PNI cannot appear as a directory number or as an ARS string on any of the systems in the network. Use the "Locate Number" maintenance command to determine if the PNI is a number that is already used on any of the other elements in the network.

I made my PNI 1999 which was an unused extension number.

 

[bobcheese]

Hate to throw a spanner in the works but check the 4.1 SP1 controller that I tested on yesterday and that doesn't have a PNI entered in the local network element but external tel dir entrys are fine.

 

[12345kevin]

Thanks all, got me on the right path.

It would appear that the "cluster element id" needs to be programmed in the Network elements form. Even though the system is standalone !

I just programmed this with a 1 and all is now OK.

 

[LoopyLou]

Hotdesking needs the cluster element ID as well so you can't go wrong programing it in.

There may be no i in team but there are three f's in fudge off.