sipXecs 4.6/bria password reset design bug & login screen wording

[Nicholas Drayer]

I'm not sure this is the right method of reporting issues - please tell me if I should be doing this differently.

I'm running sipXecs 4.6 with Bria 3 softphones. I believe there's a design bug in the feature for end-users to reset their password:

1. End user goes to the end-user portal and resets their password (My Information>Unified Messaging, the top 2 fields Password and Confirm Password);

2. End user logs in with Bria softphone, using the new password;

3. The SIP account logs in fine, the XMPP account does not.
The reason that the XMPP account doesn't work is that the .ini file (that the phone is provisioned with on login) still has the old password. A work-around is for the superadmin to create a new profile (Phones>Send Profiles button) for the user's softphone (after the end-user has changed their password). Subsequently the user's softphone needs to logout and back in again, and now both accounts work.
To resolve this, the system would have to generate new phone profiles for all the user's phones (Bria specifically) that have XMPP built in, after the user changes their password in the portal.

A second non-related issue which throws end-users into a tizzy is that the login screen to the portal asks for their PIN, when it actually needs their password (specifically, their XMPP password). Despite its heading, the user's Voice Mail PIN will not work. The heading of this field on the login screen ought to be "Password:".

Thanks!

Nicholas Drayer
Managing Director
Dyrand Systems
T. 604.408.4415 Ext. 319
www.dyrand.com

[Mircea Carasel]

On Thu, Nov 22, 2012 at 3:58 AM, Nicholas Drayer

I’m not sure this is the right method of reporting issues – please tell
me if I should be doing this differently.****
**

For opening bugs we use Jira : http://track.sipfoundry.org

**
I’m running sipXecs 4.6 with Bria 3 softphones. I believe there’s a design
bug in the feature for end-users to reset their password:****
**1. **End user goes to the end-user portal and resets their
password (My Information>Unified Messaging, the top 2 fields Password and
Confirm Password);****
**2. **End user logs in with Bria softphone, using the new password;
****
**3. **The SIP account logs in fine, the XMPP account does not.****
The reason that the XMPP account doesn’t work is that the .ini file (that
the phone is provisioned with on login) still has the old password. A
work-around is for the superadmin to create a new profile (Phones>Send
Profiles button) for the user’s softphone (after the end-user has changed
their password). Subsequently the user’s softphone needs to logout and back
in again, and now both accounts work.****
To resolve this, the system would have to generate new phone profiles for
all the user’s phones (Bria specifically) that have XMPP built in, after
the user changes their password in the portal.

Yes, so we have now the same password for user portal and XMPP (minimum 8
characters) and a voicemail PIN (minimum 4 characters) So during every
login in bria, we should make sure that we write the password in the ini
file - please open a ticket

****
** **
A second non-related issue which throws end-users into a tizzy is that the
login screen to the portal asks for their PIN, when it actually needs their
password (specifically, their XMPP password). Despite its heading, the
user’s Voice Mail PIN will not work. The heading of this field on the login
screen ought to be “Password:”.

I agree is confusing, in general when users talk about PIN they think at
voicemail pin, so yes, would be better to write there Password instead

Mircea

****
** **
Thanks!****
** **
Nicholas Drayer****
Managing Director****
Dyrand Systems****
T. 604.408.4415 Ext. 319****
www.dyrand.com****
** **
** **
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Michael Picher]

We also have a request in our internal tracker for automatically sending
bria profiles after password change...

This tracker item probably should have been in the open source tracker.

Mike

On Thu, Nov 22, 2012 at 3:58 AM, Nicholas Drayer <

I’m not sure this is the right method of reporting issues – please tell
me if I should be doing this differently.****
**

For opening bugs we use Jira : http://track.sipfoundry.org

