JIRA is a poor place to have a conversation, so I am bringing this here: Robert writes: http://track.sipfoundry.org/browse/XX-7170?focusedCommentId=45877
"I think that there is one sipXconfig issue that remains. Here is the scenario: If I create a SIP user called 'X' and assign it IM ID 'Y' and then I try to create a new SIP user called 'Y', sipXconfig will refuse that on the grounds that the default IM ID it would assign to SIP user 'Y' would collide with the IM ID of SIP user 'X'. In general, it should be possible to add a new SIP user in sipXconfig even if its SIP user ID happens to match the IM ID of another SIP user. SipXconfig could be smarter in its default IM ID generation to avoid such collision (e.g. append a '_2')." I don't think it's true. I think sipXconfig refuses to create 'Y' because of the SIP alias conflict. This is what I was warning about here: http://track.sipfoundry.org/browse/XX-6447?focusedCommentId=42311 "If we use IM id as an alias that would mean that it is restricted in similar way that SIP user parts are restricted. It would also mean that ID needs to be unique not only in IM name space but in the entire SIP id namespace (which includes all the extensions, aliases, names of conferences, hungroups etc.)" I still don't think we can have it both ways and - regardless of an 'alias issue' - I think that generating default IM IDs that would work around naming conflict is a *bad* idea. Opinions? Patches? 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 sipXecs IP PBX -- http://www.sipfoundry.org/
