Cant delete key from IP phone

[braindead2]

Hope someone can help, I have a 3300 on rel 5sp1 and I cant seem to delete a "single line" key from the handsets, which are IP 5220 dual mode. When I try to delete the keys I get the folowing fail/error message "users are assosiated with this hosted service" If I do locate number on the key number its just a non broadcast key..

For now I have created a dummy ip extn and added the key number to that, which in turn makes the key a multiline, and then I can delete from the origional extn, but now I cant delete from the dummy extn as its now back to a single line key..

Anyone came across this before..
any help appriciated
braindead

 

[caknfd]

I believe it has a name in the Telephone Directory. Delete the name then try and delete the key.

Craig

 

[Waldosworld]

Check your call rerouting forms, it is probably programmed as an answer point.

 

[kwbMitel]

it'll be the name

**********************************************
What's most important is that you realise ... There is no spoon.

 

[MyTel]

Do you have another Mitel controller, this number may exist on that system too as a remote directory number.... and may also have routing in place.

 

[braindead2]

Sorry for the time getting back, but been on holiday for easter..

Ok,
There's no name on the system for the non prime broadcast group number
There's no call routing 1st, 2nd, or always for the number
There's no other system(s) just an CIS & IQ server.

I have no idea what causing this issue.. wonder if a data save/restore would fix ?

Braindead

 

[LoopyLou]

You checked call rerouting for but did you check call rerouting to the single line?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[braindead2]

No, just checked and there are no call rerouting against the single digit number.

Braindead

 

[kwbMitel]

It won't be call routing as the system would tell you if it were. Ditto on RDN or most anything else.

The hosted service issue is a difficult one to resolve if the key is not named.

One confusing part is the "Single Line" when you are refering to a key that resides on more than 1 set. Firstly, I would only expect an error when trying to delete the last appearance and secondly, a key that resides on more than one set would not be a "Single Line". Clarification in this area may help.

I will put good money down that this will require Mitel TAC and the debug mode to remove the ervice.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[braindead2]

It is a single line as it only resides as a key on one phone. If I program the same key number on another phone, (a dummy EXTN for instance) then it changes to a multicall key, which means then I can then delete the key from the origonal phone, but now its back on the Dummy Extn as a single line which, I cant delete. As far as the customer is aware I have removed the key from the origonal phone and he is happy, but id still like to know why I can remove it from the system !

Im going to try a few other things to see if I can come up with a solution.

Thanks again
Braindead

 

[kwbMitel]

There are hidden forms that can only be accessed via debug mode.

In these forms everything that is dialable has a hosted service associated.

This is part of the SDS synch.

Usually, it is not an issue but I've run across it twice so far where I needed tech support to clean it up.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

As suggested might be screwed up in the database. If its not in the tel dir, not a call re route destination ( always, first or second ), not a trunk answer point, not a member of a hunt group, not in a pickup group then I can't think where else it would be.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[LoopyLou]

sorry or not in the local directory number form as well.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.