Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

auto registration does not work anymore

Hello,

Via auto-registration,i'm not able anymore to let phones register.

I have activated the tftp trace while connecting the phone to the network and got following traces:

01/17/2006 15:53:05.694 TFTP|-->CTftpConnect::ThreadPoolProxyRun[4788:193.191.232.242:52817] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.709 TFTP|-->CTftpConnect::tftp[4788:193.191.232.242:52817] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.709 TFTP| CTftpConnect::tftp[4788:193.191.232.242:52817] SEP0011BBAE2CF3.cnf.xml not found in constant and bin cache|<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.709 TFTP| CTftpConnect::tftp[4788:193.191.232.242:52817] SEP0011BBAE2CF3.cnf.xml not found in config cache|<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.709 TFTP|-->CTftpConnect::GetName[4788:193.191.232.242:52817] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.709 TFTP| CTftpConnect::GetName[4788:193.191.232.242:52817] Path is [C:\Program

AND

01/17/2006 15:53:05.725 TFTP|-->CTFTPConnect::GetRequest(), socket = 0000059C |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP|-->CTftpConnect::ThreadPoolProxyRun[2816:193.191.232.242:52818] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP|-->CTftpConnect::tftp[2816:193.191.232.242:52818] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP| CTftpConnect::tftp[2816:193.191.232.242:52818] SIP0011BBAE2CF3.cnf not found in constant and bin cache|<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP| CTftpConnect::tftp[2816:193.191.232.242:52818] SIP0011BBAE2CF3.cnf not found in config cache|<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP|-->CTftpConnect::GetName[2816:193.191.232.242:52818] |<CLID::StandAloneCluster><NID::172.28.1.30>

01/17/2006 15:53:05.725 TFTP| CTftpConnect::GetName[2816:193.191.232.242:52818] Path is [C:\Program Files\Cisco\TFTPpath\SIP0011BBAE2CF3.cnf]|<CLID::StandAloneCluster><NID::172.28.1.30>

the "not found in constant and bin" message,is this an error?

Anyone who has an idea? We are talking about the ip phone with mac address 0011BBAE2CF3

Is there a file corrupt?

thanks,

Kurt

4 REPLIES
New Member

Re: auto registration does not work anymore

First idea comes in mind - do you have numbers available? In the CallManager settings you define the range of DNs available for a registration, as well as what partition they belong. After you got "the Auto-registration range", go to the list of you phones and see what was the last number in that range.

Good luck,

Mike

www.ciscoheadsetadapter.com

New Member

Re: auto registration does not work anymore

Hi Mike,

thanks for your feedback.

Range is ok,there are no DN's in use at the moment.

Also,there are enough ip addresses in the DHCP.

Firmware version of the phone is 7.1.1

Cheers,

Kurt

New Member

Re: auto registration does not work anymore

I know this doesn't actually help you in any way, but I thought I'd throw in that we're having the same issue with Auto-Reg not working. We've checked spare DN's etc and all looks okay. I was passed a bug ref number which supposedly covered this issue, but it didn't really gel with me. Basically it was supposed to be an issue with a failed DB Stored Procedure when an upgrade was done on CCM. We've found that Auto-Reg works some of the time, usually until the next reboot of the CM Servers.

I know another Cisco customer around here is having the same issue which is apparently still outstanding.

I'd be interested if you come across anything.

TIa

New Member

Re: auto registration does not work anymore

Hello,

My problem is solved.The solution was easy and stupid.

A collegue of mine had added an extra CCM in the cluster and had put that one as default "auto registration" CCM in the cluster.So i did disable the new one and enabled the "old" one but forgot to adapt in "callmanager group" the default server.

I suppose this will not be the same issue with you,Nathan. ;)

Anyway,thanks for your feedback.

Kind regards

Kurt

172
Views
0
Helpful
4
Replies
CreatePlease login to create content