Matt, you probably don't even have to copy the files over to the other box... just set the DHCP option for TFTP server to point to the 3.11 box.
Mike From: [email protected] [mailto:[email protected]] On Behalf Of Matt White Sent: Saturday, December 13, 2008 7:46 AM To: [email protected] Cc: [email protected] Subject: Re: [sipX-dev] Replicating 3.11 to 3.10.3 Your idea worked great, I moved the files from 3.11 to 3.10 and provistioning seems to be working well no errors. I'm having an issue with BLF and MWI not working at all but I don't think it's related. I had them working under 3.10.2 so I'll be doing some testing to see if it's the recent 3.10.3 we just installed. -M >>> Andrei Cristian Niculae 12/10/08 12:08 PM >>> Matt White wrote: We will be deploying about 100 phones. The though of hand configuring each phone and feature is not nice. Here is what I'm thinking. I'm gonna setup both systems use LDAP to pull over the users and prefill thier extensions. So now both system have the exact same users. I haven't tried it yet, but i should be able to even fill in the SIP password from ldap right? So then I will configure phone using 3.11 and use the TFTP server on it to serve the phones. But then I should be able to play a simple DNS trick. The phone will get the config to register with sipx.company.com but that DNS will point to 3.10. Think that will work? Can anyone think of somthing that could cause a problem here, not sure how much of the other pieces will be affected like paging config. Thanks, Matt What you could do is try to plug-in the Aastra plug-in in the 3.10 deployment (I don't guaranty that this will work, but it's worth a shot). Take the aastra-phones.jar (from 3.11) and put it in the same dir as sipxconfig.jar (the folder changed from 3.10 to 3.11 and I can't remember it exactly), and then take the aastra folder from http://sipxecs.sipfoundry.org/ViewVC/sipXecs/main/sipXconfig/plugins/aas tra/etc/ and put them in /etc/sipxpbx/ (see /etc/sipxpbx/lg-nortel) and restart the application. If you get an error, just delete the above files. Even better, if that doesn't work, you could try to port the Aastra plug-in in 3.10. That shouldn't be too hard ... I don't think that there are many changes at the plug-in level. And I'm sure Damian will take the patches :) Regards, Andrei
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
