UnRegister codec

[GoogleCodeExporter]

What steps will reproduce the problem?
1.build doubango
2.build telepresence
3.

What is the expected output? What do you see instead?

From doubango config.log, required video/audio codecs has been seleceted, which 
should be expected be supported and registered when running telelpresence.

telepresence report all required codec are 'unregister codec'.

What version of the product are you using? On what operating system?

telepresence revision : 140
doubango revision : 1116
operating system : CentOS 64bit ver6.5

Please provide any additional information below.

telepresence server log, and cfg file are uploaded as attachment.

Original issue reported on code.google.com by andrewm...@gmail.com on 17 Jun 2014 at 7:35

Attachments:

• config.log
• telepresence.cfg

[GoogleCodeExporter]

telepresence log 

Original comment by andrewm...@gmail.com on 17 Jun 2014 at 7:36

Attachments:

• putty.log

[GoogleCodeExporter]

The codec are registered later but there is no logs.

Original comment by boss...@yahoo.fr on 17 Jun 2014 at 12:05

• Changed state: Invalid

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I get the following logs about codec, when running telepresence, and calling 
the function of 'tdav_codec_set_priority()' in OTEngine::setCodecs().

*INFO: UnRegister codec: PCMA, G.711a codec (native)
*INFO: UnRegister codec: PCMU, G.711u codec (native)
*INFO: UnRegister codec: opus, opus Codec
*INFO: UnRegister codec: VP8, VP8 codec (libvpx)
*INFO: UnRegister codec: H264, H264 Base Profile (FFmpeg, x264)
*INFO: UnRegister codec: H264, H264 Main Profile (FFmpeg, x264)

why does telepresence report 'unregister codec'? The above logs seem all codecs 
are not registered.

Original comment by andrewm...@gmail.com on 18 Jun 2014 at 5:17

[GoogleCodeExporter]

they are unregistered, sorted then registered. There are no logs saying they 
are registered again.
Don't really understand why you're focussing on these INFO logs. If all codecs 
were unregistered it'd be impossible to make or receive calls. Do you have such 
issue?
unregister: 
https://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyMEDIA
/src/tmedia_codec.c?r=1062#292
register: 
https://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinyMEDIA
/src/tmedia_codec.c?r=1062#299

Original comment by boss...@yahoo.fr on 18 Jun 2014 at 5:35

[GoogleCodeExporter]

I build telepresence with doubango, and call the bridge from telepresence via 
wetrtc client. Webrtc client is able to connect with telepresence, but fails to 
proceed further, and reports 'transport error'. Therefore, I review the source 
code of telepresence and doubango in terms of application log.

below is the log about webrtc client trying to connect the bridge of 
telepresence:

Upgrade: websocket
Connection: Upgrade
Host: 192.168.5.100:20060
Origin: http://conf-call.org
Sec-WebSocket-Protocol: sip
Pragma: no-cache
Cache-Control: no-cache
Sec-WebSocket-Key: R9bmr52P7MdcfTkKKMuKqQ==
Sec-WebSocket-Version: 13
Sec-WebSocket-Extensions: x-webkit-deflate-frame
User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like 
Gecko) Chrome/29.0.1547.65 Safari/537.36

Original comment by andrewm...@gmail.com on 18 Jun 2014 at 7:14

[GoogleCodeExporter]

I review the source code you point out. The function of 
'tmedia_codec_plugin_register_2()' is to remove dupulicated codec_plugin and to 
insert it the right priority position. I have no problem with register codec. 
Thanks for your help.

Original comment by andrewm...@gmail.com on 18 Jun 2014 at 8:08