VoIP Mailing List Archives

[helmut.kuper at ewetel.de]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

when I use pre_answer app and right after that the send_display app,
there is no INFO message anymore.

My dialplan condition:

<condition field="${sip_hangup_phrase}" expression="^Do Not Disturb"
break="on-true">
<action application="pre_answer"/>
<action application="send_display" data="Bitte
nicht stoeren"/>
<action application="sleep" data="500"/>
<action application="playback"
data="ansagen/22.wav"/>
</condition>

changing "pre_answer" to "answer" works, but I don't want to answer the
call for error messages.

I use latest SVN trunk.

regards
helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFK4Z0O4tZeNddg3dwRAkB/AKCLN9luR0KGunHVGso2t3wJIo4dqQCdGdjp
CY+yWGyVlyDpDs//WFtCqiA=
=eG4W
-----END PGP SIGNATURE-----

_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org

[anthony.minessale at g...]

There was a concern with letting this happen before answer.
I changed it in last revision, try it out.
The problem is that the way polycom does it, it violates the RFC.

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.


On Fri, Oct 23, 2009 at 7:09 AM, Helmut Kuper <helmut.kuper@ewetel.de (helmut.kuper@ewetel.de)> wrote:

[helmut.kuper at ewetel.de]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Anthony,

thx, it works now again. But the only way get it to work is using
send_display after pre_answer. "(sip|originate)_callee_id_name" doesn't
work with playback.

regards
Helmut


On 23.10.2009 16:33, Anthony Minessale wrote: