linphone-developers
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Linphone-developers] Loading another H264 decoder profile

From: Giacomo Furlan
Subject: Re: [Linphone-developers] Loading another H264 decoder profile
Date: Mon, 12 Oct 2015 14:23:58 +0200
Further findings:

I've added this line: ms_message("%s - %s", m->mime_type, refpt->mime_type); in submodules/linphone/coreapi/offeranswer.c : 136

The strange thing is that the result does not have H264 at all: this is the log.

10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: opus - PCMU
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: G729A - PCMU
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR - PCMU
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR-WB - PCMU
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: opus - PCMA
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: G729A - PCMA
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR - PCMA
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR-WB - PCMA
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: opus - telephone-event
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: G729A - telephone-event
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR - telephone-event
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR-WB - telephone-event
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: opus - H264
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: G729A - H264
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR - H264
10-12 14:15:33.108 16928-17011/com.be_ssd.sipinterphone I/SIPManager: AMR-WB - H264

There are 3 audio codecs and 1 video, so the cycle is repeated 3 times. Surprisingly PCMU, PCMA and telephone-event are not recognized, but nonetheless the audio stream works. For H264 though it simply will write "No match for H264" and prevent the video streaming to be initialised.

Giacomo Furlan
Software developer
Software Solutions Designs

2015-10-12 13:57 GMT+02:00 Giacomo Furlan <address@hidden>:
OK, now the "ms264" mediastream2's plugin is loaded instead of the OpenH264 one.

The problem persists though. This is the log, maybe it may be useful to you?

Thank you very much for any hint / suggestion / whatever.