**
I’m running sipXecs 4.6 with Bria 3 softphones. I believe there’s a
design bug in the feature for end-users to reset their password:****
**1. **End user goes to the end-user portal and resets their
password (My Information>Unified Messaging, the top 2 fields Password and
Confirm Password);****
**2. **End user logs in with Bria softphone, using the new
password;****
**3. **The SIP account logs in fine, the XMPP account does not.****
The reason that the XMPP account doesn’t work is that the .ini file (that
the phone is provisioned with on login) still has the old password. A
work-around is for the superadmin to create a new profile (Phones>Send
Profiles button) for the user’s softphone (after the end-user has changed
their password). Subsequently the user’s softphone needs to logout and back
in again, and now both accounts work.****
To resolve this, the system would have to generate new phone profiles
for all the user’s phones (Bria specifically) that have XMPP built in,
after the user changes their password in the portal.

Yes, so we have now the same password for user portal and XMPP (minimum 8
characters) and a voicemail PIN (minimum 4 characters) So during every
login in bria, we should make sure that we write the password in the ini
file - please open a ticket

****
** **
A second non-related issue which throws end-users into a tizzy is that
the login screen to the portal asks for their PIN, when it actually needs
their password (specifically, their XMPP password). Despite its heading,
the user’s Voice Mail PIN will not work. The heading of this field on the
login screen ought to be “Password:”.

I agree is confusing, in general when users talk about PIN they think at
voicemail pin, so yes, would be better to write there Password instead
Mircea

****
** **
Thanks!****
** **
Nicholas Drayer****
Managing Director****
Dyrand Systems****
T. 604.408.4415 Ext. 319****
www.dyrand.com****
** **
** **
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.

[Mircea Carasel]

Post by Michael Picher
We also have a request in our internal tracker for automatically sending
bria profiles after password change...
This tracker item probably should have been in the open source tracker.

Yes, this should have been in the open source tracker, but anyway, I think
we can use the internal one to address the problem
mircea

Post by Michael Picher
Mike

[Tony Graziano]

Could item be moved where folks could comment on it?

I've thought at first maybe the user could request a pull from the user
portal, but that didn't make sense since the UA does that already.

The only thing that makes sense is that the config gets auto pushed for
that phone type of a user change (password), then the user can logout/login
to force the config refresh. Perhaps an email message could be auto
generated.

Post by Mircea Carasel

Post by Michael Picher
We also have a request in our internal tracker for automatically sending
bria profiles after password change...
This tracker item probably should have been in the open source tracker.

Yes, this should have been in the open source tracker, but anyway, I think
we can use the internal one to address the problem
mircea

Post by Michael Picher
Mike

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Nicholas Drayer]

Thank you, I've entered them both. I've no idea how to solve programming issues, but I figure it's helpful to the developers for me to enter them!
Nicholas

From: sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Michael Picher
Sent: November-22-12 2:06 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] sipXecs 4.6/bria password reset design bug & login screen wording

We also have a request in our internal tracker for automatically sending bria profiles after password change...

This tracker item probably should have been in the open source tracker.

Mike

On Thu, Nov 22, 2012 at 4:10 AM, Mircea Carasel <***@ezuce.com<mailto:***@ezuce.com>> wrote:

On Thu, Nov 22, 2012 at 3:58 AM, Nicholas Drayer <***@dyrand.com<mailto:***@dyrand.com>> wrote:
I'm not sure this is the right method of reporting issues - please tell me if I should be doing this differently.

For opening bugs we use Jira : http://track.sipfoundry.org<http://track.sipfoundry.org/>
I'm running sipXecs 4.6 with Bria 3 softphones. I believe there's a design bug in the feature for end-users to reset their password:

1. End user goes to the end-user portal and resets their password (My Information>Unified Messaging, the top 2 fields Password and Confirm Password);

2. End user logs in with Bria softphone, using the new password;

3. The SIP account logs in fine, the XMPP account does not.
The reason that the XMPP account doesn't work is that the .ini file (that the phone is provisioned with on login) still has the old password. A work-around is for the superadmin to create a new profile (Phones>Send Profiles button) for the user's softphone (after the end-user has changed their password). Subsequently the user's softphone needs to logout and back in again, and now both accounts work.
To resolve this, the system would have to generate new phone profiles for all the user's phones (Bria specifically) that have XMPP built in, after the user changes their password in the portal.
Yes, so we have now the same password for user portal and XMPP (minimum 8 characters) and a voicemail PIN (minimum 4 characters) So during every login in bria, we should make sure that we write the password in the ini file - please open a ticket

