Subject: Re: [h323plus] OpenMCU Codec issues
Hi Simon
About plugins, I'm searching source code of PPluginManager
algorithm an I found that they match the Environment Var/Directory
Name with the suffix of the plugins file names. So if you use
PTLIBPLUINGSDIR the source automatic append '_ptplugin' (the default
suffix) to the file to be loaded.
I don't know the linux code, but the default Windows compilation
put '_pwplugin' suffix on files of plugins solution (if loaded source
from H323Plus CVS), so you need use PWLIBPLUGINSDIR env. var.
2009/11/17 Josh Barth <
jbarth@buttechc.com>:
> So I still have the same issue, I have set the PTLIBPLUGINDIR env var.
>
>
>
> Should the structure then be /usr/local/lib/ptlib and then each of the
> libraries? Or should they exist in codecs/ or codecs/audio/ and
> codecs/video/
>
>
>
> I am right in thinking once these are placed properly OpenMCU should pick
> them up? I don’t have to place them, then recompile OpenMCU do I?
>
>
>
> Thanks very much,
>
> Josh
>
>
>
>
>
> From:
h323plus-bounces@lists.packetizer.com
> [mailto:
h323plus-bounces@lists.packetizer.com] On Behalf Of Simon Horne
> Sent: Tuesday, November 17, 2009 5:17 PM
> To:
h323plus@lists.packetizer.com
> Subject: Re: [h323plus] OpenMCU Codec issues
>
>
>
> Josh
>
>
>
> The default directory for plugins should be /usr/lib/ptlib unless you set
> the environment variable PTLIBPLUGINDIR to point to your plugin directory.
>
>
>
> Simon
>
>
>
> ________________________________
>
> From:
h323plus-bounces@lists.packetizer.com
> [mailto:
h323plus-bounces@lists.packetizer.com] On Behalf Of Josh Barth
> Sent: Wednesday, 18 November 2009 9:45 AM
> To: '
h323plus@lists.packetizer.com'
> Subject: [h323plus] OpenMCU Codec issues
>
> I have the ptlib, h323plus, plugins, and openmcu from
h323plus.org
>
>
>
> I built each successfully, but I am not having any luck getting the
> additional codecs loaded when I launch OpenMCU, all I get is G.711.
>
>
>
> Did I not build something right? In order I built, ptlib, h323plus, openmcu,
> plugins
>
>
>
> Where should the codecs be located? (they are in /usr/local/lib/pwlib)
>
>
>
> These are modular correct, I don’t need to re-compile h323plus or OpenMCU?
>
>
>
> Here is my trace:
>
>
>
> 0:00.081 OpenMCU Version 2.2.5 by H323plus on
> Unix Linux (2.6.26-2-sparc64-sparc64) at 2009/11/17 14:43:29.321
>
> 0:00.082 OpenMCU PWLib File handle high water mark
> set: 15 Thread unblock pipe
>
> 0:00.082 OpenMCU PWLib Created thread 0x162c78 H323
> Listener:%0x
>
> 0:00.083 OpenMCU PWLib File handle high water mark
> set: 16 PTCPSocket
>
> 0:00.083 OpenMCU H323 Started listener
> Listener[ip$*:1720]
>
> 0:00.084 OpenMCU PWLib Thread high water mark set:
> 6
>
> 0:00.085 OpenMCU H323 FindCapability:
> "G.711-ALaw-64k{sw}"
>
> 0:00.085 OpenMCU H323 Added capability:
> G.711-ALaw-64k <1>
>
> 0:00.085 OpenMCU H323 FindCapability:
> "G.711-uLaw-64k{sw}"
>
> 0:00.086 OpenMCU H323 Added capability:
> G.711-uLaw-64k <2>
>
> 0:00.086 OpenMCU H323 FindCapability:
> "G.711-ALaw-64k{sw}"
>
> 0:00.086 OpenMCU H323 FindCapability:
> "G.711-uLaw-64k{sw}"
>
> 0:00.086 OpenMCU H323 FindCapability:
> "G.711-ALaw-64k{sw}"
>
> 0:00.086 OpenMCU H323 FindCapability:
> "G.711-uLaw-64k{sw}"
>
> 0:00.087 OpenMCU H323 FindCapability:
> "G.711-ALaw-64k{sw}"
>
> 0:00.087 OpenMCU H323 FindCapability:
> "G.711-uLaw-64k{sw}"
>
> 0:00.087 OpenMCU H323 FindCapability:
> "G.711-ALaw-64k{sw}"
>
> 0:00.087 OpenMCU H323 FindCapability:
> "G.711-uLaw-64k{sw}"
>
> 0:00.087 OpenMCU EXT No Extended Capabilities
> found to load
>
> 0:00.088 OpenMCU H323 FindCapability: "*-QCIF*"
>
> 0:00.088 OpenMCU H323 FindCapability: "*-SQCIF*"
>
> 0:00.088 OpenMCU H323 Added capability:
> UserInput/hookflash <3>
>
> 0:00.088 OpenMCU H323 Added capability:
> UserInput/basicString <4>
>
> 0:00.088 OpenMCU H323 Added capability:
> UserInput/dtmf <5>
>
> 0:00.089 OpenMCU H323 Added capability:
> UserInput/RFC2833 <6>
>
> 0:00.089 OpenMCU H323 Added capability:
> UserInput/Navigation <7>
>
> 0:00.089 OpenMCU H323 Added capability:
> UserInput/Softkey <8>
>
> 0:00.089 OpenMCU H323 Added capability:
> UserInput/PointDevice <9>
>
> 0:00.089 OpenMCU H323 Added capability:
> UserInput/Modal <10>
>
> 0:00.089 OpenMCU MCU Codecs (in preference
> order):
>
> Table:
>
> G.711-ALaw-64k <1>
>
> G.711-uLaw-64k <2>
>
> UserInput/hookflash <3>
>
> UserInput/basicString <4>
>
> UserInput/dtmf <5>
>
> UserInput/RFC2833 <6>
>
> UserInput/Navigation <7>
>
> UserInput/Softkey <8>
>
> UserInput/PointDevice <9>
>
> UserInput/Modal <10>
>
> Set:
>
> 0:
>
> 0:
>
> G.711-ALaw-64k <1>
>
> G.711-uLaw-64k <2>
>
> 1:
>
> 2:
>
> UserInput/hookflash <3>
>
> UserInput/basicString <4>
>
> UserInput/dtmf <5>
>
> UserInput/RFC2833 <6>
>
> UserInput/Navigation <7>
>
> UserInput/Softkey <8>
>
> UserInput/PointDevice <9>
>
> UserInput/Modal <10>
>
>
>
> 0:00.094 OpenMCU PWLib File handle high water mark
> set: 17 PTCPSocket
>
> 0:00.095 OpenMCU PWLib File handle high water mark
> set: 19 Thread unblock pipe
>
> 0:00.095 OpenMCU PWLib Created thread 0x168620 HTTP
> Service
>
> 0:00.095 H323 Listener:f6f8bb90 PWLib Started thread 0x162c78 H323
> Listener:f6f8bb90
>
> 0:00.095 H323 Listener:f6f8bb90 H323 Awaiting TCP connections on
> port 1720
>
> 0:00.095 H323 Listener:f6f8bb90 TCP Waiting on socket accept on
> ip$*:1720
>
>
--
-----
Jogue RPG, alimente o lado criativo!