<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 12/20/2016 06:01 PM, Jerry Geis
wrote:<br>
</div>
<blockquote
cite="mid:CABr8-B7a80WxxTtdj6YSufutRoEK4AGgXjca+KH2wV3+C1SnvQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">>Hi Jerry,
> just had a look through the code, and from what I can tell, what
>you're trying to do is not supposed to work, exactly. It appears that
>what Asterisk expects is to be given a filename, such as "myplayback".
>Asterisk will first search for an audio version of the file (like
>myplayback.gsm or myplayback.opus), and open that as an audio stream. If
>that succeeds, it then will also see if there is an accompanying video
>stream (such as myplayback.h264). If it then finds that video, then the
>result will be that Asterisk will play the audio from the audio file and
>the video from the video file.
>What this means is that Asterisk does not properly handle:
>* Files that have audio and video streams contained within
>* Video files without accompanying audio
>This is one of those times where Asterisk's handling of video is not
>user-friendly and in general ass-backwards and terrible. If you have a
>tool that can extract the audio to its own file, then you would be able
>to run your scenario, presumably.
>It would be a welcome addition for Asterisk to be able to open a single
>file containing video and accompanying audio and be able to play those back.
</pre>
<div>Hi Mark,</div>
<div><br>
</div>
<div>Thanks for your reply...</div>
<div>I just tried what you suggested on only got audio. I
created a wav file and put it in the /tmp</div>
<div>directory just like the video.h264 file. So /tmp has
video.h264 and video.wav both.</div>
<div>I then placed the call and only heard the audio from the
wav file. </div>
<div><br>
</div>
<div>I used this for my call file:</div>
<div>
<div>Channel: SIP/2002</div>
<div>Context: testing</div>
<div>Extension: 999999</div>
<div>Priority: 1</div>
<div>Application: Playback</div>
<div>Codecs: h263,h264,vp8,g722,ulaw,alaw,wav<br>
</div>
<div>Data: /tmp/video<br>
</div>
</div>
<div><br>
</div>
<div>My Bria 4 softphone uses the h263 and h264 codecs and of
course wav file audio.</div>
<div>Based on your look of the code did I miss something to
trigger the playing of the video file?</div>
<div>I can extract the audio out to a seperate file - so not a
show stopper for me.</div>
<div><br>
</div>
<div>No errors showed up on the Asterisk CLI when I did my
test.</div>
<div><br>
</div>
<div>Thanks so much,</div>
<div><br>
</div>
<div>Jerry</div>
</div>
</div>
</blockquote>
<br>
I don't see anything obvious in the code that would have prevented
the video from playing back. Unfortunately, the debug from Asterisk
isn't going to be especially helpful here, with one exception. If
you have core debug at level 1 or higher, then when Asterisk detects
the video file, it will say:<br>
<br>
"Ooh, found a video stream, too, format h264"<br>
<br>
If you see that message, that at least means that Asterisk is
finding the video file as expected. If you don't see that, then it's
likely that Asterisk is unaware of the h264 file format type. It may
be that you don't have the format_h264.so module loaded. It may be
that there was an error that occurred when that module was loading,
causing it not to be able to load properly.<br>
<br>
If you are seeing that debug message, it at least means that
Asterisk attempted to play back the video file, but something else
in the process caused the video not to play back as expected. The
first thing you could check is packet captures to see if Asterisk is
even attempting to send video to the softphone. If so, then it's
likely that there is some sort of codec mismatch happening (likely
something in the format parameters). If Asterisk is not even
attempting to send any video, then it likely means that there is
some other issue. It may be a bug, or it may be some erroneous
condition in the environment. Hard to tell yet though.<br>
<br>
Mark Michelson<br>
</body>
</html>