10-12 13:54:25.098 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: ending recv background task with id=[1d50051a].
10-12 13:54:25.098 24938-25149/com.be_ssd.sipinterphone I/SIPManager: wake_lock_release(): Android wake lock released [ref=0x1d50051a]
10-12 13:54:25.528 24938-25161/com.be_ssd.sipinterphone I/SIPManager: Changing [server] [CANCEL] transaction [0x6af7e290], from state [COMPLETED] to [TERMINATED]
10-12 13:54:25.528 24938-25161/com.be_ssd.sipinterphone I/SIPManager: Server CANCEL transaction [0x6af7e290] terminated
10-12 13:54:25.548 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Changing [server] [INVITE] transaction [0x6c156c48], from state [COMPLETED] to [TERMINATED]
10-12 13:54:25.548 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Server INVITE transaction [0x6c156c48] terminated
10-12 13:54:25.558 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Destroying op [0x6c1fafe8] of type [SalOpCall]
10-12 13:54:28.958 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: keep alive sent to [UDP://192.168.0.201:5060]
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: bellesip_wake_lock_acquire(): Android wake lock acquired [ref=0x1d40051e]
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: starting recv background task with id=[1d40051e].
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: received [793] new bytes from [UDP://192.168.0.201:5060]:
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: INVITE sip:address@hidden SIP/2.0
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Via: SIP/2.0/UDP 192.168.0.201:5060;rport;branch=z9hG4bK522919066
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: From: <sip:address@hidden>;tag=615517005
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: To: <sip:address@hidden>
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Call-ID: 358683571
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: CSeq: 20 INVITE
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Contact: <sip:address@hidden:5060>
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Content-Type: application/sdp
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Max-Forwards: 70
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: User-Agent: DnakeVoip v1.0
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Content-Length:   430
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager:
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: v=0
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: o=dnake 1897841182 1897841182 IN IP4 192.168.0.201
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: s=dnake
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: c=IN IP4 192.168.0.201
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: t=0 0
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: m=audio 6000 RTP/AVP 0 8 101
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=rtpmap:0 PCMU/8000/1
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=rtpmap:8 PCMA/8000/1
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=rtpmap:101 telephone-event/8000/1
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=fmtp:101 0-11
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=sendrecv
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: m=video 6200 RTP/AVP 102
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=rtpmap:102 H264/90000
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=fmtp:102 profile-level-id=4D0029; packetization-mode=1
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=ex_fmtp:102 2CIF=1
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=ex_multicast:102 ip=238.9.0.201; port=6300
10-12 13:54:38.038 24938-25149/com.be_ssd.sipinterphone I/SIPManager: a=sendrecv
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008] [363] bytes parsed
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008] read [430] bytes of body from [192.168.0.201:5060]
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Changing [server] [INVITE] transaction [0x6af7e098], from state [INIT] to [PROCEEDING]
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: message sent to [UDP://192.168.0.201:5060], size: [203] bytes
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: SIP/2.0 100 Trying
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Via: SIP/2.0/UDP 192.168.0.201:5060;rport;branch=z9hG4bK522919066
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: From: <sip:address@hidden>;tag=615517005
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: To: sip:address@hidden
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Call-ID: 358683571
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: CSeq: 20 INVITE
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager:
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: New server dialog [0x6af6ce78] , local tag [], remote tag [615517005]
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: op [0x6a3862d0] : set_or_update_dialog() current=[0x0] new=[0x6af6ce78]
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: new incoming call from [sip:address@hidden] to [sip:address@hidden]
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Found payload PCMU/8000 fmtp=
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Found payload PCMA/8000 fmtp=
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Found payload telephone-event/8000 fmtp=0-11
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Found payload H264/90000 fmtp=profile-level-id=4D0029; packetization-mode=1
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Searching for already_a_call_with_remote_address.
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: New LinphoneCall [0x6af3f3a0] initialized (LinphoneCore version: 3.8.5-710-g68829ae)
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: audio stream index found: 0, updating main audio stream index
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: video stream index found: 1, updating main video stream index
10-12 13:54:38.048 24938-25149/com.be_ssd.sipinterphone I/SIPManager: RtpSession bound to [0.0.0.0] ports [7076] [7077]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Setting DSCP to 46 for MSAudio stream.
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone W/SIPManager: cannot set echo limiter to mode [1] because no volume send
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Equalizer location: hp
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: cannot set noise gate mode to [0] because no volume send
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: RtpSession bound to [0.0.0.0] ports [9078] [9079]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Setting DSCP to 0 for MSVideo stream.
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Don't put video stream on local offer for call [0x6af3f3a0]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Don't put text stream on local offer for call [0x6af3f3a0]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Doing SDP offer/answer process of type incoming
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: No match for H264/90000
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: bellesip_wake_lock_acquire(): Android wake lock acquired [ref=0x1d400526]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Linphone core [0x6a37f378] notifying [show]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Linphone core [0x6a37f378] notifying [display_status]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Starting local ring...
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: speex_lib_ctl init with neon ? 1
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Configuring resampler input with rate=[44100], nchannels=[2]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: MSFilePlayer[0x6c151150]: /data/data/com.be_ssd.sipinterphone/files/lowfreq.wav opened: rate=44100,channel=2
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: configuring resampler output to rate=[44100], nchannels=[2]
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: ms_filter_link: MSFilePlayer:0x6c151150,0-->MSDtmfGen:0x6c1fb018,0
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: ms_filter_link: MSDtmfGen:0x6c1fb018,0-->MSResample:0x6c151230,0
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: ms_filter_link: MSResample:0x6c151230,0-->MSAndroidSndWrite:0x6c1fb070,0
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Initializing speex resampler in mode [voip]
10-12 13:54:38.058 24938-28380/com.be_ssd.sipinterphone I/SIPManager: Priority used: 99
10-12 13:54:38.058 24938-28380/com.be_ssd.sipinterphone I/SIPManager: Ring MSTicker priority increased to maximum.
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone W/SIPManager: Could not set voip=on: err=-38.
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: AudioTrack: min frame count is 5644
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: incStrong(0x6a384298)
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone W/SIPManager: AudioTrack::initCheck() not available assuming OK
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: AudioTrack latency estimated to -1 ms
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Call 0x6af3f3a0: moving from state LinphoneCallIdle to LinphoneCallIncomingReceived
10-12 13:54:38.058 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Call [0x6af3f3a0] acquires both wifi and multicast lock
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone W/SIPManager: No multicast lock configured or not usable for core [0x6a37f378]
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Linphone core [0x6a37f378] notifying [call_state_changed]
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone D/SIPManager: Call state: IncomingReceived (Incoming call)
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: wake_lock_release(): Android wake lock released [ref=0x1d400526]
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Contact has been fixed using proxy
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: message sent to [UDP://192.168.0.201:5060], size: [285] bytes
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: SIP/2.0 180 Ringing
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Via: SIP/2.0/UDP 192.168.0.201:5060;rport;branch=z9hG4bK522919066
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: From: <sip:address@hidden>;tag=615517005
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: To: <sip:address@hidden>;tag=URDzRqn
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Call-ID: 358683571
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: CSeq: 20 INVITE
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: User-Agent: SIPManager/1.0 (belle-sip/1.4.1)
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Supported: outbound
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager:
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: Dialog [0x6af6ce78]: now updated by transaction [0x6af7e098].
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: ending recv background task with id=[1d40051e].
10-12 13:54:38.068 24938-25149/com.be_ssd.sipinterphone I/SIPManager: wake_lock_release(): Android wake lock released [ref=0x1d40051e]
10-12 13:54:38.948 24938-25161/com.be_ssd.sipinterphone I/SIPManager: incoming call ringing for 0 seconds
10-12 13:54:39.948 24938-25161/com.be_ssd.sipinterphone I/SIPManager: incoming call ringing for 1 seconds
10-12 13:54:40.938 24938-25149/com.be_ssd.sipinterphone I/SIPManager: incoming call ringing for 2 seconds
10-12 13:54:41.138 24938-24938/com.be_ssd.sipinterphone I/SIPManager: stop ringing
10-12 13:54:41.138 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Stopping sound playback
10-12 13:54:41.138 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Sound playback stopped
10-12 13:54:41.138 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Sound playback flushed, deleting
10-12 13:54:41.138 24938-24938/com.be_ssd.sipinterphone I/SIPManager: decStrong(0x6a384298)
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone W/SIPManager: Could not set voip=off: err=-38.
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone I/SIPManager: ms_filter_unlink: MSFilePlayer:0x6c151150,0-->MSDtmfGen:0x6c1fb018,0
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone I/SIPManager: ms_filter_unlink: MSDtmfGen:0x6c1fb018,0-->MSResample:0x6c151230,0
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone I/SIPManager: ms_filter_unlink: MSResample:0x6c151230,0-->MSAndroidSndWrite:0x6c1fb070,0
10-12 13:54:41.148 24938-28380/com.be_ssd.sipinterphone I/SIPManager: Ring MSTicker thread exiting
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone I/SIPManager: configuring prefered card sampling rate to [48000]
10-12 13:54:41.148 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Accepting server transaction [0x6af7e098] on op [0x6a3862d0]
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: channel [0x6af1e008]: message sent to [UDP://192.168.0.201:5060], size: [713] bytes
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: SIP/2.0 200 Ok
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Via: SIP/2.0/UDP 192.168.0.201:5060;rport;branch=z9hG4bK522919066
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: From: <sip:address@hidden>;tag=615517005
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: To: <sip:address@hidden>;tag=URDzRqn
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Call-ID: 358683571
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: CSeq: 20 INVITE
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: User-Agent: SIPManager/1.0 (belle-sip/1.4.1)
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Supported: outbound
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Contact: <sip:address@hidden>;+sip.instance="<urn:uuid:bdfaf2c1-1dc9-40d8-a6a1-34a2f250ce8a>"
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Content-Type: application/sdp
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: Content-Length: 191
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager:
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: v=0
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: o=1050 2357 2272 IN IP4 192.168.0.176
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: s=Talk
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: c=IN IP4 192.168.0.176
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: b=AS:380
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: t=0 0
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: m=audio 7076 RTP/AVP 0 8 101
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: a=rtpmap:101 telephone-event/8000
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: m=video 0 RTP/AVP 0
10-12 13:54:41.158 24938-24938/com.be_ssd.sipinterphone I/SIPManager: a=inactive
[...]


Giacomo Furlan
Software developer
Software Solutions Designs

2015-10-12 13:40 GMT+02:00 Giacomo Furlan <address@hidden>:
After further investigation I found out the OpenH264 does not support the Main profile - but x264 does. I'm now making the project with the following flags:

BUILD_OPENH264=0
BUILD_OPENH264_DECODER=0
BUILD_X264=1

Will let you know if something changes.

Thanks

Giacomo Furlan
Software developer
Software Solutions Designs

2015-10-12 12:48 GMT+02:00 Giacomo Furlan <address@hidden>:
Hello again!

I've tried adding manually to submodules/linphone/coreapi/linphonecore.c a different payload type (in particular payload_type_h264 with profile-level-id=4D0029), but when the call is accepted, I still get the following error:

10-12 12:38:03.283 29515-29678/com.be_ssd.sipinterphone I/SIPManager: Found payload H264/90000 fmtp=profile-level-id=4D0029; packetization-mode=1
10-12 12:38:03.293 29515-29678/com.be_ssd.sipinterphone I/SIPManager: No match for H264/90000

I've built the library with BUILD_X264=1, but still I only see that only msopenh264-android plugin is being registered (and not msx264)...

AFAIK the profile-level-id is formed by three words, in this case 4D, 00, 29 (profile_idc: 0x7D, profile-iop: 0x00, level-idc: 0x29). Maybe that combination is not supported by FFMPEG? Or should I register it somewhere else?

Please help me!

Thanks

Giacomo Furlan
Software developer
Software Solutions Designs

2015-10-08 17:14 GMT+02:00 Giacomo Furlan <address@hidden>:
Hello!

I think I found the problem why I can't receive the video: the H264/90000 codec compiled with the relative submodule supports a profile level id different than 4D0029 (which is the one that is used by the other SIP client). I don't really know what this profile id is, and thus I don't know how much effort it would take to support it.

Where could I start from?

Thank you.

Giacomo Furlan
Software developer
Software Solutions Designs




reply via email to
[Prev in Thread] Current Thread [Next in Thread]