On our old system we were able to set our phones up so that if we pressed the "envelope" button, we were taken directly into our voicemail without a password prompt.
Now that we have upgraded to ThirdLane, our phone's "envelope" button resets to extension "100" every day, and when we change it (in the phone) to point to our extension... we still have to enter our VM password.
How can I set it up so that our "envelope" buttons point to our individual voicemail accounts without a password
*note* i do not want to remove the password all together because our Webmin is public over the internet and we want it secured for access.
actually it looks like the
actually it looks like the problem is that the phone continues to reset. Does anyone know how to persist config when the phone reboots (currently reboots daily).
My previous reseller told me that the phone needed to reboot daily in order to pull the newest data.
re: actually it looks like the
If you are using auto-provisioning, then any changes made at the phone will be over written whenever the phone re-syncs if the setting is contained in the auto-provisioning config for that phone.
You can configure the voicemail extension with the following setting in /etc/asterisk/provisioning/linksys_phone_9xx.cfg (which creates spa$MAC.cfg when a phone is provisioned)
<Voice_Mail_Number>${VOICEMAIL_NUMBER}</Voice_Mail_Number>
I noticed that the newer version has a settings contained in the same file that requires a reset for them to be applied which will happen whenever the phone resyncs (24hours):
<Line_Enable_1_>No</Line_Enable_1_>
<Short_Name_1_> </Short_Name_1_>
These do not need to be included in /etc/asterisk/provisioning/linksys_phone_9xx.cfg and only need to be applied once during a reset, and should be added to /etx/asterisk/provisioning/linksys_spa_model.cfg which ends up as spa942.cfg etc.
Copy these files to /etc/asterisk/user_provisioning/ and make the changes there, they will override the defaults but protect them from being overwritten during upgrades.
Hope this helps
Allister
Wow that is totally
Wow that is totally complicating to me. What is the downfall of just turning off Auto Provisioning?
I don't know how to manage any config files (I'm a Windows guy)... Does the ThirdLane Webmin give me any options to edit it thru the GUI?
Wow that is totally
You edit the config files through the GUI, go to: Tools->Configuration Editor.
A quick hack to get it going: Select /etc/asterisk/provisioning/linksys_phone_9xx.cfg and edit 'Voice_Mail_Number' xml tag to be the extension you have been manually configuring on the phones.
Then go to Tools->Auto-Provisioning, select the phones you want to update and click 'Provision Selected' button. Note! Phones will not update until they re-sync (24 hours for you), you can restart the phone to pick them straight away.
Regards
Allister
Currently each phone dials
Currently each phone dials its extension so phone A would use 101 phone B would use 102 etc. Should I maybe setup a custom script for it?
Well I changed the line to
Well I changed the line to
*85
Then I restarted the system and restarted the phone.
When I it the VM button, it still dialed 100
So what I have done for now is create a feature code for "100" and have it check VM... suppose it works for now.
that all depends on the model of phone.. but you would have to assign a feature code to perform that task. We used to do password-less voicemail from phones until one customer had an employee sneak around and listen to the CEO's voicemail looking for private information of a pending merger. Since then we just use the login version. the 's' option of VoiceMailMain will bypass password checking.
for polycom phones to call a specific extension on the voicemail button its...
up.oneTouchVoiceMail="1"
msg.bypassInstantMessage="1"
msg.mwi.1.callBackMode="contact"
msg.mwi.1.callBack="*98"
i have no idea how to do other models of phones.