[asterisk-users] OT: Aastra 57i configuration via TFTP problem

[Roi Stork]

Here's what I did:

1) Reduced the local config to just network settings.
2) <mac>.cfg contains network + sip settings.
3) Restarted the phone.

The result was only some sip settings like auth name, user name,
password get updated.
Fields such as proxy ip and registrar ip didn't get updated. I
expected the whole sip settings were read from the cfg file and set,
but it wasn't the case.

Same problem happened to your setup?

On Nov 7, 2007 6:33 PM, Michelle Dupuis <support at ocg.ca> wrote:
> Use the web interface of the phone to retrieve the config file that you
> uploaded.  Is it only partially there?
>
> > -----Original Message-----
> > From: asterisk-users-bounces at lists.digium.com
> > [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of
> > Roi Stork
> > Sent: Wednesday, November 07, 2007 9:27 PM
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: Re: [asterisk-users] OT: Aastra 57i configuration
> > via TFTP problem
> >
>
> > Thanks! We checked the TFTP server and there seems to be no problem.
> > It's up and listening, and looking at the tcpdump and the log
> > there really was traffic between the phone and the server. We
> > also successfully downloaded files using another TFTP client.
> >
> > On Nov 7, 2007 5:33 AM, Jared Smith <jsmith at digium.com> wrote:
> > > On Wed, 2007-11-07 at 00:08 -0800, Roi Stork wrote:
> > > > 1) No DHCP, so I manually set the network settings via phone UI.
> > > > 2) The files aastra.cfg and <mac address>.cfg are in the
> > TFTP root folder.
> > > > 3) Restarted the phone.
> > >
> > > Here's what I'd do to troubleshoot the problem:
> > >
> > > 1) First make sure that your TFTP server is actually listening:
> > >
> > > [root at hockey ~]# netstat --listen -npu | grep :69
> > > udp        0      0 0.0.0.0:69                0.0.0.0:*
> > > 2334/xinetd
> > >
> > > 2) Next, I'd use tcpdump to make sure you're actually seeing TFTP
> > > traffic from the phone:
> > >
> > > [root at hockey ~]# tcpdump -vv port 69
> > > tcpdump: listening on eth0, link-type EN10MB (Ethernet),
> > capture size
> > > 96 bytes 08:28:56.622180 IP (tos 0x0, ttl 64, id 0, offset 0, flags
> > > [DF], proto UDP (17), length 48) 192.168.0.100.34771 >
> > > 192.168.0.50.tftp: [udp sum ok]  20 RRQ "test.txt" netascii
> > >
> > > 1 packets captured
> > > 1 packets received by filter
> > > 0 packets dropped by kernel
> > >
> > > 3) As an additional step, you can turn up the verbosity of the tftp
> > > server, and look for it's messages in /var/log/messages.
> > In my case,
> > > I simply add a "-v" to the server_args line in my
> > /etc/xinetd.d/tftp
> > > file as show below and restart xinetd.
> > >
> > >         server_args             = -s /tftpboot -v
> > >
> > > The information shows up in /var/log/messages:
> > >
> > > Nov  7 08:28:56 hockey in.tftpd[27601]: RRQ from 192.168.0.100
> > > filename test.txt
> > >
> > > Let me know if that helps, or if I need to go into more detail.
> > >
> > >
> > > --
> > > Jared Smith
> > > Community Relations Manager
> > > Digium, Inc.
> > >
> > >
> > >
> > > _______________________________________________
> > > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> > >
> > > asterisk-users mailing list
> > > To UNSUBSCRIBE or update options visit:
> > >    http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> >
> > _______________________________________________
> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
> >
> > asterisk-users mailing list
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>