asterisk users - Feb 2005 - Polycom screwed up Messages button in 1.4.1?

I think Polycom has added another feature that nobody wants.

With MWI configured, and a phonexxx.cfg that has this:

    <msg msg.bypassInstantMessage="1">
       <mwi msg.mwi.1.subscribe=""
msg.mwi.1.callBackMode="contact"
msg.mwi.1.callBack="XXX" msg.mwi.2.subscribe=...>
    </msg>

Under 1.3.4 and earlier, the phone would immediately connect you to 
extension XXX.

Under the 1.4.1 firmware, when you press the messages hard button on 
the phone, the phone takes you to a "Messages" screen that tells you 
how many new, old, and urgent messages you have - useful, maybe, but 
also somewhat redundant if the MWI light is blinking.  You then have to 
press a "connect" soft button to actually connect to extension XXX.

1. Has anybody figured out a way around this (i.e. restore the behavior 
of immediate connection to extension "XXX"

2. Polycom (and any other phone manufacturers that are reading this):  
It has been my experience that users DON'T WANT EXTRA STEPS.  And, 
USERS DON'T WANT SOFT BUTTONS.  The more hard buttons with ONE press, 
the better.

> Message: 4
> Date: Tue, 8 Feb 2005 13:09:23 -0500
> From: Noah Miller <noah@rosecompanies.com>
> Subject: [Asterisk-Users] Polycom screwed up Messages button in 1.4.1?
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> 	<asterisk-users@lists.digium.com>
> Message-ID: <eac61b60be5f8d238c9ab95256e1fc97@rosecompanies.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
> 
> I think Polycom has added another feature that nobody wants.
> 
> With MWI configured, and a phonexxx.cfg that has this:
> 
>     <msg msg.bypassInstantMessage="1">
>        <mwi msg.mwi.1.subscribe=""
msg.mwi.1.callBackMode="contact"
> msg.mwi.1.callBack="XXX" msg.mwi.2.subscribe=...>
>     </msg>
> 
> Under 1.3.4 and earlier, the phone would immediately connect you to 
> extension XXX.
> 
> Under the 1.4.1 firmware, when you press the messages hard button on 
> the phone, the phone takes you to a "Messages" screen that tells
you
> how many new, old, and urgent messages you have - useful, maybe, but 
> also somewhat redundant if the MWI light is blinking.  You 
> then have to 
> press a "connect" soft button to actually connect to extension
XXX.
It works great here, under 1.4.1
> 
> 1. Has anybody figured out a way around this (i.e. restore 
> the behavior 
> of immediate connection to extension "XXX"
I suggest you take a look at your configuration files, especially
ipmid.cfg, in <user_preferences>, the attribute
"up.oneTouchVoiceMail".


This setting has had to be set since 1.3.1 (at least I had to set it).
Perhaps you clobbered it when you upgraded the SIP stuff?
> 
> 2. Polycom (and any other phone manufacturers that are 
> reading this):  
> It has been my experience that users DON'T WANT EXTRA STEPS.  And, 
> USERS DON'T WANT SOFT BUTTONS.  The more hard buttons with ONE press, 
> the better.
> 
I like soft buttons.  They're terribly useful, as people push buttons
that have no real use in contexts that don't make sense (i.e. they press
Call Forward on our old phone system, when they really mean Call
Transfer).  When they use soft buttons, and the phone is *intelligently*
designed, then all the useful features appear, and all the irrelevant
ones are inaccessible.  

That having been said, I would like to be able to easily reprogramm some
hard buttons for 1-touch dialling and the like, or to access other
features.

As far as extra steps, I don't think there are any extra steps.  Please
take a look at your configurations and tell me if you disagree.

Thanks,
David Gomillion

>  I suggest you take a look at your configuration files, especially
> ipmid.cfg, in <user_preferences>, the attribute
"up.oneTouchVoiceMail".
Arrgh.  Quite right, David.  I guess I'll stop posting my rants, and 
actually keep track of my config files.  Yet another stupid error on my 
part.