On Dec 9, 2008, at 6:52 AM, Jan Kubr wrote:
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
What is the difference this makes? Just curious because I've been using the latter as well.
we just tested you changes and it works the opposite way it should.
this means: when we do not send an uuid, we get an an error (Reply-Text => -ERR invalid session id []). if we send a wrong/not existing uuid, the command will be executed on the inbound uuid.
This hasn't been changed, has it? On the latest trunk, if I don't pass the uuid, I get "-ERR invalid session id". I can always pass it explicitly though, so no big deal.
Jan Kubr
We did have confirmation from others that this is working properly now. Can you please make sure you are on current trunk and re-test this. Mike