asterisk users - Feb 2008 - Automon reliability issue

Hi list,

Can someone please explain how to get one touch recording (automon) to  
work reliably? I'm using Asterisk 1.4.14 on a Debian etch system. My  
current configuration includes the following settings:

In /etc/asterisk/sip.conf:

    [2000]
    ; Siemens Gigaset S675 IP wireless SIP phone.
    type=friend
    secret=1234
    context=phones-j
    dtmfmode=rfc2833
    qualify=yes
    host=dynamic

    [3000]
    ; Siemens Gigaset E455 wireless analog phone
    ; attached to Linksys PAP2T SIP adapter.
    type=friend
    secret=4321
    context=phones-j
    dtmfmode=rfc2833
    qualify=yes
    host=dynamic

In /etc/asterisk/features.conf:

    [featuremap]
    automon => *1

In /etc/asterisk/extensions.conf:

    [phones-j]
    exten => 2000,1,Dial(SIP/2000,,wW)
    exten => 3000,1,Dial(SIP/3000,,wW)

When I make or receive a call with either of these extensions, it's  
possible to start and stop recording by pressing "*1". However, this  
only works if I press the two keys in quick succession; if I'm not  
fast enough, all I see is lots of the following console output:

    -- Packet2Packet bridging SIP/1000-081cffb0 and SIP/2000-08241270
    -- Packet2Packet bridging SIP/1000-081cffb0 and SIP/2000-08241270
    -- Packet2Packet bridging SIP/1000-081cffb0 and SIP/2000-08241270
    -- Packet2Packet bridging SIP/1000-081cffb0 and SIP/2000-08241270

In other words, unless I'm also monitoring the console, I can never be  
sure that Asterisk has actually started or stopped recording a call  
after I press these keys. Frequently, I first have to make several  
attempts.

Is there some way to get automon to work reliably, or is the Monitor()  
function the only thing we can really count on to record calls?

Thanks,

Jaap

Jaap Winius wrote:
> Hi list,
>
> Can someone please explain how to get one touch recording (automon) to  
> work reliably? I'm using Asterisk 1.4.14 on a Debian etch system. My  
>   
We made this function reliable by including the word "quickly" in our 
instructions for pressing the keycode to start the recording. (Asterisk 
1.2.24 on Debian Etch)

Although a private confirmation beep to the initiator of the recording 
would be handy, this is the way things have to be in order to use the 
features.conf codes and still allow the use of * and # when calling 
outside IVR and voicemail systems. eg. "Enter your password followed by 
the pound key..."

regards,

Drew

-- 
Drew Gibson

Systems Administrator
OANDA Corporation
www.oanda.com

Jaap Winius wrote:
> only works if I press the two keys in quick succession; if I'm not  
> fast enough, all I see is lots of the following console output:
>
>   
featuredigittimeout = 500      ; Max time (ms) between digits for
                               ; feature activation  (default is 500 ms)

> In other words, unless I'm also monitoring the console, I can never be
> sure that Asterisk has actually started or stopped recording a call  
>   
courtesytone = local/stutter    ; Sound file to play to the parked caller
                                ; when someone dials a parked call
                                ; or the Touch Monitor is 
Activated/Deactivated.               


Doug


-- 
 
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety."