There was a concern with letting this happen before answer.<br>I changed it in last revision, try it out.<br>The problem is that the way polycom does it, it violates the RFC.<br><br>Also know you can set sip_callee_id_name and sip_callee_id_number before you send a ring_ready pre_answer or answer to send the display update in that packet instead of sending a separate one.<br>
<br><br><div class="gmail_quote">On Fri, Oct 23, 2009 at 7:09 AM, Helmut Kuper <span dir="ltr">&lt;<a href="mailto:helmut.kuper@ewetel.de">helmut.kuper@ewetel.de</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Hello,<br>
<br>
when I use pre_answer app and right after that the send_display app,<br>
there is no INFO message anymore.<br>
<br>
My dialplan condition:<br>
<br>
&lt;condition field=&quot;${sip_hangup_phrase}&quot; expression=&quot;^Do Not Disturb&quot;<br>
break=&quot;on-true&quot;&gt;<br>
                        &lt;action application=&quot;pre_answer&quot;/&gt;<br>
                        &lt;action application=&quot;send_display&quot; data=&quot;Bitte<br>
nicht stoeren&quot;/&gt;<br>
                        &lt;action application=&quot;sleep&quot; data=&quot;500&quot;/&gt;<br>
                        &lt;action application=&quot;playback&quot;<br>
data=&quot;ansagen/22.wav&quot;/&gt;<br>
&lt;/condition&gt;<br>
<br>
changing &quot;pre_answer&quot; to &quot;answer&quot; works, but I don&#39;t want to answer the<br>
call for error messages.<br>
<br>
I use latest SVN trunk.<br>
<br>
regards<br>
helmut<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.7 (MingW32)<br>
<br>
iD8DBQFK4Z0O4tZeNddg3dwRAkB/AKCLN9luR0KGunHVGso2t3wJIo4dqQCdGdjp<br>
CY+yWGyVlyDpDs//WFtCqiA=<br>
=eG4W<br>
-----END PGP SIGNATURE-----<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>