On 1/5/07, <b class="gmail_sendername">BJ Weschke</b> <<a href="mailto:bweschke@gmail.com">bweschke@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Local channels probably pose the same issue for you as well. This was</blockquote><div><br>I've been using the 1.2 version of the patch, specificly the manager command (as opposed to the dialplan application), for quite some time with Local channels and have not run into problems.
<br><br>I'm not too familiar with chan_agent, is Agent/1 actually a channel like you'd pass to, e.g. the manager redirect command, or a device like you'd pass to the Dial command or add to a queue? Or is it somehow both? With local channels you have what I usually call a device, like
Local/5000@my_content that you can Dial(), which creates two new channels, Local/5000@my_content-aaaa,1 and ,2, one of which is linked to the channel that called Dial, the other starts navigating the dialplan, and can be bridged just fine to some other live channel, or it can Dial a device and get bridged that way. In the end, if there's not a dial string of n, both Local channels masquerade themselves out of the way (producing 3 rename events each, which only through reading the code did I realize were a single entity, and that for my purposes only the middle one mattered).
<br><br>--Tim<br></div><br></div>