[Freeswitch-users] Auto-Answer based on Call-Info from originator

[Sean Devoy]

Hi Peter,

I don't have answer to your actual question about passing that header through, I will leave that to real tech folks. But, it seems you could solve this with clever dial plan "tricks."  For example, on your DID rule check if the caller-id is your cell phone and enable auto-answer if true.  Or, the brute force approach would be to get a second DID and put the auto-answer feature on that.

Of course passing the existing header would be much more elegant, let's see what else comes up.

Sean

From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Peter Hillier
Sent: Tuesday, April 01, 2014 8:40 PM
To: freeswitch-users at lists.freeswitch.org
Subject: [Freeswitch-users] Auto-Answer based on Call-Info from originator

I have a specific call scenario where I want to transfer a call and have the destination (REFER-TO) end answer automatically. Basically I own both devices and I am moving the call from my mobile VoIP client to my SIP deskphone. I want it to be seamless with no ringback or alerting introduced (hence the reason I am looking at auto answer).

My SIP deskphone supports auto-answer when the Call-Info header indicates "answer-after=0". This header is specified in the REFER from the originating device (mobile VoIP client). Freeswitch does not pass this header through to the destination device.

Is there any specific setting that I can do to pass this header through? I know that I can change the dialplan using the following:


<action application="export" data="sip_auto_answer=true"/>
But this triggers all calls to the destination to be auto-answered. I only want some of the calls to be answered (hence to reason I want the originator to specify this header).

Regards,
Peter

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140402/db348848/attachment-0001.html