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 Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Local-Only Form

Status
Not open for further replies.

cdpak

Vendor
Feb 17, 2009
105
US
MXe 3300 4.2
I have number that is listed on the Local-Only form. That I cannot find in any other form to delete. I have removed it from all IP sets multicalls keys. I do not see it on the "Multiline Appearence group" form. I removed it from all Voice mail forms. I don see it in, Analog Sets, Analog Trunks, Digital trunks, All Call Reroute forms,Associated Directory numbers, Remote directory, Trunk groups, hunt groups, page groups, Ring groups. Any other ideas?

Thanks you
 
I get "number not in use". But it is still there in "Local-Number Directory".
Thanks caknfd for the reminder. I now remember that command from class.
 
You have a cluster with the local number form shared? Check for the extension on one of the other controllers in the cluster.

The single biggest problem with communications is the illusion that it has taken place.
 
There are two controllers in the cluster. The 2nd is for resiliency only. There are no extensions on it. When I do a "Locate Number" on the 2nd controller. It only referes to the Remote Directory listing only.
 
I reckon this is a bug, I have the same thing on a site and spoke to TS who couldnt replicate the issue and even after a datasave/data restore could still not change it or delete it. is it one of your voicemail ports by any chance ?
 
No it wasn't a VM port. It was a multicall key. I had to have Mitel get in to the controller via debug and remove it off the Local Directory.
 
I ran into this exact issue today and found this thread trying to find a solution. I thought I'd post my solution just in case anyone else runs into the same problem and finds this thread down the line.

It seemed to have been caused by multicall keys that were assigned as local-only numbers on clustered DNs during a migration to RDN synchronization sometime in the past. Removing the key assignments on these phones does not remove the number from the local-only list.

I was able to remove the number(s) from the local-only form by simply creating a local-only DN in the Multiline Set IP Config form and then deleting that DN from the User Configuration form. It then removed the numbers needed from the local-only form and I was able to assign the key on the clustered phones again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top