[asterisk-bugs] [JIRA] (ASTERISK-28417) SDP negotiation issue

[Alan (JIRA)]

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

Alan edited comment on ASTERISK-28417 at 5/15/19 2:08 PM:
----------------------------------------------------------

Building with external pjproject 2.8 results in pjsip modules that won't load due to missing symbols.

If I try to build with the bundled pjproject I get this error:
...
   [LD] libasteriskpj.o -> libasteriskpj.so.2
/usr/bin/ld:libasteriskpj.exports:1: ignoring invalid character `-' in script
/usr/bin/ld:libasteriskpj.exports:1989: syntax error in VERSION script
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:287: libasteriskpj.so.2] Error 1
make: *** [Makefile:387: main] Error 2

Checking libasteriskpj.exports I see:
-e {
global:
PJSIP_EINVAL_ERR_EXCEPTION;
...

The Makefile rule that produced this is:
libasteriskpj.exports: $(ASTTOPDIR)/$(PJPROJECT_DIR)/pjproject.symbols
        $(ECHO_PREFIX) echo "   [GENERATE] libasteriskpj.exports"
ifeq ($(GNU_LD),1)
        $(CMD_PREFIX) echo -e "{\nglobal:" > libasteriskpj.exports
        $(CMD_PREFIX) sed -r -e "s/.*/$(LINKER_SYMBOL_PREFIX)&;/" $(ASTTOPDIR)/$(PJPROJECT_DIR)/pjproject.symbols >> libasteriskpj.exports
        $(CMD_PREFIX) echo -e "$(LINKER_SYMBOL_PREFIX)ast_pj_init;\n" >> libasteriskpj.exports
        $(CMD_PREFIX) echo -e "local:\n*;\n};" >> libasteriskpj.exports
endif

If I replace echo with /bin/echo, it works.  I'm using GNU make 4.2.1. I think "echo" is a builtin that interprets escape sequences but doesn't take "-e" as a parameter.

Anyway, after fixing this and building with the bundled pjproject, the behavior with the SDP is exactly the same and the video still looks bad.


was (Author: lameventanas):
Building with external pjproject 2.8 results in pjsip modules that won't load due to missing symbols.

If I try to build with the bundled pjproject I get this error:
...
   [LD] libasteriskpj.o -> libasteriskpj.so.2
/usr/bin/ld:libasteriskpj.exports:1: ignoring invalid character `-' in script
/usr/bin/ld:libasteriskpj.exports:1989: syntax error in VERSION script
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:287: libasteriskpj.so.2] Error 1
make: *** [Makefile:387: main] Error 2

Checking libasteriskpj.exports I see:
-e {
global:
PJSIP_EINVAL_ERR_EXCEPTION;
...

The Makefile rule that produced this is:
libasteriskpj.exports: $(ASTTOPDIR)/$(PJPROJECT_DIR)/pjproject.symbols
        $(ECHO_PREFIX) echo "   [GENERATE] libasteriskpj.exports"
ifeq ($(GNU_LD),1)
        $(CMD_PREFIX) echo -e "{\nglobal:" > libasteriskpj.exports
        $(CMD_PREFIX) sed -r -e "s/.*/$(LINKER_SYMBOL_PREFIX)&;/" $(ASTTOPDIR)/$(PJPROJECT_DIR)/pjproject.symbols >> libasteriskpj.exports
        $(CMD_PREFIX) echo -e "$(LINKER_SYMBOL_PREFIX)ast_pj_init;\n" >> libasteriskpj.exports
        $(CMD_PREFIX) echo -e "local:\n*;\n};" >> libasteriskpj.exports
endif

If I replace echo with /bin/echo, the it works.  I'm using GNU make 4.2.1. I think "echo" is a builtin that interprets escape sequences but doesn't take "-e" as a parameter.

Anyway, after fixing this, the behavior with the SDP is exactly the same and the video still looks bad.

> SDP negotiation issue
> ---------------------
>
>                 Key: ASTERISK-28417
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28417
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General, pjproject/pjsip
>    Affects Versions: 13.26.0
>         Environment: Linux
>            Reporter: Alan
>            Assignee: Unassigned
>              Labels: pjsip
>
> I compiled Asterisk 13.26.0 with external pjsip 2.6.
> Asterisk is in the same network as 2 phones:
> extension 11: software phone based on pjproject 2.8
> extension 02: hardware phone Grandstream GXV3240
> When 11 calls 02, audio works well but the video looks terrible.
> extract of SDP from 11 to Asterisk:
> m=video 4014 RTP/AVP 97 96
> c=IN IP4 10.6.0.254
> b=TIAS:256000
> a=rtcp:4015 IN IP4 10.6.0.254
> a=sendrecv
> a=rtpmap:97 H264/90000
> a=fmtp:97 profile-level-id=42e01e; packetization-mode=1
> a=rtpmap:96 H263-1998/90000
> a=fmtp:96 CIF=1;QCIF=1
> a=ssrc:1987299971 cname:719547ff01003a20
> extract of SDP from Asterisk to 02:
> m=video 4014 RTP/AVP 97 96
> c=IN IP4 10.6.0.254
> b=TIAS:256000
> a=rtcp:4015 IN IP4 10.6.0.254
> a=sendrecv
> a=rtpmap:97 H264/90000
> a=fmtp:97 profile-level-id=42e01e; packetization-mode=1
> a=rtpmap:96 H263-1998/90000
> a=fmtp:96 CIF=1;QCIF=1
> a=ssrc:1987299971 cname:719547ff01003a20
> extract of SDP from 02 to Asterisk:
> m=video 5006 RTP/AVP 99
> a=sendrecv
> a=rtcp:5007 IN IP4 10.6.0.244
> a=rtpmap:99 H264/90000
> a=fmtp:99 profile-level-id=42E014; packetization-mode=1
> a=content:main
> a=label:11
> extract of SDP from Asterisk to 11:
> m=video 19562 RTP/AVP 97
> a=rtpmap:97 H264/90000
> a=fmtp:97 packetization-mode=1;profile-level-id=42E01E
> a=sendrecv
> At this point the profile-level-id changed from 2.0 to 3.0.
> Could this be causing the video issue?



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