CUCM 8.6 - Registration rejected

[Ven Taylor]

Hey folks.  I had a weird one this week.  I had three new wireless phones get the same error.  Registration rejected.

During troubleshooting, I stopped and restarted the TFTP service to no avail.

Finally, I took a guess and turned off auto registration on our Subscriber and Publisher, and then turned it back on.

The phones all registered.

My question is this... What the heck??  Why did that fix it?

Thanks!

Ven

[acampbell]

Ven,

Is it possible that you had run out of DNs on your auto reg.

Are you using a different range of Dns on you new auto reg

Regards

Alex

[Ven Taylor]

You know Alex, I had thought about that.

I went through the list of unregistered auto-reg phones and deleted them in device/phone.

I had 1000 to 1500, but had maybe 50 unregistered auto-reg phones.

I assumed that would recycle the numbers.  Was I right?

Is there a better way to do this?

Ven

[acampbell · Accepted solution]

Ven,

As far as I know the DNs in auto reg do not recycle.

Lets say you just had

1001 - 1029 set

You plug in the phones say 40 of them

The 1st 29 will get Auto-reg assigned.

You go to CUCM and move the phone to new DNs say 2XXX range.

The remaining phones will still not register till you rest the AUTO-REG

I dont know if your set up keeps the auto-reg number or do you change the DNs once registered.

Regards

Alex

[Jaime Valencia · Accepted solution]

Alex is correct on this, your assumption that they recicle is wrong.

When it comes to auto registration CUCM only knows this 3 things

What DN to start from, on what DN to stop and a field which has the next-DN to assign for auto-registration until it's equial to the last DN from the pool you created.

CUCM doesn't go back and check if you're no longer using the DNs or if you have deleted the DNs.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[Ven Taylor]

Wow... That is definitely what happened then.

So is there a proper way to "reset" the range besides re-defining it?

Being a hospital, we constantly have our phones swapped out because of user abuse.

Our process is that we let the phone auto-register, then configure it like the "old" phone.

OR

Should I just change the current device to match the mac address of the "new" phone, so aut-registration never happens?

Ven

[Jaime Valencia]

You would need to disable and re-enable auto-reg to reset the next-DN value in the DB, or change the range.

But if you use the same range and forget to change a phone or do not delete the DNs from unassigned you can have problems.

If it's the same phone model that you just keep changing wouldn't it be easier to bulk export all details from the phone and then have the file at hand just changing the MAC address when you need to swap the phone?

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk