Strange issue with a DN - seems 'stuck' to a specific TN?

[apridham]

I'm almost sure this must be a bug in the code, I have a ticket open with our telco, but maybe someone has seen this before..

1 -> I had a SCR DN assigned to a TN, let's say 5551234 assigned to 4 0 8 1
2 -> I outed the TN, as it was supposed to be taken out of service. Someone then lets me know that it's still required.
3 -> I went to recreate the TN with the SCR 5551234, and it said I wasn't able to create it, because it conflicts with existing call config or something along those lines. Basically that the DN was already in use. Very strange, I had just outed the only phone that was using it.
4 -> Create a new TN with the same config on 4 0 8 1, except no numbers. Print it out, and verify that there are no numbers configured (acd, scr, etc - nothing).
5 -> Print DNB 5551234, and it shows up as assigned to 4 0 8 1 on Key 3. Print the TN again, no numbers assigned (triple checked).
6 -> Out the TN again, print DNB 5551234, does not exist. Create the TN again (with no numbers), print DNB 5551234, shows up as key 3 on 4 0 8 1 (though it's definitely NOT configured there).

Tearing my hair out (if I had any) with this one. Where could this number be sticking around? How can I remove it so I can reprogram the number on this set?

Cheers

 

[captnamo]

Stab in the dark here. What happens if you program an SCR on key 3 with a different DN. Save it. Then go in and NUL key 3. See if that makes it go away?

 

[gwmyers]

Just a thought
What if you did a LD 11 CHG on 4 0 8 1 and NUL on Key 3

 

[apridham]

Unfortunately tried most of these already (figured maybe some memory had an old value that just didn't get removed when I outed the TN?). Tried them again, still no luck.

DN 5556789 <--- this is what's currently configured on key 03
TYPE SL1
TN 004 0 10 09 V KEY 03 H MARP DES ADMIN 28 AUG 2013
(3903)

DN 5551234 <---- This is the DN that seems to be stuck
TYPE SL1
TN 004 0 10 09 V KEY 03 H MARP DES ADMIN 28 AUG 2013
(3903)

They're both showing up on Key 03 of the same TN, but only the top one is configured. If I NUL key 3, and print 5551234, it still shows up on Key 03 of the set :/

 

[trvlr1]

Maybe it's time to poke it in the eye off hours to see if that clears any memory issues.

 

[Firebird Scrambler]

Check that the DN isn't stuck in the CPND. I had a case like yours a few times and there are two ways of clearing it.
The quickest way is probably to reboot the switch. Of course this isn't a good idea for a call centre!.

The other way is a little more tricky, but you need to have knowledge of "pdt" corruption and clear it that way. I've done both methods to resolve the problem.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.