VoIP Mailing List Archives

[anthony.minessale at g...]

There is a transfer dial plan application also.

There is not really any benefit in blocking the api commands from the dialplan
apart from the potential for a blocking api call to delay the audio stream which
you can do at your own risk and use the sleep application with 0ms to flush the read buffers.

So I guess i can lift that limitation in tree.

see r10790


On Tue, Dec 16, 2008 at 7:07 AM, Carole O. <carole.olivier@enst.fr (carole.olivier@enst.fr)> wrote:

[carole.olivier at enst.fr]

Thanks for this answer.
Just a question so that everything is clear: there is no command to bridge
directly a call and both legs into a conference? We have to transfer the
call to another extension and from there create the conference isn't?

I used the command transfer but I still have a problem. I do the following
and it did not work: in my dialplan I write:
<action application="bind_meta_app" data="1 ab s transfer::3333"/>

The extension 3333 works fine.

However, nothing happens when I press *1.
Do you have an idea where am I wrong?

(A subsidiary question: will both legs be transferred to the extension 3333
or just the one which press *1? is there a way to transfer both together?)


Thanks a lot,
Carole


Anthony Minessale-2 wrote:

[anthony.minessale at g...]

it should work with
<action application="bind_meta_app" data="1 ab s transfer::-both 3333"/>

make sure you have debug log on (press f to see if there are any issues.


On Tue, Dec 16, 2008 at 8:43 AM, Carole O. <carole.olivier@enst.fr (carole.olivier@enst.fr)> wrote:

[carole.olivier at enst.fr]

ok
Thanks a lot,
Carole


Anthony Minessale-2 wrote:

[anthony.minessale at g...]

I said i unblocked the ones in mod_commands

mod_conference was it's own module.
I changed it to work in latest trunk as well.



On Wed, Dec 17, 2008 at 4:15 AM, Carole O. <carole.olivier@enst.fr (carole.olivier@enst.fr)> wrote:

[carole.olivier at enst.fr]

Thanks, this works fine.

But I try to use some other API commands and something goes wrong: I would
like to be able to use the API commands for the conference like lock,
unlock, say, etc... from the dialplan.

I try to add in my dialplan
<action application="bind_meta_app" data="1 a s conference::conf1 lock"/>
but it did not work, I presse F8 and I have got:

2008-12-17 10:47:58 [DEBUG] switch_ivr_async.c:1425 meta_on_dtmf()
sofia/internal/1002@192.168.1.102:2054;line=n7ovvfr7;fs_nat=yes Processing
meta digit '2' [conference::conf1 lock]
2008-12-17 10:47:58 [DEBUG] switch_core_session.c:611
switch_core_session_queue_private_event() Kill
sofia/internal/1002@192.168.1.102:2054;line=n7ovvfr7;fs_nat=yes [BREAK]

You told me that the API commands should not be blocked isn't it? So I do
not understand where I am wrong. Is "bind_meta_app" not supported in
conference?

I have also tried to write directly:
<action application="conference" data="conf1 lock"/>
which also has no effect.

Thanks for your help,
Carole


Anthony Minessale-2 wrote:

[carole.olivier at enst.fr]

(I have just read the post again, I have written <action
application="bind_meta_app" data="1 a s conference::conf1 lock"/> but I
meant <action application="bind_meta_app" data="2 a s conference::conf1
lock"/> please don't pay attention for that, I made the mistake when I have
copied it in the post, not in the configuration.)


Carole O. wrote: