G3 V8 removing an x-ported Station issue

[phoneuser]

We have an issue where we are trying remove some x-ported extensions that have bridged-app buttons on another

x6001 is a 6408D+ with a phone associated and working

x6004 to x6009 are x-ported extensions with brdg-app of
6001 ...we get an error when trying to remove the brdg-app
of 6001 on the others (6004 - 6009) saying "identifier not assigned" when trying to blank said bridged button

you can not remove an extension until the bridged-app are removed

11/04 9:06 INADS dadmin cha station 6004 DENIED: -10003
11/04 9:06 INADS dadmin cha station 6004 DENIED: -10003

this is the error code we get ....possible data conflict
or corrupt ????

 

[SF0751]

Are you just blanking out the "6001" field, or are you removing the brdg-appr button altogether?

Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[phoneuser]

I am removing the Brdg-app button all together
FEATURE BUTTON ASSIGNMENTS

9: autodial Number: 6110
10: brdg-appr Btn:1 Ext:6001
11:
12:
13:
14:
15:
16:

*just depressing the spacebar to blank the brdg-appr
(even tried f4 Clear field option)
even if you tried it will not let you blank just the
btn or ext fields

FEATURE BUTTON ASSIGNMENTS

9: autodial Number: 6110
10:
11:
12:
13:
14:
15:
16:

*F3 to enter comes back with
FEATURE BUTTON ASSIGNMENTS

9: autodial Number: 6110
10:
11:
12:
13:
14:
15:
16:


Identifier not assigned
(this is what shows up on the command line)

maybe its me but I can not remember running into this in the past ....

 

[phoneuser]

Susan
I should be able to just enter even a different button type
right over the "brdg-app" button and then save ......
still comes up as ........Identifier not assigned
meaning 6001 brdg-app on 6004 (almost like it does not see 6001 as valid)
could it be a conflict or corruption ??? I have seen some strange things but this has me ?????

phoneuser

 

[SF0751]

Do you get the same results when you try to remove the bridged-appearance on the other extensions (6005 to 6009)?

Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[phoneuser]

Yes ....it seems to be 6001 is the common factor
but you can not remove x6001 until you remove brdg-app from other phones .....these test x6004 - x6009 were setup along
time ago ...since they were never really used we decided to
get rid of them and clean house.....(RTU issue )
remove all non used x-ported devices ....should have been built as VDN or Hunt Groups to save RTU

why they setup 6 x-ported extensions with brdg-app of
x6001 is beyond me .....

 

[SF0751]

Weird - can you remove x6004 through x6009 first (the entire station) and then delete 6001?

Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[tkinney]

I believe I got stuck like this on an ornery station and I had to busyout the station first then remove it. I hope it works!
Tina

 

[dufus2506]

The last time I saw this happen it was because Button 1 on the station was removed after it was bridged elsewhere. (Not at all sure how that happened!)

Is button 1 on ext 6001 still there?

Carpe dialem! (Seize the line!)

 

[phoneuser]

SFO751
Its x6004 - x6009 that we are trying to remove ...since they have brdg-app of 6001 it will not let you do that

no you can not remove any station with a brdg-app of another ...it should be simple just remove brdg buttons on x6004 - x6009 of x6001 (Enter)
and then remove x6004/ x6009 from programming (Enter)

there are 3 call-app of 6001 on x6001 btn 1-3
tried busy out command with same results .....

phoneuser

 

[SF0751]

Sorry - I got dizzy for a moment. Have you tried list usage extension 6001 to see if 6001 is anywhere else (like a hunt group, etc)?

Susan
"People seem not to see that their opinion of the world is also a confession of their character."
Ralph Waldo Emerson (1803 - 1882)

 

[orypecos]

When in doubt, reboot the pbx. I have seen that clear up a lot of corruption, if that is what it really is.

Da-vi'do

P.S. A message to all,if you want to get the best response to a question, please read FAQ222-2244 first. Also give the type & version of your voice mail & pbx system & preview your post to make sure it is complete & understandable. Be aware that if u don't answer a question, I usually will not continue to help u.

 

[tkinney]

First I would do the list usage that Susan suggested then I would print a copy of 6001's screens then remove it (at a convenient time for the user). Then remove 6001 from all of the stations 6004 6009 etc. and then remove 6004, 6009. Add 6001 back in. Thought is: perhaps if 6001 ceased to exist then you could remove its buttons from the others. I had a phone that just would not do what it was supposed to so I removed it and added it back in, works o.k. now....just a thought
Tina

 

[phoneuser]

Tina

*list usage only shows brdg-app on 6004 - 6009 of 6001
and not anywhere else
*Here is the problem I can not remove the brdg-app of 6001 on any phones (6004-6009) I want to keep 6001 and just remove 6004-6009 ....but you can not remove a phone until removing brdg-app buttons first (save) remove station xxxx
(save)
*As for 6001 not exsisting ....you would have had to remove the brdg-app of 6001 before removing 6001 ...and then add 6001 before assigning a brdg-app of 6001 to anything ...
it almost seems like it caught in the middle ....
does not mind that you have a brdg-app of 6001 ...just won't let you change or remove said brdg-app of 6001 on anything.......for giggles I may assign another brdg-app of 6001 and try to remove it from a complete different phone other then 6004-6009
*I will try the reboot of the system as its seems have an issue with just any phone that has a brdg-app of 6001 which is a known good working extension ......and what other kinds of issue could there be ....

Thanks for all your post while thinking back the customer lost power about a month or so ago maybe its just that it needs a gracefull shutdown and restart ...there were no isses when it came back up .....just wondering out loud