<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 30/06/2021 à 16:10, Ryan Press a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CABx3TkW=whyhG_nUS9dPuE9OgLtj+6tq+=iKj+A-Q6zT=80oYw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">[...]<br>
[from-internal-custom] ; Doorbell video bridge
<div>exten => doorbell_rtsp,1,Answer() same =>
n,RTSP-SIP(<a class="moz-txt-link-freetext" href="rtsp://">rtsp://</a><a
href="http://admin:12345@192.168.24.53:554/live/sub,0,asterisk,5060"
target="_blank" moz-do-not-send="true">admin:12345@192.168.24.53:554/live/sub,0,asterisk,5060</a>)</div>
<div>; Doorbell combined video/audio incoming</div>
<div>exten => 762,1,Answer() same =>
n,Page(PJSIP/805&Local/doorbell_rtsp@from-internal-custom,qd)<br>
<br>
The problem comes when I try to get the door intercom to call
an extension. Because the calling device (door intercom) does
not include video, the video capability is not added to the
ConfBridge and therefore when I bridge in the RTSP-SIP channel
it does not connect. When I tried to use Originate it had the
same problem, no video codec was offered.<br>
</div>
<div><br>
</div>
<div>Is there some way I can create a ConfBridge and force a
video codec? Or use Originate with a video codec?</div>
<div><br>
</div>
<div>I see that Asterisk has included Streams for a while now.
Maybe this is the best way forward but I'm not sure this is
something I can easily configure without writing a bunch of
new code.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Ryan</div>
<div><br>
</div>
</div>
</blockquote>
<p>Hello,</p>
<p>Did you try to use ARI's "originate" function with the "format"
parameter containing a video codec ?<br>
</p>
</body>
</html>