On Thu, Nov 6, 2008 at 9:54 AM, Dennis
<odermann@googlemail.com> wrote:
hi anthony,
i just pasted the results of 3 unsuccessful tests into the pastebin:
http://pastebin.freeswitch.org/6018
perhaps you could be so nice and have a look at it...
in the first test i made an uuid-bridge over our socket script.
in the second test i made an originate and then an intercept (which
shows an error in the debug log).
in the last test, i entered to uuid-bridge into the cli.
some more information arround the whole thing:
1.) the uuid's must be correct, because we can do everything with the
inbound and the outbound by sending messages with the uuid of the leg,
we want to talk to.
2.) if we make two originates, so that we have 2 outbound legs, we are
able to uuid-bride the two outbound legs with each other. it simply
does not work with the inbound...
thanks
dennis
2008/11/6 Anthony Minessale <anthony.minessale@gmail.com>:
> If that doesn't work one of your uuids are wrong or contains a superfluous
> space or some other character
> You have to understand that the inbound call that uses "socket" is the same
> thing as &park()
> They are both in a park state at that point and there is no functional
> difference.
>
> once both channels are answered and in the park state,
> you have 2 choices and they both work, so watch the console log on debug
> level to find your mistake.
>
> api uuid_bridge <uuid> <other_uuid>
> sendmsg to <uuid> with call-command: execute to execute intercept on
> <other_uuid>
>
> to prove it, just set your script to accept and answer the inbound call then
> make the outbound call and do nothing more.
> Then at the CLI type:
>>console loglevel debug
>>show channels
>
> get the 2 uuid from the output
> and type:
>>uuid_bridge <uuid> <other_uuid>
>
> if this does not work, send me a complete copy of the console output