Matt White wrote: > Is it possible to mix the two version a production environment? > > Specifically, we are looking to deploy the ConfigServer from 3.11 > branch. We really need to be able to automatically deploy our Aastra > phones. ie Create a user and assign it to phone and have the conf files > autocreated or updated when we modify the line and phone features. > > So, we would keep the 3.10 for the main media server. Basically, 3.10 > will do all the sip registration and routing but we would use 3.11 to > generate the phone profiles. > > We went with the Aastra phones back in August because at the time 4.0 > was scheduled for late 2008...but now it appears to be push backed about > 6 months. And managing the phones by hand is a real pain. > > Your thoughts are appreciated. >
That would not work: way too many things have changed. You could try running 3.11 separately just to generate the aastra phone profiles (export users to 3.11 and use it to manage only aastra phones). You can also try creating your own version by forking 3.10 and merging the Aastra plug-in. What has some remote chances of working is taking just the aastra plug-in (aastra-phones.jar) and dropping it into 3.10. I would not try it in the production environment. There are chances it'll stop sipXconfig from starting at all, damage your DB beyond repair, or worse. If you do not know what to do to get back to working configuration after something like that - do not try it. Damian _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
