On Thu, 2010-02-11 at 20:06 +0530, Chitralekha wrote: > Robert Joly wrote: > > > Hi All, > > > > > > This query is regarding "Joining a Conference IM Chat with > > > the password set" from the Pidgin Client. > > > > > > I have SCS Audio conference named "Qantom" with the > > > Extension as 1111 and Password set to 999 added to SipX. > > > Assigned IM user 400 as the owner of the > > > conference.Registered a pidgin client to user 400. > > > Now I try to access conference "Qantom" from Pidgin client > > > TUI>>Tools>>Room List>>Get list>>Find Rooms>> Qantom.Double > > > click on the displayed conference "qantom" to establish a IM > > > conference chat. > > > > > > Now after double clicking on "qantom", > > > > > > An error message "401:Not Authorized" is > > > displayed to the user. > > > > > > Please refer the below screen shot: > > > > > > <imap://chitralekha%[email protected]:143/fetch%3EUID%3E%5Es > > > > > ipx-dev%20Digest%3E9587?part=1.1.1.2&filename=moz-> screenshot-65.jpg> > > > > > Kindly suggest if this is an expected behavior or an Issue? > > > If this is an expected behavior I will raise an improvement > > > issue to provide an help text mentioning for the same. > > > > > > NOTE: > > > -------- > > > Conference chat is successfully established if the audio > > > conference "Qantom" DO NOT have password set. > > > > > > > That is expected behavior. Arguably, pidgin could do a better UI job > > and prompt for a password but it is what it is. To enter multiuser > > chatrooms protected by a PIN, you need to add the chat as a buddy and > > set the password property to match the PIN. If you do that, you sohould > > be able to enter the room. > > > Thanks Bob. > The scenario which explained works absolutely fine. > I think there should be help text which mention or indicates the > same.Or there should be a help text in the sipx config ui which could > give the information to users that "Avoid assigning Password while > creating a Conference IM Chat in the Sipx". > I will rasie an Improvement Issue for the same.
I don't think we need any issue for this - it is what it is, and it behaves correctly. Pidgin does a poor job displaying an authentication failure - not much we can do about that. _______________________________________________ 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/
