[asterisk-bugs] [JIRA] (ASTERISK-27125) PJProject 2.6 fails to playback recorded video

[Richard Mudgett (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=237691#comment-237691 ] 

Richard Mudgett edited comment on ASTERISK-27125 at 7/12/17 12:22 PM:
----------------------------------------------------------------------

This appears to be related to the following: ASTERISK-26554

The underlying issue here is the video playback at 1 frame per second. Seems to qualify as a bug to me. This isn't a configuration issue.


was (Author: johned):
This appears to be related to the following: https://issues.asterisk.org/jira/browse/ASTERISK-26554

The underlying issue here is the video playback at 1 frame per second. Seems to qualify as a bug to me. This isn't a configuration issue.

> PJProject 2.6 fails to playback recorded video
> ----------------------------------------------
>
>                 Key: ASTERISK-27125
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27125
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 14.4.0
>            Reporter: John Edell
>            Severity: Minor
>
> The bundled version of PJProject 2.6 accompanying Asterisk 14.4 fails to playback asterisk recorded h264 video on Cisco E20 or E70 Video Phone devices. The video files display an IVVR menu recorded through asterisk and as such, the functionality of video playback on these devices is paramount. The video only fails to playback on these devices with PJProject version 2.6.
> Video will play on SIP clients such as Linphone but will only play at 1FPS and will display no video at all on the Cisco devices. 
> Video will play on all devices after regression to PJProject 2.5.5 or prior versions, still at the extremely slow rate of only 1 frame per second
> I have looked at the release notes for PJProject 2.6 in comparison to 2.5.5 but can't seem to find where the problem could be, and thus, am reaching out for community assistance.



--
This message was sent by Atlassian JIRA
(v6.2#6252)