Paul Mossman wrote:
Laurentiu wrote:
Revision 17209 introduced a new IM validation that checks IM
IDs to be unique
(http://code.sipfoundry.org/changelog/sipXecs/?cs=17209).
More than that, looking in ImAccount.getImId() method ...
* If configured IM id has the highest priority. If not
username or an alias is used in the
* following order: (1) non-numeric username, (2)
non-numeric alias,
(3) username.
So the problem occurs when we are running on a revision <
17209 (and there are multiple users configured with the same
IM ID for example).
Updating to rev 17209 or greater (containing IM validation)
will result in error messages displayed every time the user
is saved/updated.
An enhancement would be to include in error message users
with same IM IDs, so admin will have the chance to fix this.
Any other thoughts?
This won't happen on upgrades from released versions, so I don't think
it warrants a fix.
On development systems, you can just correct the configuration error
right?
-Paul
[email protected]
Yes, I think you are right since both features (IM panel and IM ID
validation) were introduced in 4.1
Laurentiu
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
