Thanks Steven, So if I have understood this correctly, - login-keys allows a user to login into his own voicemail box by a. dialling his own number from an external/different phone b. wait for the call to timeout and enter voicemail IVR c. and then press '*' to enter the voicemail box - considering that '*' can be a key that any caller could press during the voicemail recording, it is important the each user in the system protects his/her mailbox with a passcode. For example, a caller might end up recording a message whose length is shorter than the 'min-record-len', and then press '*' - in this case, instead of being asked to record a longer message, he might actually find himself listening to the callee's recorded voicemails. If a passcode is in place, although the caller doesn't get a chance to record his message again, at least he wouldn't have access to someone else's voicemail box On Fri, Oct 10, 2014 at 3:58 AM, Steven Ayre <steveayre@gmail.com> wrote:
It gives them the ability to call into their voicemail externally from an unrecognised number and login to check their messages. You could use 'check', but that needs a separate extension which from PSTN probably needs either IVR or a separate DID. It's just more than one way to do it.
On 9 October 2014 01:42, Siri MM <sirimmfs@gmail.com> wrote:
Thanks Michael,
If I were to add the passcode, caller will be prompted for the passcode. After getting rid of login_keys, I don't observe this behavior anymore.
Could you please help me understand the login_keys feature better? Why should a caller be provided access to the voicemail box of a callee - that too when he is supposed to leave a recording? If one wanted to access his/her own voicemail box, then I thought the voicemail application with data="check default $${domain}" would suffice..
On Thu, Oct 9, 2014 at 6:06 AM, Michael Collins <msc@freeswitch.org> wrote:
Check in voicemail.conf.xml for a line with something like "login_keys". You can comment that out to prevent the ability of someone getting in. However, it also sounds like user 901 does not have a passcode set on his voicemail box. I would confirm that as well.
-MC
On Tue, Oct 7, 2014 at 9:40 PM, Siri MM <sirimmfs@gmail.com> wrote:
Hi,
I am currently using Freeswitch 1.2.7. I have setup a couple of extensions, with voicemail enabled as follows:
Under directory, extension xml has vm-enabled set to true
Under dialplan, I have the following: <extension name="901" > <condition field="context" expression="public" > </condition> <condition field="destination_number" expression="^901$" > <action application="ring_ready" /> <action application="set" data="call_timeout=10" /> <action application="set" data="continue_on_fail=true" /> <action application="set" data="hangup_after_bridge=true" /> <action application="bridge" data="user/901" /> <action application="answer" /> <action application="voicemail" data="default $${domain} 901" />
</condition> </extension>
Now, lets say I dial the above extension 901 from another extension, say 902. After 10 seconds, the call is redirected to voicemail: a. Voice prompt says: "Person at extension 901 is not available. Record message after the tone. Press any key or stop talking to end the recording" b. At this stage, if the caller (902) records a message, and presses any key other than '*', then the normal voicemail submenu continues (i.e. Press 1 to listen, 2 to save etc..) c. However, if the caller (902) were to record a message and press '*', instead of the above voicemail sub menu, he actually gain access to the callee's Voicemail box!! Caller 902 is able to listen to 901's messages, change settings etc.
Could anyone please let me know if I am missing something here?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE: http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org