<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 06/10/2021 à 14:35, Joshua C. Colp a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAM0A2Z3NkbbtQL=bMReqAL0-wwEZ-ZgtBETxo0ix7xx9VEp+Cw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Wed, Oct 6, 2021 at 6:54 AM Jean Aunis <<a
href="mailto:jean.aunis@prescom.fr" moz-do-not-send="true">jean.aunis@prescom.fr</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
I have a question regarding the use of a framehook in
bridge_native_rtp.<br>
<br>
The framehook is used to redirect RTP streams when a hold,
unhold or RTP <br>
update is detected.<br>
<br>
But what's the reason for doing this in a framehook ? <br>
</blockquote>
</div>
</div>
</blockquote>
[...]<br>
<blockquote type="cite"
cite="mid:CAM0A2Z3NkbbtQL=bMReqAL0-wwEZ-ZgtBETxo0ix7xx9VEp+Cw@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>I don't remember specific reasoning. It may or may not
work as needed there.</div>
</div>
</div>
</blockquote>
<p>[...]</p>
If it's of use for anybody, I think I've got the answer: that's
because HOLD and UNHOLD frames may be written directly to the
destination channel instead of going through the bridge. For example
when using hold/unhold ARI calls.<br>
</body>
</html>