Damian Krzeminski wrote: > Robert Joly wrote: >>> I am in the middle of reviewing (well really rewriting in >>> this case) a patch for sipXconfig side of location specific >>> gateways. I got to the part when we generate new >>> fallbackrules.xml, but I do not think that Scott's patch that >>> adds falbackrules.xsd.in is checked it. >>> >>> See here: >>> http://article.gmane.org/gmane.comp.voip.sipx.devel/13390 >>> >>> What am I missing? >>> If it's just a question of a missing .xsd I can commit >>> Scott's patch... >>> D. >> The patch I committed for XECS-415 is all the redirector logic that will >> come into play once the location-enhanced fallbackrules get generated >> but haven't committed any xsd files. The new xsd file cannot be >> committed before sipXconfig starts generating fallbackrules that comply >> with it as this would cause the schema checker to fail, causing start-up >> issues. I suggest that you commit Scott's new xsd file at the same time >> as you commit your sipXconfig changes. > > Perfect. That's what I'll do. Thank you. > Damian >
I think that the basic support for location based routing in sipXconfig is ready: http://track.sipfoundry.org/secure/attachment/16763/0001-XCF-2407-add-basic-support-for-site-based-routing.patch I cannot check it in because whenever sipXconfig attempts to replicate userlocation dataset supervisor complains with: "2008-11-24T22:41:52.907685Z":1226:SUPERVISOR:CRIT:doto.pingtel.com:HttpConnection-71:B31C3B90:Supervisor:"ImdbRpcReplaceTable::clearTable invalid table name 'userlocation'" I do not think that userlocation database is currently supported by sipxsupervisor XML/RPC. I do not see any references to userlocation in sipXsupervisor/src/ImdbRpc.cpp BTW: which component should claim dependency on it? sipXproxy or sipXregistrar? D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
