Auto Answer via SIP Header on Yealink

[nicolas]

Start FOP2 in debug mode and originate a call from it.. watch the originate command being set and if the variable is there or not

http://support.asternic.biz/?/selfhelp/view-article/how-to-debug-fop2/10

[avayax]

What should the variable in the originate command look like?

[nicolas]

A header similar to this in the Action: Originate:

Variable: __SIPADDHEADER51=Call-Info=answer-after=0.001

[avayax]

Looks like the variable is empty:
127.0.0.1 -> Exten: 5333
127.0.0.1 -> CallerID: Johann <5313>
127.0.0.1 -> Async: 1
127.0.0.1 -> Account:
127.0.0.1 -> Channel: SIP/5313
127.0.0.1 -> Context: from-internal
127.0.0.1 -> Action: Originate
127.0.0.1 -> Priority: 1
127.0.0.1 -> Variable:
127.0.0.1 -> ActionID: 229

FOP2 Version: 2.29.02
What to do?
Auto answer set to yes in FOP2 and this as the auto answer header:
__SIPADDHEADER51=Call-Info: answer-after=0.001
[attachment:56144aa8d10e3][attachment:56144b2605cc0]

[nicolas]

What FOP2 version are you running? What is the output from

/usr/local/fop2/autoconfig-buttons.sh | grep -i answer

?

[nicolas]

What FOP2 version are you running? What is the output from

/usr/local/fop2/autoconfig-buttons.sh | grep -i answer

?

[avayax]

FOP2 Version: 2.29.02
/usr/local/fop2/autoconfig-buttons.sh | grep -i answer
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
...
...
I also have this file in /etc/asterisk/fop2 for my HA cluster.
/etc/asterisk/fop2/autoconfig-buttons.sh | grep -i answer

autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
autoanswerheader=__SIPADDHEADER51=Call-Info=answer-after=0.001
...
...

[nicolas]

Did you upgrade FOP2 from a previous version? Are you positive the autoconfig script called from fop2.cfg is autoconfig-buttons.sh and not the old autoconfig-buttons-freepbx.sh ?

If so, you will have to start fop2 server in debug mode and try, then stop capturing logs and search the string "autoanswer" in the log file, is there any result?

http://support.asternic.biz/?/selfhelp/view-article/how-to-debug-fop2/10

[avayax]

I am making some progress on this issue.
The Auto Answer headers that work with Yealink phones are:
"__SIPADDHEADER51=Alert-Info:answer-after=0" or (0.001 if you prefer) and
"__SIPADDHEADER51=Alert-Info:info=alert-autoanswer"

This works on regular call initiate, but not when I pick up the call via mouse click from a queue or from a parking slot. The phone wouldn't auto answer then.
Any way to make this work?

[nicolas]

Headers are added to call origination, the Originate action in the Asterisk Manager Interface, as that actions allows you to set headers/variables.

When you pickup you are actually doing a Redirect action, and that action in manager does not have the option to set variables/headers.

So, it is just not possible to add those via AMI actions directly. There are workarounds but those involves modifying the dialplan, but FOP2 does not alter your dialplan and works with what you have (its a philosophical decision).