Re: [asterisk-users] automon=*, Dial(, , Ww), rfc2833, canreinvite=no, but...

2008-07-21 Thread Jared Smith
On Fri, 2008-07-18 at 13:02 -0400, Bill Michaelson wrote:
 After much checking and puzzling, I cannot get my Polycom 601 to
 toggle call recording with my Asterisk 1.4.21.1.
 
 I can see this in the feature*.conf file set:
 
 automon=*1
 
 and I can see a 'Ww' in the logged/traced call to dial().

Is the DYNAMIC_FEATURES variable set correctly?  It's been my experience
that not setting DYNAMIC_FEATURES is the number one problem people
encounter with one-touch recording.

 Finally, it might be worth noting that the packet traces show three
 RFC2833 end events for each DTMF code pressed.  This might be
 perfectly normal

Perfectly normal... nothing to worry about there.


-- 
Jared Smith
Training Manager
Digium, Inc.


___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[asterisk-users] automon=*, Dial(, , Ww), rfc2833, canreinvite=no, but...

2008-07-18 Thread Bill Michaelson
After much checking and puzzling, I cannot get my Polycom 601 to toggle 
call recording with my Asterisk 1.4.21.1.


Via FreePBX, I can set a user to always record, and the recording will 
show up in /var/spool/asterisk/monitor.


But if I try to start recording by toggling in-call, no luck.

I can see this in the feature*.conf file set:

automon=*1

and I can see a 'Ww' in the logged/traced call to dial().

and I can see the RFC2833 RTP packets going through Asterisk, both with 
rtp debug and with wireshark.


So my questions are:

1) How do I verify that asterisk actually saw the feature code spec upon 
restart/reload? I can't find any clues.


2) Are there any other parameters that have a bearing on this?

3) Is there anything I haven't thought of?

Finally, it might be worth noting that the packet traces show three 
RFC2833 end events for each DTMF code pressed. This might be perfectly 
normal, and I even tried fudging the automon string to ***111 just to 
compensate as an experiment, but it had no effect.


If I've done everything necessary to configure enabling the toggle 
function, then where should I see the failure/refusal to comply in any 
logs. I'm getting nothing in logs/traces.


A side question: freepbx is generating include statements with a leading 
#, a la C includes - or a la Perl/Shell/et al comments! This is OK? I've 
floundering with the suspicion that I'm overlooking something really dumb...


I would be grateful for some explicit diagnostic suggestions.




smime.p7s
Description: S/MIME Cryptographic Signature
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users