What I had to do was create branches for each location that has a gateway, assign the gateways to the proper branches, then assign each group to a branch. For universal "shared" gateways no configuration is necessary. It's not that much work, probably only 15 minutes worth for me during the upgrade process but if someone that has a lot of location based routes then this process could take an hour or more to accomplish. Perhaps in 4.2.1 an upgrade option could be present to allow groups that gateways are assigned to, to be converted or copied to branches so these location based rules won't be completely lost during the upgrade. It seems like a one time ordeal, and it also seems like a lot of work to "fix it", maybe the official stance should be to "be prepared" for it, and be ready to manually put some information in?
Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 4/26/2010 3:33 PM, Scott Lawrence wrote: > On Mon, 2010-04-26 at 15:08 -0500, Josh Patten wrote: > >> Upon performing an upgrade in my test environment from 4.0.4 to 4.2.0 I >> noticed something that might make life difficult for administrators of >> large, dispersed systems that have many location based dialing rules: >> The "groups" that were used to route calls before did not get converted >> to "branches" essentially making a lot of things, such as location based >> 911 dialing, break after the upgrade requiring a lot of manual >> intervention and configuration of every user. Was this the intention or >> did I miss something important? >> > It was not the intention, but may not be completely avoidable. > > Ideally, we would have been able to recognize that a group was being > used in this way, but since groups are general concepts, that usage > could also have been mixed in with many other settings. Recognizing > which were being used for routing might be hard. > > We should probably take another look at this. > > Do you have some notes on what you had to do that we could use to make > up some upgrade documentation, Josh? > > _______________________________________________ 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/
