,,, или по клику запускаем по столу маленького такого робота, который доезжает до ИП-телефона и нажимает кнопку Answer.
При originate срабатывает автоответ, потому что в header-e SIP пакета INVITE на телефон
Код: Выделить всё
Call-Info: Answer-After=0.
Alert-Info: ;info=alert-autoanswer.
Alert-Info: <sip:>;info=alert-autoanswer.
Alert-Info: <sip:domain>;info=alert-autoanswer. domain = AsteriskPBX.mydomain.org
Much of the discussion of this topic in working group meetings and on
the mailing list dealt with differentiating "answering mode" from
"alerting mode". Some early work did not make this distinction. We
therefore proceed with the following definitions:
o Answering Mode includes behaviors in a SIP UA relating to
acceptance or rejection of a request that are contingent on
interaction between the UA and the user of that UA after the UA
has received the request. We are principally concerned with the
user interaction involved in accepting the request and initiating
an active session. An example of this might be pressing the "yes"
button on a mobile phone.
o Alerting Mode includes behaviors in a SIP UA relating to informing
the user of the UA that a request to initiate a session has been
received. An example of this might be activating the ring tone of
a mobile phone.
This document deals only with "Answering Mode". Issues relating to
"Alerting Mode" are outside its scope.
This document defines two SIP extension header fields: "Answer-Mode"
and "Priv-Answer-Mode". These two extensions take the same
parameters and operate in the same general way.
RFC5373 (c)
У входящий звонка скорее всего такого хидеоа нет. Но поставьте?