INFO-Messages: Send_display in pre_answer state doesnt work anymore
-----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-----
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>wrote:
-----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 II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
-----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:
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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32)
iD8DBQFK5bEO4tZeNddg3dwRAkycAKCg61dUy1jkmzauQUDliqYw81aA5ACgmeim hayGIQk5KlRN8edZGLom1mQ= =a5QJ -----END PGP SIGNATURE-----
participants (2)
-
Anthony Minessale
-
Helmut Kuper