Yup, I double checked that > -----Original Message----- > From: Keith Gearty [mailto:[email protected]] > Sent: Wednesday, June 24, 2009 9:14 PM > To: Boy Aidil Sjam > Cc: [email protected] > Subject: Re: [sipx-users] Linksys SPA941 IP Phone - Provisioning Issues > > When you manually added the phone, did you enter the correct case for > the MAC address? > > Keith. > > > Boy Aidil Sjam wrote: > > >Oops, I mean, I found spa000E08D09436.cfg at the tftproot folder. > Sorry for the typo > > > > > >------------------------- > >Original Message: > >From: Keith Gearty <[email protected]> > >To: Boy Aidil Sjam <[email protected]> > >Cc: [email protected] > >Date: Wednesday, 24 June 2009 19:25 > >Subject: Re: [sipx-users] Linksys SPA941 IP Phone - Provisioning > Issues > >Was that a typo in your email, or does the file actually have the > wrong > >number of zeros after "spa" ? > > > >Keith. > > > >Boy Aidil Sjam wrote: > > > > > > > >>Hi All, > >> > >>I think there are some issues with Linksys SPA IP Phone with sipXecs > >>ver.4.0. > >> > >>I used Linksys SPA941 > >> > >>First, when I used Discover Devices, the IP Phone was discovered with > >>the correct mac address, IP address, and Vendor, but there?s no > single > >>model I can choose. > >> > >>Second, I manually add the phone from the phone menu, I assign the > >>line and used all the default value. After I reset the phone to > >>factory default, set profile rule to /spa$MA.cfg, then reboot the > >>phone, the phone can not registered. Try to restart the sipX server, > >>reconfigure the phone on server, and reconfigure the phone but still > >>the same. > >> > >>Then I ran wireshark to capture the communication between the phone > to > >>the server. I found out that the Linksys request file: > >>/spa000e08d09436.cfg and cannot find the file on the server. > >> > >>I checked on the tftp server root directory on the server, I found > >>there?s a spa00E08D09436.cfg (all the MAC address characters in the > >>capital). After I rename the file, now the Linksys able to load the > >>configuration. > >> > >>This problem never found on sipXecs ver.3.10. 3 > >> > >>Regards, > >> > >>B. Aidil > >> > >> > >> > >> > >> > > > > > > > >DISCLAIMER: > >Information in this message is confidential and may be legally > privileged. It is intended solely for the addressees. Access to this > message by anyone else is unauthorised. If you are not the intended > recipient, any disclosure, copying, or distribution of the message, or > any action or omission taken by you in reliance on it, is prohibited > and may be unlawful. Please immediately contact the sender if you have > received this message in error. > > > > > >---------------------------------------------------------------------- > -- > > > > > >No virus found in this incoming message. > >Checked by AVG - www.avg.com > >Version: 8.5.375 / Virus Database: 270.12.90/2198 - Release Date: > 06/23/09 17:54:00 > > > > > > > Checked by AVG - www.avg.com > Version: 8.5.374 / Virus Database: 270.12.90/2200 - Release Date: > 06/24/09 12:49:00
DISCLAIMER: Information in this message is confidential and may be legally privileged. It is intended solely for the addressees. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
