channels in originate were not checking for private events.
now they should but if send them commands to do crazy stuff like play a file while they are
in the middle of originating there could be ill side effects (e.g. play file before media was established etc which could cause the call to abort)
btw you can send
call-command: hangup
hangup-cause: normal_clearing
in place of
call-command: execute
execute-app-name: hangup
execute-app-arg: normal_clearing
> you would get a hangup event in either case.yes, you are right. we just tested and saw that. the reason for
sendmsg hangup, was the sometimes useful event-lock.
it works with api uuid_kill as we wanted. but with sendmsg hangup it
still does not work. shouldn't sendmsg hangup work like uuid_kill
here? how useful could it be, to let it ring, when the hangup was
already sent and is immediately executed when the anser is sent?
#2 now works perfectly. thanks for the great support!
_______________________________________________
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