[Asterisk-video] name of file for video playback

[Borja SIXTO]

Hi Jerry,

How did you generated the h264 file ?

As I said Asterisk use a specific format for the video (Headers and RTP 
data frames).

You need to use mp4asterisk2 to generate the video file or the old 
mp4asterisk provided by the old SIP fontventa project (now Medooze 
http://www.medooze.com/products/asterisk-applications.aspx).

The Ulex.fr company is going to release a tool to generate Asterisk 
video contents.
It is based on the SIP fontventa and some extensions.
It use old projects as : mpeg4ip (release 1.5.0.1), and a old FFmpeg 
snapshot.
For the moment, on an updated Linux server, we had some issues with the 
compilation.
We are trying to commit some changes in order to provide a ready to 
compile sources.

Perhaps you can help us with this task.
If you are ready, contact us directly.

Regards,

Borja SIXTO from ulex.fr


Le 18/12/2016 à 15:34, Jerry Geis a écrit :
> Asterisk 11.25.1 playing with...
> Playback supports these formats.
>
> Supported video codecs
>
>   * H.261 <http://www.voip-info.org/wiki/view/H.261>
>   * H.263 <http://www.voip-info.org/wiki/view/H.263>
>   * H.263p <http://www.voip-info.org/wiki/view/H.263p> (Asterisk 1.4)
>   * H.264 (Asterisk 1.4)
>
> I have a call file I'm using Application: Playback
> Data: /tmp/video
>
> I am using a bria 4 softphone with  h264 enabled.
> The message I see on the console is:
>
> File /tmp/video does not exist in any format
> Unable to open /tmp/video (format ulaw|h263|h264)
>
> In fact I have the file /tmp/video.h264 and is readable by owner group 
> and world.
>
> What am I not doing correctly to get an h264 video file to play?
> Thanks,
>
> Jerry
>
>

-- 
Borja SIXTO (co-founder/manager)

Mail: borja.sixto at ulex.fr
Tel: +33(0)4 28 35 03 44  Ext. 11
Ulex Innovative Systems | 4 rue des Prairies, 38460 St Romain de Jalionas, France
www.ulex.fr

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-video/attachments/20161219/18e10a74/attachment.html>