> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Krzeminski, Damian (BL60:9D30)
> Sent: Tuesday, November 25, 2008 2:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [sipX-dev] Is XECS-415 really fixed?
> 
> Robert Joly wrote:
> >> Thanks - I'll check in as soon as I see your check-in. And 
> maybe we 
> >> can finally test it :-) D.
> > 
> > Committed in R14088.
> 
> 
> http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14091
> http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14092
> 
> userlocation is now replicated
> fallbackrules.xml adheres to a new format with separate 
> trasform lists for each location
> 
> Add couple of user groups, assign gateways to locations and 
> check if this is what you had in mind.
> D.

Damian, I finally found some time to look up the work you had done.
Although I haven't tested the functionality yet, I have a couple of
comments on the GUI itself:

1- Users do not have a 'Location' setting.
2- The choices that appear in the 'Location' pull-down list of gateways
are the configured groups, not locations.  I thought we had agreed that
although they are implemented similarly, groups and locations would be
distinct concepts at the user level.
3- The 'Location' pull-down list of gateways does not allow multiple
selections.  We need to be able to specify that a gateway serves several
locations.
4- Dialplan rules are missing a checkbox to indicate whether the rule is
subject to location-based routing or not.
5- For usability, the Gateway list appearing in the dialplan rule page
should have two extra columns; one enumerating the location(s) of the
gateway and one to indicate whether or not the gateway is shared.



_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to