I don't know if you can prefill SIP passwords with LDAP (recall reading something about that somewhere along the way).
Worst case though, export your users on the 3.10.3 system and then import them on the 3.11 box. The other stuff should work. Mike From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt White Sent: Wednesday, December 10, 2008 10:43 AM To: [EMAIL PROTECTED] Subject: Re: [sipX-dev] Replicating 3.11 to 3.10.3 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 >>> Kevin Thorley <[EMAIL PROTECTED]> 12/10/08 9:36 AM >>> On Wed, 2008-12-10 at 00:19 -0500, Matt White wrote: > I'm getting ready to start a new 3.10.3 deployment using Aastra > phones. > > I'd love to use the configuration server in 3.11.8 builds to deploy > the Aastra phone configs. But I really don't want to use the dev > builds in production. > > Is there a why I can use the 3.11.8 server as the configuration server > but have it register to the 3.10.3 server. I'd have to replicate > users between the two systems I think. > > -Matt I haven't tried this before, but I don't see why you can't run the 3.11.x server elsewhere on your network to generate all the phone configs, then just manually copy them to the 3.10.3 sipXconfig phone dir. Its not quite as easy as what you're suggesting, but I think it gets the job done. The problem with running a 3.11.8 sipXconfig with 3.10.3 sipx is that we've changed a lot of things about how sipXconfig relplicates configurations (for sipx services) and starts and stops processes... I doubt it would actually work. Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
