[asterisk-bugs] [JIRA] (ASTERISK-26871) Record command don't record video on SIP/PJSIP with VP8/h263p

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26871:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Record command don't record video on SIP/PJSIP with VP8/h263p
> -------------------------------------------------------------
>
>                 Key: ASTERISK-26871
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26871
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_record
>    Affects Versions: 14.3.0
>         Environment: Complete test on CentOS 7.3.1701, FreePBX 14.0.1alpha34
> Also tried on FreePBX 10.13.66-64bit, CentOS 6.6, Asterisk 13
>            Reporter: David Bohorquez Tovar
>
> Hi,
> I create two PJSIP extensions,1001 and 1002, and two SIP extensions, 2001 and 2002, like:
> disallow=all
> allow=alaw&vp8
> or allow=alaw&h263p
> or allow=alaw&h263
> To begin the only SIP channel enabled is PJSIP.
> When I call from one extension to the other I can see video on both ends.
> Then I create a small custom dialplan:
> [from-internal-custom]
> exten => 98001,1,Answer()
> exten => 98001,n,Record(/tmp/test.ulaw,,,k)
> exten => 98001,n,Hangup()
> exten => 98002,1,Answer()
> exten => 98002,n,Playback(/tmp/test)
> exten => 98002,n,Hangup()
> Obviously I change the allowed codec according every test I did.
> When I call to record video I can see that mi video in apperance is being sent, but is not recorded and obviously not played back and on the CLI I can see that codec h263p or VP8 are not allowed:
> Console verbose was OFF and is now 3.
> – Executing [98001 at from-internal:1] Answer("PJSIP/1001-0000000a", "") in new stack
> – Executing [98001 at from-internal:2] Record("PJSIP/1001-0000000a", "/tmp/test.ulaw,,,k") in new stack
> – Remote UNIX connection
> – Remote UNIX connection disconnected
> – Playing 'beep.alaw' (language 'en')
> [2017-03-06 07:44:12] WARNING[12470][C-00000007]: file.c:1479 ast_writefile: No such format 'vp8'
> [2017-03-06 07:44:12] WARNING[12470][C-00000007]: file.c:1479 ast_writefile: No such format 'vp8'
> voip11*CLI>
> == Setting global variable 'SIPDOMAIN' to '192.168.77.68'
> – Executing [98001 at from-internal:1] Answer("PJSIP/1001-00000003", "") in new stack
> – Executing [98001 at from-internal:2] Record("PJSIP/1001-00000003", "/tmp/test.ulaw,,,k") in new stack
> – <PJSIP/1001-00000003> Playing 'beep.alaw' (language 'en')
> [2017-03-06 18:39:16] WARNING[13336][C-0000000a]: file.c:1479 ast_writefile: No such format 'h263p'
> [2017-03-06 18:39:16] WARNING[13336][C-0000000a]: file.c:1479 ast_writefile: No such format 'h263p'
> I've discussed this on asterisk community forum and they suggest to report as a bug, on, https://community.asterisk.org/t/reading-a-video-file-and-playback-it-to-a-sip-client-pc/7577/4
> So, in conclusion:
> * Using codec h263 It works but video playback is out of phase.
> * Now if I enable chan SIP the result of the same tests are
>    - On h263, recorded video are out of phase
>    - On h263p, no video is send or received or recorded
>    - On vp8, no video is send or received or recorded
> Please let me know wich other information is needed in order to debug this issue.



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