search for: vm_authentication

On 2017-04-18 08:17 PM, Pete Mundy wrote: >> On 19/04/2017, at 7:58 am, D'Arcy Cain <darcy at VybeNetworks.com >> <mailto:darcy at VybeNetworks.com>> wrote: >> >> <snip> >> Everything looks the same as another one that works except for two >> things. The one that works doesn't have the "Probation passed" lines. >> I am

On 2017-04-18 02:42 AM, Pete Mundy wrote: > Try this: > > asterisk -r > core set verbose 10 > [get user to trigger fault] > [examine console output, and post to list if still unclear] > > If you don't solve it yourself, then we'll be able to help further once > we've seen the output. I can't see much more than at my previous debug level but here it is

Hi, I am getting the following error when I attempt to listen to voice messages by dialing 9999 (I can hear nothing): --Executing VoiceMailMain ("SIP/2092-6918", "2092") in new stack --Playing 'vm-password' (language 'en') WARNING: app_voicemail.c:4922 vm_authentication: Unable to read password. I read in previous posts that this may be to do with the dtmf settings and have set both (asterisk and BT100) to info. This has not helped. My phones register with SER (port 5060) and use Asterisk for voicemail (port 5064). My configs are below along with my BT100 settin...

Hello: I am relatively new to Asterisk, so this hopefully is an easy question for someone: I'm unable to get into voicemail to retrieve messages. Since I'm learning, the conf files are very basic. The relevant portions of the voicemail.conf is: [general] format=wav serveremail=asterisk@myserver.com append=yes maxgreet=30 maxmessage=120 [default] 100 => 9999,100,me@myserver.com When

...have taken another bizarre twist.. I have continued getting the error when 2092 tries to listen to messages by dialing 9999. --Executing VoiceMailMain ("SIP/2092-6918", "2092") in new stack --Playing 'vm-password' (language 'en') WARNING: app_voicemail.c:4922 vm_authentication: Unable to read password. Then I decided to plug out my BT100 and left it plugged out for a few hours. When I plugged it back in and dialed 9999 for voicemail, bizarrely I could hear the voicemail main menu and was prompted for a password. When I entered the password, I was able to listen to the...

I've been trying to use the VMAuthenticate function in 1.2+. This function is supposed to "behave[s] the same way as the Authenticate application, but the passwords are taken from voicemail.conf." The problem is that it always gives the "comedian mail" prompt and requests the mailbox number, even though I provide the mailbox number already. The upshot is that

I (sometimes) get this error message: WARNING[17191]: app_voicemail.c:2411 leave_voicemail: No entry in voicemail config file for 'irstname.lastname' I can see the value of the argument is "firstname.lastname" when this line executes in the std-exten macro: exten => s-NOANSWER,1,Voicemail(u${ARG1}) ; If unavailable... But the error message drops the first character. It

Hello, Asterisk 1.4.26.2, FreeBSD 8.0-RELEASE We have a very simple setup, using SIP softphones and a simple diaplan as follows in the examples below. When I dial the 700 extension it asks me for the extension and password, and it always says "login incorrect". The mail system send the email ok and Ekiga shows that I have vaoicemail, so the only thing that is failing is the actual

On 2017-04-19 02:39 AM, Pete Mundy wrote: > Hmm... Above my pay grade I'm afraid! Looking at your 'voicemail > show users' I can't see why the vm_authenticate function is > failing to read the username :( I can answer that one. It's because we can't enter 'stocktrans2' from a telephone so we just hang up. The question is, why does it ask for the

Hi List, Merlin Magix hardware v02 I'm trying to get asterisk to act as a voicemail server for a lucent merlin magix PBX that we purchased used. We have 4 FXO channels between the two PBXs on a Sangoma A200 card. The 770 dialgroup is working properly, in that calls to 770 are answered by Asterisk. The magix is sending mode codes in the format #XX#XXX#, where the 2nd block of digits

...have taken another bizarre twist.. I have continued getting the error when 2092 tries to listen to messages by dialing 9999. --Executing VoiceMailMain ("SIP/2092-6918", "2092") in new stack --Playing 'vm-password' (language 'en') WARNING: app_voicemail.c:4922 vm_authentication: Unable to read password. Then I decided to plug out my BT100 and left it plugged out for a few hours. When I plugged it back in and dialed 9999 for voicemail, bizarrely I could hear the voicemail main menu and was prompted for a password. When I entered the password, I was able to listen to the...

Hello, I have just updated my Asterisk installation from 1.2x to 1.4 (on FreeBSD) - mostly everything seem to work fine. However, I use G.729 pass-thru - and I have before successfully used the following setup: http://www.voip-info.org/wiki/index.php?page=Asterisk%20G.729%20pass-thru However, it is not working with 1.4 - I see the following errors: [Apr 16 15:59:24] WARNING[10139]:

Mark, While these samples are pretty good they do not work "out of the box" - there are a couple of issues: 1. the samples are 44100 samples/second and Asterisk needs them to be at 8000 samples/second. This is what happens if you prune out all of the Amercian voicemail prompts and substitute yours: Asterisk 1.2.7, Copyright (C) 1999 - 2006 Digium, Inc. and others. Created by Mark

We have a template for extensions and voicmail. They look like this: exten => %ACCOUNT%,1,Verbose(0,Entering extension %ACCOUNT%) same => n(DialDesk),Verbose(0,${CALLERID(all)} Calling ${EXTEN}) same => n,Dial(SIP/%ACCOUNT%,30) same => n(VoiceMail),Set(CDR(userfield)=VoiceMail) same => n,Verbose(0,${CALLERID(all)} going into voice mail for %ACCOUNT%)

Hi all, I've been running Asterisk with a TDM400P for about 6months, no problems. 2 in/outgoing analog lines, one analog phone. Recently I was messing with the XTEN client, got to finagling with things, and not knowing what was wrong I upgraded from 1.0.7 to 1.0.9 (both asterisk + zaptel). I was testing various things, and found everything worked except outgoing calls. So I checked