Hello,

This has a bit of a long explanation... ultimately the question is why
adding a section to sip.conf made a difference to One Touch Record.

We're implementing a recording toggle using the "Record" button on a SIP
telephone and Asterisk's "One Touch Record" feature in features.conf.

It worked without problem when the calling party pressed the Record button,
but it didn't work when the called party pressed the Record button. When
the called party pressed the button Asterisk logged "Recording requested,
but no One Touch Monitor registered. (See features.conf)", even though it
was certainly enabled in features.conf

The destination was called with a dial string like SIP/1111@12.34.56.78:5060.
Eventually we worked out that adding a section to sip.conf like this
allowed it to start working:

[12.34.56.78:5060]
type = friend
... etc..

We already (before it started working) had a section almost identical but
without the port in the section name:
[12.34.56.78]
type = friend
... etc..

The question is, why did adding the section with the port in the name make
a difference? Is it because only Asterisk sip users (of which a friend is
one) are allowed to use One Touch Record? If so I don't see this documented
anywhere. Note that adding or removing the 'w' or 'W' options to the Dial
seems to make no difference at all, and following the addition of the
sip.conf section it works without either of these options in the Dial.

Thank you in advance for any insight into this.

-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

Check out the new Asterisk community forum at: https://community.asterisk.org/

New to Asterisk? Start here:
      https://wiki.asterisk.org/wiki/display/AST/Getting+Started

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

Reply via email to