A second non-related issue which throws end-users into a tizzy is that the login screen to the portal asks for their PIN, when it actually needs their password (specifically, their XMPP password). Despite its heading, the user's Voice Mail PIN will not work. The heading of this field on the login screen ought to be "Password:".
I agree is confusing, in general when users talk about PIN they think at voicemail pin, so yes, would be better to write there Password instead

Mircea

Thanks!

Nicholas Drayer
Managing Director
Dyrand Systems
T. 604.408.4415 Ext. 319<tel:[phone]%20Ext.%20319>
www.dyrand.com<http://www.dyrand.com>




_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/


_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square

Suite 201

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin<http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com<http://www.ezuce.com>

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and those who don't.

[Alex Mateescu]

User feedback is highly appreciated, thanks.

Alex


On Thu, Nov 22, 2012 at 9:07 PM, Nicholas Drayer

Thank you, I’ve entered them both. I’ve no idea how to solve programming
issues, but I figure it’s helpful to the developers for me to enter them!
Nicholas****
** **
*Sent:* November-22-12 2:06 AM
*To:* Discussion list for users of sipXecs software
*Subject:* Re: [sipx-users] sipXecs 4.6/bria password reset design bug &
login screen wording****
** **
We also have a request in our internal tracker for automatically sending
bria profiles after password change...****
** **
This tracker item probably should have been in the open source tracker.***
*
** **
Mike****
** **
****
** **
On Thu, Nov 22, 2012 at 3:58 AM, Nicholas Drayer <
I’m not sure this is the right method of reporting issues – please tell me
if I should be doing this differently.****
****
For opening bugs we use Jira : http://track.sipfoundry.org ****
I’m running sipXecs 4.6 with Bria 3 softphones. I believe there’s a
design bug in the feature for end-users to reset their password:****
1. End user goes to the end-user portal and resets their password
(My Information>Unified Messaging, the top 2 fields Password and Confirm
Password);****
2. End user logs in with Bria softphone, using the new password;****
3. The SIP account logs in fine, the XMPP account does not.****
The reason that the XMPP account doesn’t work is that the .ini file (that
the phone is provisioned with on login) still has the old password. A
work-around is for the superadmin to create a new profile (Phones>Send
Profiles button) for the user’s softphone (after the end-user has changed
their password). Subsequently the user’s softphone needs to logout and back
in again, and now both accounts work.****
To resolve this, the system would have to generate new phone profiles for
all the user’s phones (Bria specifically) that have XMPP built in, after
the user changes their password in the portal.****
Yes, so we have now the same password for user portal and XMPP (minimum
8 characters) and a voicemail PIN (minimum 4 characters) So during every
login in bria, we should make sure that we write the password in the ini
file - please open a ticket****
****
A second non-related issue which throws end-users into a tizzy is that the
login screen to the portal asks for their PIN, when it actually needs their
password (specifically, their XMPP password). Despite its heading, the
user’s Voice Mail PIN will not work. The heading of this field on the login
screen ought to be “Password:”.****
I agree is confusing, in general when users talk about PIN they think at
voicemail pin, so yes, would be better to write there Password instead****
** **
Mircea ****
****
Thanks!****
****
Nicholas Drayer****
Managing Director****
Dyrand Systems****
T. 604.408.4415 Ext. 319****
www.dyrand.com****
****
****
****
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/****
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/****
****
** **
--
Michael Picher, Director of Technical Services
eZuce, Inc.****
300 Brickstone Square****
Suite 201****
Andover, MA. 01810****
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher> ****
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com****
** **
------------------------------------------------------------------------------------------------------------
****
There are 10 kinds of people in the world, those who understand binary and
those who don't.****
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/