<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Joshua,<br>
<br>
I'll give it a try at ttps://issues.asterisk.org/jira
<br>
and I hope my English is <span id="result_box" class="short_text"
lang="en"><span class="hps">good enough</span></span> to explain
the problem. ;-)<br>
<br>
wow ... <span id="result_box" class="short_text" lang="en"><span
class="hps">early</span> <span class="hps">bird it is </span></span>03:36
(PDT) in the morning at your place <br>
<br>
Thanks!<br>
<br>
Rainer<br>
<br>
<br>
Am 07.05.2014 12:36, schrieb Joshua Colp:<br>
</div>
<blockquote cite="mid:536A0CA6.9020008@digium.com" type="cite">Rainer
Piper wrote:
<br>
<blockquote type="cite">perhaps a silly question ...
<br>
<br>
if a channel switches from simple_bridge to native_bridge ... is
the
<br>
channel switching to direct_media between the endpoints ?
<br>
<br>
if so, why doesn't turn direct_media = no and
<br>
disable_direct_media_on_nat = yes switching to native_bridge off
?
<br>
</blockquote>
<br>
The bridge_native_rtp module can actually "native bridge" in two
ways:
<br>
<br>
1. Media directly between both sides
<br>
2. Media within the RTP stack
<br>
<br>
Even with NAT #2 can still operate fine as media still goes
through Asterisk, just not as much.
<br>
<br>
As for your issue I would suggest you get a complete console log
output with debug and create an issue[1] as this sounds like a
bug.
<br>
<br>
Cheers,
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://issues.asterisk.org/jira">https://issues.asterisk.org/jira</a>
<br>
<br>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<b>Rainer Piper</b>
<br>
Integration engineer
<br>
Koeslinstr. 56
<br>
53123 BONN <br>
GERMANY
<br>
Phone: +49 228 97167161</div>
</body>
</html>