The issue as I understand it is that you are wanting to have a visual presence of when the group VM has an unread message. This is a new feature according to the phone firmware release notes and not very well documented as to how to implement or the ramifications of what the impact might be. I am not able to test at the moment as my GXV3350 does not have the needed settings (sigh!).
The phone firmware release document reveals the following for the feature -
In looking at the recently released config parameters for the same firmware (11.71) and model (gxp2130-2170), the only related setting shown is -
Given the firmware instructions shown earlier, one would think that the config parameters would show P60076 thru P60576. It is not clear to me as to why GS only shows the setting for what appears to be account 2 in the config parameters.
With regard to the group VM function, GS apparently envisioned it as a forwarding service. If a VM was left, the message would be forwarded to the VM box of the members assigned to same and as such, that would engage the MWI light for each member. Each member was then expected to handle the message as if the message had been left by a caller directly to their individual box. Whatever action was taken by a given member in dealing with the VM had no impact on the other members’ duplicate VM and as a result there would be confusion and coordination required between the members to handle the message correctly. This has been a contentious issue for many users since day 1 with numerous pleas made to make it a shared VM as can be found in other Asterisk based system, but GS has been silent on the issue.
I do not see any reference to using *98 in conjunction with the new feature. This is a dial code that is typically used to access a VM box other than the one associated to the dialing extension. In essence, it allows one to dial and access their own extension from any attached extension should they not be using their own phone. It has nothing do with monitoring; only triggering the UCM to offer the prompt that requests the desired extension’s VM to be accessed followed by a prompt for the PIN code.
Having said the above, you may need to keep in mind how you assign (or not) members to the group VMs. You should assume that any member of the group who is also monitoring the group VM extension (if that is even allowed) will likely get the MWI for both their own extension as the message is forwarded in addition to the MWI from the monitoring function. If you try and delete the message from the group, it will have no affect on any of the members’ VM as it will be too late.
So, back to the settings -
It is certainly not clear to me how the settings provided above are meant to be implemented. So I can offer what I believe may be a possible configuration -
Looking at the Web Config settings, I assume it should be the desired extension number (66666 example) to be monitored. I am assuming that it is what I will call a “psuedo account”-
Similarly input into the same field by using the needed Pcode for the account and with the string being that of the extension. So, if using account one and wanting to input 66666 into the field using zero-config, the entry would be -
Just as one can enter the VM account associated to the extension that is dialing without having to enter the PIN code, I assume this provides for a similar function. However, there still needs to be a button by which to access this setting in addition to seeing the visual button turning into a MWI.
I am uncertain as to what the “voicemail programmable keys” are, but I assume these to be the VPK/VMPK keys that can be used where the option of “Voice Mail” is offered as a mode-
The definition for the setting is -
I take it that the VPK is set to Voice Mail and the value is set to the same desired extension number to be monitored as that used with the Pcode from earlier.
I am guessing that when the VPK button for VM is pressed, it somehow associates to the Pcode in the account setting which has the extension number that when sent to the UCM, the UCM will not ask for the PIN code for the remote VM box. This is no different than pressing the VM button on the front panel and getting to the extension’s VM without having to enter the PIN.
If the VPK were the only setting configured, it will monitor the extension, but pressing the button will require the PIN.
It also appears that only one monitored extension is allowed per phone account given the Pcode values whose limit is then dictated by the phone model in use. So, this too will need some guess work and experimentation for what works best for a given need.
Again, the above suggestions are just that and I may be entirely wrong. The documentation does not go into any detail, the wording is somewhat open to interpretation and you need to refer to several documents to get any kind of sense of what might be the intent.