always opt on the side of allowing for more security... even if a regular user can shoot themselves in the foot. maybe a simple warning on PIN change through the GUI that they have entered a complex password that may make it difficult to enter their PIN from a phone.
Also, allow an administrator to shoot themselves in the foot... just give them an extra warning :-) Mike On Thu, Sep 22, 2011 at 7:51 AM, Michael Picher <[email protected]> wrote: > understood... but if you don't get to vm through your phone you might want > a more complex pin. > > > > On Thu, Sep 22, 2011 at 7:50 AM, Kumaran T <[email protected] > > wrote: > >> ** >> >> If pin is special character then user cannot enter into VM through >> phone.. >> >> Kumaran T >> >> >> On 9/22/2011 5:16 PM, Michael Picher wrote: >> >> For conference PINS it makes sense. PINs however are used for more than >> just getting to voicemail so they need to allow special characters. >> >> Mike >> >> On Thu, Sep 22, 2011 at 7:42 AM, <[email protected]> wrote: >> >>> What about alpanumeric for phones (with warning in Description) and >>> numeric-only for conferences? >>> >>> Paul >>> >>> Michael Picher <[email protected]> wrote on 22-09-2011 13:38:20: >>> >>> >>> >>> > I disagree that all pins should always be numeric. We need to allow >>> > special characters. If the user does not use a phone to access VM >>> > then they may want a more complex password. >>> >>> > >>> > Thanks, >>> > Mike >>> >>> > On Thu, Sep 22, 2011 at 7:35 AM, Tony Graziano < >>> [email protected] >>> > > wrote: >>> > all pins should always be numeric IMO. you cannot enter special >>> > charade via a numeric keypad. >>> > On Sep 22, 2011 7:31 AM, "Kumaran T" <[email protected]> >>> wrote: >>> > > Hi All, >>> > > By normal speaking the special characters can be allowed for pin.But >>> > > if user have special character in the pin then user cannot enter to >>> into >>> > > conference or voicemail inbox through the phone either software or >>> > > hardphone.So whether its valid to have special character as the >>> pin?If >>> > > it can be then help text should be provide.. >>> > > >>> > > Regards, >>> > > Kumaran T >>> > > _______________________________________________ >>> > > sipx-dev mailing list >>> > > [email protected] >>> > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >>> > >>> > _______________________________________________ >>> > sipx-dev mailing list >>> > [email protected] >>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >>> > >>> >>> > >>> > -- >>> > Michael Picher >>> > eZuce >>> > Director of Technical Services >>> > O.978-296-1005 X2015 <978-296-1005%20X2015> >>> > M.207-956-0262 >>> > @mpicher <http://twitter.com/mpicher> >>> > www.ezuce.com >>> > _______________________________________________ >>> > sipx-dev mailing list >>> > [email protected] >>> > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >>> >>> _______________________________________________ >>> sipx-dev mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >>> >> >> >> >> -- >> Michael Picher >> eZuce >> Director of Technical Services >> O.978-296-1005 X2015 >> M.207-956-0262 >> @mpicher <http://twitter.com/mpicher> >> www.ezuce.com >> >> >> _______________________________________________ >> sipx-dev mailing [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> >> >> >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > > > > -- > Michael Picher > eZuce > Director of Technical Services > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com > > -- Michael Picher eZuce Director of Technical Services O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
