Reprogramming IP Phones not Registering with Switch

[CollegeTech]

Since the 6.0 upgrade whenever an IP phone is outed and reprogrammed the user has to manually hit the reset button (first soft key) for the phone to come up. With the previous Switch Rls the phone would program like a regular digital set where it comes right up. Easy Changes work fine.

My vendor has been working on this for 6 months and can't figure it out.

I get the following error on the phone-
InvalidTN: 100.00.01.12
Reason: Unequipped

Error in the Switch-
SRPT062 Request to register TN rejected. UNEQUIPPED tn = 100-00-01-12 hwid = 180
016caf48
65d6602

I've tried this on i2002, i2004 and 1140E all same error. Firmware updated on the sets and the software we use to bill and program has been ruled out.

Anyone have the same issue?

 

[Wane47]

I think this is what's going on. The TN was not programed when you plugged the phone in. The phone tried to come up based on the retry counter, which usually defaults to 5. You programed the tn after the retry timer expired, causing the user to maually intervene to force the registration process to begin again.

 

[Tman45]

If you are changing the phone TN you have to physically be at the phone to enter the new TN (unless you are pushing the config via TFTP) from what I understand and have dealt with for 5+ years.

Maybe I'm wrong, but yes if you are just changing the phone programming via the PBX that does NOT change the actual TN config on the phone. I would recommend unplugging it for a bit too. These phones have a tendancy to 'hold on' to their initial config.

 

[CollegeTech]

I am simply outing the phone and reprogramming it so the Autodials will clear our for the next user. No configuration change or anything like that. I've upped the retry count to 199 just to see and it won't come up and this is since the upgrade. (which will soon be to 7.5 [*rolls eyes])

It hits the Node screen, then right to to Invalid TN. Now it used to go to Forwarding Terminal Manager and wait until the phone was done rebuilding and come right up.

It's just frustrating because I've got the data people saying nothing changed on the network, the PBX guys saying it's not the upgrade or the third party software used for billing and building phones saying it's not them. I will end up figuring it out if determined enough but I've been doing this for 10 years and seems it's always the phone guys who get stuck in the end.

Thanks all anyway. I did build a phone directly in the switch, nothing.

 

[Johnthephoneguy]

I would try this:

Unplug the phone

Out the phone

rebuild the phone

plug the phone back in

See what happens then

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[CollegeTech]

Yea, I don't want people unplugging phones. We know what happens when that happens, phones get moved all over the place and I am not yet equipped to assign DNs to data ports.

I just want to know what could have changed so the phone can see when the TN is programmed and grab the configuration opposed to just opting out when it's not there. I am narrowing down on something about the Terminal Manager because I am noticing some different things going on there. Sometimes waiting for that but timing out right before the phone finishes programming and sometimes not waiting at all. Very inconsistent.

Can't wait for the next upgrade so I can chase more problems.

I definitely appreciate the help people are willing go give.