5 thoughts on - Auto-answer Call

• I’m just a 1.2 Luddite…

  I have this for a Sipura:

  exten = _!.,n,sipaddheader(Call-Info:\;answer-after=0)

  Maybe the quotes or the space after the semi-colon?

  Maybe wireshark would yield a clue?

• thanks for your response ,

  i test this solution but the issue still the same

  any other solution thanks and regards

  2014-02-04 Steve Edwards :

• Please don’t top post.

  How does what you see in wireshark compare to what the snom expects?

  Can you enable debug/verbose syslogging on the phone to see if it complains about anything?

• Here is a list of headers used for various vendors, I can’t remember which one is for Polycom.

  SIPAddHeader(Alert-Info: Ring Answer);
  SIPAddHeader(Alert-Info: Info=Alert-Autoanswer);
  SIPAddHeader(Call-Info:\;Answer-After=0);
  SIPAddHeader(P-Auto-Answer: normal);
  SIPAddHeader(Answer-Mode: Auto);

  Larry.

• hi

  when i try to this with page()

  exten => 506,1,SIPAddHeader(“Call-Info:__\; answer-after=0”)
  exten => 506,n,page(SIP/105)

  CLI>Accepting call from ‘0661xxxxxx’ to ‘506’ on channel 1/13, span 1
  — Executing [506@default:1] SIPAddHeader(“DAHDI/13-1”, “”Call-Info:__;
  answer-after=0″”) in new stack
  — Executing [506@default:2] Page(“DAHDI/13-1”, “SIP/105”) in new stack
  — Called 105
  — Playing ‘beep’ (language ‘en’)
  — SIP/105-000000c7 is ringing
  — SIP/105-000000c7 is ringing
  — SIP/105-000000c7 is ringing
  — Created MeetMe conference 1023 for conference ‘1894843837d’
  — SIP/105-000000c7 is ringing
  — Span 1: Channel 1/13 got hangup, cause -1
  — Hungup ‘DAHDI/pseudo-358137724’
  == Spawn extension (default, 506, 2) exited non-zero on ‘DAHDI/13-1’
  — Hungup ‘DAHDI/13-1’

  and the call hungup

  when i use the Dial the sip/105 still ringing

  thanks and regards

  2014-02-05 Larry Moore :