Hmm... not too sure what's up with this one. I've only used AMD with Zap channels, so I don't know if there are any hidden gotchas with using SIP.
Has anyone else used app_amd with SIP calls? -MC _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Halliday Sent: Wednesday, January 24, 2007 1:37 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] setting up AMD now I have amd.conf set to this: initial_silence = 3700 greeting = 2500 after_greeting_silence = 1200 total_analysis_time = 6000 min_word_length = 100 between_words_silence = 50 maximum_number_of_words = 4 silence_threshold = 860 The resulting log is this: Jan 24 18:53:04 DEBUG[31555] chan_sip.c: build_route: Contact hop: <sip:[EMAIL PROTECTED]> Jan 24 18:53:04 VERBOSE[31567] logger.c: -- AMD: SIP/sip.broadvoice.com-087743a0 6079362172 (null) (Fmt: 4) Jan 24 18:53:04 VERBOSE[31567] logger.c: -- AMD: initialSilence [3700] greeting [2500] afterGreetingSilence [1200] totalAnalysisTime [6000] minimumWordLength [100] betweenWordsSilence [50] maximumNumberOfWords [4] silenceThreshold [860] Jan 24 18:53:20 DEBUG[31555] chan_sip.c: Scheduled a registration timeout for sip.broadvoice.com id #19 Jan 24 18:53:20 DEBUG[31555] chan_sip.c: Stopping retransmission on ' [EMAIL PROTECTED]' of Request 104: Match Found Jan 24 18:53:20 DEBUG[31555] chan_sip.c: Registration successful Jan 24 18:53:20 DEBUG[31555] chan_sip.c: Cancelling timeout 19 Jan 24 18:53:28 DEBUG[31555] chan_sip.c: Auto destroying call '[EMAIL PROTECTED] ' Jan 24 18:53:32 DEBUG[31555] chan_sip.c: Stopping retransmission on '[EMAIL PROTECTED]' of Request 102: Match Found Jan 24 18:53:36 VERBOSE[31567] logger.c: -- AMD: HANGUP Jan 24 18:53:36 DEBUG[31567] app_amd.c: Got hangup Jan 24 18:53:36 DEBUG[31567] pbx.c: Extension s, priority 2 returned normally even though call was hung up Jan 24 18:53:36 DEBUG[31567] chan_sip.c: update_call_counter(6079362172) - decrement call limit counter On 1/24/07, Michael Collins < <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]> wrote: _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Halliday Sent: Wednesday, January 24, 2007 11:56 AM To: asterisk-users@lists.digium.com Subject: [asterisk-users] setting up AMD I'm trying get this working. I've looked through the list, and can't see how to get AMD to print out more. I have it call and say Hello like I normally would. I've tried to say more and less doesn't seem to matter. After I hangup it does recognize hangup. Here's logging during an attempt where I make outbound call and answer, but then hangup after 1-2 seconds: Jan 24 17:01:37 VERBOSE[31455] logger.c: -- AMD: SIP/sip.broadvoice.com-098c4aa8 6079362172 (null) (Fmt: 4) Jan 24 17:01:37 VERBOSE[31455] logger.c: -- AMD: initialSilence [8000] greeting [1500] afterGreetingSilence [300] totalAnalysisTime [5000] minimumWordLength [120] betweenWordsSilence [50] maximumNumberOfWords [5] silenceThreshold [256] Jan 24 17:01:44 DEBUG[31437] chan_sip.c: Auto destroying call '[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ' Jan 24 17:01:45 DEBUG[31447] manager.c: Manager received command 'Command' Jan 24 17:01:45 DEBUG[31447] manager.c: Manager received command 'Command' Jan 24 17:01:45 DEBUG[31447] manager.c: Manager received command 'Command' Jan 24 17:01:56 VERBOSE[31455] logger.c: -- AMD: HANGUP Jan 24 17:01:56 DEBUG[31455] app_amd.c: Got hangup The amd.conf: [amd] initial_silence = 3500 greeting = 1500 after_greeting_silence = 300 total_analysis_time = 5000 min_word_length = 120 between_words_silence = 50 maximum_number_of_words = 5 silence_threshold = 256 In extensions.conf [outboundmsg1] exten => s,1,NoCDR exten => s,n,AMD exten => s,n,GotoIf($[${AMDSTATUS}=AMD_PERSON]?humn:mach) exten => s,n(mach),WaitForSilence(2500) exten => s,n,Playback(outboundmsgs/msg1) exten => s,n,Hangup exten => s,n(humn),WaitForSilence(500) exten => s,n,Playback(outboundmsgs/msg1) exten => s,n,Hangup Peter, It looks like your initial silence setting might be having trouble. The amd.conf file has a value of 3500 but the log file is showing 8000. Try changing the amd.conf to something like 3000 and issue a "reload" at the CLI. Make another test call and see if the trace still shows 8000 for the initial silence. I think having an initial silence value that is longer than the total analysis time might be causing the undesired behavior. Let us know what happens when you try to modify the initial silence value. -MC _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users <http://lists.digium.com/mailman/listinfo/asterisk-users>
_______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
