[Asterisk-Users] Polycom 600 Ring-Answer (but not ring!)

[Billy Dunn]

Kristian Kielhofner wrote:

> Billy Dunn wrote:
>
>> I have a bunch of Polycom Soundpoint 600 phones and they are working 
>> great.  The only thing I can't seem to get them to do is to 
>> ring-answer without the ring.
>>
>> This is what I have in my sip.cfg file on the boot server:
>>
>> <alertInfo voIpProt.SIP.alertInfo.2.value="RA" 
>> voIpProt.SIP.alertInfo.2.class="4"/>
>> <alertInfo voIpProt.SIP.alertInfo.3.value="RANR" 
>> voIpProt.SIP.alertInfo.3.class="5"/>
>>
>> <RING_ANSWER se.rt.4.name="Ring Answer" se.rt.4.type="ring-answer" 
>> se.rt.4.timeout="2000" se.rt.
>> 4.ringer="2" se.rt.4.callWait="6" se.rt.4.mod="1"/>
>> <RING_ANSWER_NR se.rt.5.name="Ring Answer NR" se.rt.5.type="answer" 
>> se.rt.5.timeout="1" se.rt.5.
>> ringer="1" se.rt.5.callWait="6" se.rt.5.mod="1"/>
>>
>> This is what I have in my extensions.conf file:
>>
>> ; bdunn's Office Extension AUTO ANSWER - WITH RING
>>    exten => 83004,1,SetVar(ALERT_INFO="RA")
>>    exten => 83004,2,Macro(stdexten,3004,${BDUNNOFFICE})
>> ; bdunn's Office Extension AUTO ANSWER - NO RING
>>    exten => 93004,1,SetVar(ALERT_INFO="RANR")
>>    exten => 93004,2,Macro(stdexten,3004,${BDUNNOFFICE})
>>
>> This does most of what I need - 93004 answers to speakerphone 
>> automatically, but there is a ring (a very short ring).  Dialing 
>> 83004 gives a moderate length ring and answers as expected.  I'd 
>> really like to do it without the ring if possible.
>>
>> If there are any Polycom pros out there, I could use some help.  I 
>> have already checked out this: 
>> http://www.voip-info.org/tiki-index.php?page=Polycom%20auto-answer%20config#comments 
>>
>>
>> Thanks.
>
>
> My Polycom configs at:
>
>  http://www.krisk.org/asterisk/pcom/
>
> will do what you are looking for.  Set your ALERT_INFO variable to 
> equal "AA" (Auto Answer) and the phone will go right to speaker phone 
> mode, no ring.
>
Oh yeah... I've been ripping off your work a lot.  It's been a big help 
to me.  Thanks.  I think the next message clears up where I went wrong.