Some of the Aastra's are pretty picky, and will give up if they don't find some extra files present, I believe one of those magic files is "aastra.tuz". It doesn't need to contain anything.
If you look at your FTP logs, you should see what else it's attempting to retrieve. You can also accept syslog from the phone by adding a '-r' to /etc/default/syslogd, setting the syslog server to your system in the phone under 'troubleshooting', and cranking the debugging levels to 65535 for anything related to provisioning. -spd On Mon, Jun 29, 2009 at 7:55 PM, Terry D. Cudney <[email protected]> wrote: > > Hi all, > > Having a problem gettin my Aastra 480ict to retrieve its configs from any > kind of server, tftp, ftp or http. > > Prefer ftp, and have ftp autoconfig working with my Aastra 51i. > > The two phones both have the latest firmware from Aastra although they have > slightly different functionality, i.e. the 51i has a "ftp path" option in > the web ui, while the 480ict does not. Otherwise they are configured the same. > > With a user login on my Debian server dedicated to handling the ftp-configs > for these phones, I put eh <mac>.cfg and aastra.cfg files int eh root of the > ftp-user account and the 51i's <mac>.cfg and aastra.cfg in a subdirectory > called "configs/". With no "path" parameter for the 480ict I figured they > should go in the root of the user account. > > Here are the "/var/log/syslog" lines where the two phones fail/succeed to > retrieve their configs (ip numbers have been changed, but they are both on > the same subnet with the server): > > #portion of /var/log/syslog where Aastra 480ict fails to retrieve > configuration > Jun 29 18:23:15 a1 in.ftpd[16963]: connect from 192.168.9.2 (192.168.9.2) > Jun 29 18:23:15 a1 in.ftpd[16964]: connect from 192.168.9.2 (192.168.9.2) > Jun 29 18:23:15 a1 ftpd[16964]: mmap(0): Invalid argument > Jun 29 18:23:15 a1 in.ftpd[16965]: connect from 192.168.9.2 (192.168.9.2) > Jun 29 18:23:15 a1 in.ftpd[16966]: connect from 192.168.9.2 (192.168.9.2) > > #portion of log where Aastra 51i succeeds in retrieving configuration > Jun 29 18:30:13 a1 in.ftpd[17083]: connect from 192.168.9.6 (192.168.9.6) > Jun 29 18:30:13 a1 ftpd[17083]: mmap(0): Invalid argument > > they both get the "invalid argument" error, but the 51i succeeds while the > 480ict fails. The 51i does not try to connect after the "mmap(0): Invalid > argument" message, as the 480ict does. > > I have tried tftp and http as well with the 480ict and nothing works so > far. > > Any pointers/suggestions will be much appreciated. > > > --terry > > -- > Name: Terry D. Cudney > Phone: (705) 812-4949 > SIP: [email protected] > E-mail: [email protected] > > Please avoid sending me Word or PowerPoint attachments. > See http://www.gnu.org/philosophy/no-word-attachments.html > > Having a smoking section in a restaurant is like... > having a peeing sectionin a swimming pool. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
