[cisco-voip] Phone Registration Rejected

Fri Oct 6 17:11:58 EDT 2006

Thank you both for getting to the granular detail.  I dont' know why my auto
registration isn't working but I am going to try disabling it and
re-enabling it.

On 10/6/06, Wes Sisk <wsisk at cisco.com> wrote:
>
>  TFTP stores the file in memory, not on physical disk.
>
> if you want to see the file, simply use a TFTP client and request the file
> from the TFTP server.
>
> windows 2000 has a builtin TFTP client.  from the command prompt:
>
> C:\cdets\bin>tftp  /?
>
> Transfers files to and from a remote computer running the TFTP service.
>
> TFTP [-i] host [GET | PUT] source [destination]
>
>   -i              Specifies binary image transfer mode (also called
>                   octet). In binary image mode the file is moved
>                   literally, byte by byte. Use this mode when
>                   transferring binary files.
>   host            Specifies the local or remote host.
>   GET             Transfers the file destination on the remote host to
>                   the file source on the local host.
>   PUT             Transfers the file source on the local host to
>                   the file destination on the remote host.
>   source          Specifies the file to transfer.
>   destination     Specifies where to transfer the file.
>
> /Wes
>
> Candese Perez wrote:
>
> Ok, can you please help me understand how the phone sees the file if I
> can't see it on the disk?  I don't quite understand the caching feature.
> Also where do you access the TFTP service parameters, the Windows MMC
> services snap-in or in CM somewhere?
>
> thanks
>
> On 10/6/06, Ryan Ratliff <rratliff at cisco.com> wrote:
> >
> > The Cisco TFTP server caches config files in memory to reduce disk
> > access and speed up tftp requests.  Unless you go into advanced TFTP
> > service parameters and disable caching you will never see the config
> > files on the hard disk.
> >
> > -Ryan
> >
> > On Oct 6, 2006, at 1:54 PM, Candese Perez wrote:
> >
> > ok, i do see a read request for an xmldefault.cnf.xml from the phone
> > to the cm server but i don't see that file in my tftp directory. Any
> > ideas as to why that is?
> >
> >
> >
> > On 10/6/06, Wes Sisk <wsisk at cisco.com> wrote:
> > default.cnf was only used by old phone loads (in CM3.1 we changed
> > to .cnf.xml files).  that file will probably not be built unless you
> > change the TFTP service parameter from 'build selective' to 'build all'.
> >
> > only VERY old phone loads should need that file.
> >
> > /Wes
> >
> > Candese Perez wrote:
> > > Manually adding the phone works.  (Thank you)
> > > Any ideas on why I don't have a default.cnf file in my tftp
> > > directory if auto-registration is enabled?
> > >
> > > On 10/6/06, Ryan Ratliff <rratliff at cisco.com > wrote: Under System-
> > > >CallManager there is a check box to disable auto-
> > > registration on a server.
> > >
> > > There will not be a config file on the TFTP server unless the phone
> > > is in the database.   I'd recommend you add the phone manually and it
> > > will then register.
> > >
> > > -Ryan
> > >
> > > On Oct 6, 2006, at 12:48 PM, Candese Perez wrote:
> > >
> > > I don't believe the phone is in the database because i can't find it
> > > when searching by it's MAC address.  When I look at my CM server
> > > configuration I don't see that auto-registration is disabled.  Is
> > > there some place else I should be looking to check for auto-
> > > registration?
> > >
> > >
> > >
> > > On 10/6/06, Ryan Ratliff < rratliff at cisco.com> wrote: Is the phone in
> > > the database?  If not and autoregistration is
> > > disabled then the config file won't exist and it won't register.
> > >
> > > If the phone is in the database try bouncing TFTP and then doing a
> > > TFTP GET on the macaddr.cnf.xml from a windows cmd prompt to see if
> > > you can get the file.
> > >
> > > -Ryan
> > >
> > > On Oct 6, 2006, at 12:26 PM, Candese Perez wrote:
> > >
> > > When I do a factory reset it looks for a file SEP+MAC address and
> > > then says file not found and returns to registration rejected.  In my
> > > trace file I can see  several TFTP error codes referencing the same
> > > message that the tftp server doesn't have the SEP+MAC.cnf.xml file
> > > nor does it have XMLDefault.cnf.xml.
> > >
> > > On 10/6/06, Brian Henry <Brian.Henry at apptis.com > wrote:
> > > I assume that you are not running in secure mode.
> > >
> > > 1.  Did you do a factory reset of the phone?
> > >
> > > Have you looked at the debugs on the phone web page to see what error
> > > code it is giving you? or you can attach the cable in the docs to the
> > > aux port to look at the phones boot up process and a more detailed
> > > view.
> > >
> > > Brian
> > >
> > > From: cisco-voip-bounces at puck.nether.net on behalf of Candese Perez
> > > Sent: Fri 10/6/2006 11:58 AM
> > > To: cisco-voip at puck.nether.net
> > > Subject: [cisco-voip] Phone Registration Rejected
> > >
> > > I have a 7960 that will nto register with my CM 4.0 server, and I
> > > believe it is because the .cnf file is out of date or has changed as
> > > this phone has been in storage for several months.
> > >
> > > How can i get the phone to use the new file on CM if it won't
> > > register in CM.  Is there a way to push the new file to the phone?
> > >
> > > Candese
> > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> > >
> > >
> > > _______________________________________________
> > > cisco-voip mailing list
> > > cisco-voip at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061006/b18c824e/attachment.html 