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
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
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
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!
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 dont 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
Marcos Yes sorry the PWLIBPLUGINDIR environmental variable should be used. Make sure you remove the PTLIBPLUGINDIR variable as it has precedence. Simon -----Original Message----- From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Marcos Fábio Jardini Sent: Wednesday, 18 November 2009 10:43 PM To: Josh Barth Cc: h323plus@lists.packetizer.com 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>: 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 dont 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!
I used the PWPLUGINSDIR env. var. and it seems to work.....but. I only get H.261 for video and do not see it load H.263. I have the plugins in /usr/lib/pwlib and I have libavcodec.so there and avcodec symlinked to it. I also get complaints from OpenMCU, "failed to compile regex 2" when trying to access the web console. Josh ________________________________________ From: Marcos Fábio Jardini [marcos.f.jardini@gmail.com] Sent: Wednesday, November 18, 2009 5:43 AM To: Josh Barth Cc: h323plus@lists.packetizer.com 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!
HI Josh, The H.263 plugin on h323plus.com is compatible with ffmpeg 0.4.7 version. You can get the precompiled lib for it from: http://www.voxgratia.org/bin/libavcodec-0.4.7-linux.bin.tar.gz Put this so in $PWLIBPLUGINDIR with name avcodec. Thanks, -- Prasad 2009/11/19 Josh Barth <jbarth@buttechc.com>
I used the PWPLUGINSDIR env. var. and it seems to work.....but.
I only get H.261 for video and do not see it load H.263.
I have the plugins in /usr/lib/pwlib and I have libavcodec.so there and avcodec symlinked to it.
I also get complaints from OpenMCU, "failed to compile regex 2" when trying to access the web console.
Josh ________________________________________ From: Marcos Fábio Jardini [marcos.f.jardini@gmail.com] Sent: Wednesday, November 18, 2009 5:43 AM To: Josh Barth Cc: h323plus@lists.packetizer.com 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.
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
2009/11/17 Josh Barth <jbarth@buttechc.com>: 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!
I copied the libavcodec.so from tarball to $PWLIBPLUGINDIR/avcodec, but it still doesn't appear. Here is my $PWLIBPLUGINDIR: drwxr-xr-x 5 root root 4096 2009-11-19 08:57 . drwxr-xr-x 123 root root 36864 2009-11-17 17:21 .. drwxr-xr-x 3 root root 4096 2009-08-03 12:31 1.10.10 drwxr-xr-x 3 root root 4096 2009-11-16 11:05 1.11.2 -rwxr-xr-x 1 root root 1773160 2009-11-19 08:57 avcodec -rw-r--r-- 1 root root 47060 2004-04-22 06:27 avcodec.h drwxr-xr-x 6 root root 4096 2009-11-17 14:40 codecs -rw-r--r-- 1 root root 28985 2004-04-22 06:28 common.h -rwxr-xr-x 1 root root 4311548 2009-11-19 08:56 libavcodec.so And the trace Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> G.726-16k{sw} <3> G.726-24k{sw} <4> G.726-32k{sw} <5> G.726-40k{sw} <6> GSM-06.10{sw} <7> GSM-AMR{sw} <8> LPC-10{sw} <9> MS-GSM{sw} <10> MS-IMA-ADPCM{sw} <11> SpeexIETFNarrow-11k{sw} <12> SpeexIETFNarrow-15k{sw} <13> SpeexIETFNarrow-18.2k{sw} <14> SpeexIETFNarrow-24.6k{sw} <15> SpeexIETFNarrow-5.95k{sw} <16> SpeexIETFNarrow-8k{sw} <17> SpeexIETFWide-20.6k{sw} <18> SpeexWNarrow-8k{sw} <19> SpeexWide-20.6k{sw} <20> iLBC-13k3{sw} <21> iLBC-15k2{sw} <22> 1: H.261-CIF{sw} <23> 2: UserInput/hookflash <24> UserInput/basicString <25> UserInput/dtmf <26> UserInput/RFC2833 <27> UserInput/Navigation <28> UserInput/Softkey <29> UserInput/PointDevice <30> UserInput/Modal <31> From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Prasad Mohire Sent: Thursday, November 19, 2009 12:15 AM To: h323plus@lists.packetizer.com Subject: Re: [h323plus] OpenMCU Codec issues HI Josh, The H.263 plugin on h323plus.com<http://h323plus.com/> is compatible with ffmpeg 0.4.7 version. You can get the precompiled lib for it from: http://www.voxgratia.org/bin/libavcodec-0.4.7-linux.bin.tar.gz Put this so in $PWLIBPLUGINDIR with name avcodec. Thanks, -- Prasad 2009/11/19 Josh Barth <jbarth@buttechc.com<mailto:jbarth@buttechc.com>> I used the PWPLUGINSDIR env. var. and it seems to work.....but. I only get H.261 for video and do not see it load H.263. I have the plugins in /usr/lib/pwlib and I have libavcodec.so there and avcodec symlinked to it. I also get complaints from OpenMCU, "failed to compile regex 2" when trying to access the web console. Josh ________________________________________ From: Marcos Fábio Jardini [marcos.f.jardini@gmail.com<mailto:marcos.f.jardini@gmail.com>] Sent: Wednesday, November 18, 2009 5:43 AM To: Josh Barth Cc: h323plus@lists.packetizer.com<mailto:h323plus@lists.packetizer.com> 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<mailto: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> [mailto: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<mailto: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> [mailto: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<mailto:h323plus@lists.packetizer.com>' Subject: [h323plus] OpenMCU Codec issues
I have the ptlib, h323plus, plugins, and openmcu from h323plus.org<http://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!
Actually I just realized there is a reason: "error loading /usr/lib/pwlib/avcodec - /usr/lib/pwlib/avcodec: ELF file data encoding not big-endian" So I assume this means I need to compile the library myself? If so what is the process there get the 0.4.7 source and compile and place it? Or am I overlooking some details? What is the deal with h263-ffmpeg_video_pwplugin.so included with the plugins tarball from the h323plus source page? How are these different? Thanks, Josh From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Josh Barth Sent: Thursday, November 19, 2009 9:28 AM To: 'Prasad Mohire'; 'h323plus@lists.packetizer.com' Subject: Re: [h323plus] OpenMCU Codec issues I copied the libavcodec.so from tarball to $PWLIBPLUGINDIR/avcodec, but it still doesn't appear. Here is my $PWLIBPLUGINDIR: drwxr-xr-x 5 root root 4096 2009-11-19 08:57 . drwxr-xr-x 123 root root 36864 2009-11-17 17:21 .. drwxr-xr-x 3 root root 4096 2009-08-03 12:31 1.10.10 drwxr-xr-x 3 root root 4096 2009-11-16 11:05 1.11.2 -rwxr-xr-x 1 root root 1773160 2009-11-19 08:57 avcodec -rw-r--r-- 1 root root 47060 2004-04-22 06:27 avcodec.h drwxr-xr-x 6 root root 4096 2009-11-17 14:40 codecs -rw-r--r-- 1 root root 28985 2004-04-22 06:28 common.h -rwxr-xr-x 1 root root 4311548 2009-11-19 08:56 libavcodec.so And the trace Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> G.726-16k{sw} <3> G.726-24k{sw} <4> G.726-32k{sw} <5> G.726-40k{sw} <6> GSM-06.10{sw} <7> GSM-AMR{sw} <8> LPC-10{sw} <9> MS-GSM{sw} <10> MS-IMA-ADPCM{sw} <11> SpeexIETFNarrow-11k{sw} <12> SpeexIETFNarrow-15k{sw} <13> SpeexIETFNarrow-18.2k{sw} <14> SpeexIETFNarrow-24.6k{sw} <15> SpeexIETFNarrow-5.95k{sw} <16> SpeexIETFNarrow-8k{sw} <17> SpeexIETFWide-20.6k{sw} <18> SpeexWNarrow-8k{sw} <19> SpeexWide-20.6k{sw} <20> iLBC-13k3{sw} <21> iLBC-15k2{sw} <22> 1: H.261-CIF{sw} <23> 2: UserInput/hookflash <24> UserInput/basicString <25> UserInput/dtmf <26> UserInput/RFC2833 <27> UserInput/Navigation <28> UserInput/Softkey <29> UserInput/PointDevice <30> UserInput/Modal <31> From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Prasad Mohire Sent: Thursday, November 19, 2009 12:15 AM To: h323plus@lists.packetizer.com Subject: Re: [h323plus] OpenMCU Codec issues HI Josh, The H.263 plugin on h323plus.com<http://h323plus.com/> is compatible with ffmpeg 0.4.7 version. You can get the precompiled lib for it from: http://www.voxgratia.org/bin/libavcodec-0.4.7-linux.bin.tar.gz Put this so in $PWLIBPLUGINDIR with name avcodec. Thanks, -- Prasad 2009/11/19 Josh Barth <jbarth@buttechc.com<mailto:jbarth@buttechc.com>> I used the PWPLUGINSDIR env. var. and it seems to work.....but. I only get H.261 for video and do not see it load H.263. I have the plugins in /usr/lib/pwlib and I have libavcodec.so there and avcodec symlinked to it. I also get complaints from OpenMCU, "failed to compile regex 2" when trying to access the web console. Josh ________________________________________ From: Marcos Fábio Jardini [marcos.f.jardini@gmail.com<mailto:marcos.f.jardini@gmail.com>] Sent: Wednesday, November 18, 2009 5:43 AM To: Josh Barth Cc: h323plus@lists.packetizer.com<mailto:h323plus@lists.packetizer.com> 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<mailto: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> [mailto: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<mailto: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> [mailto: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<mailto:h323plus@lists.packetizer.com>' Subject: [h323plus] OpenMCU Codec issues
I have the ptlib, h323plus, plugins, and openmcu from h323plus.org<http://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!
Hi The .so, (and .dll) that comes inside 'plugins' from SVN are compiled for x86 (little-endian). If you are using a diferent CPU architecture you need find 'how' and 'if' the old avcodec compile to your platform. I'll put bellow the VoxGratia old site about avcodec. Basically need download the source, apply a patch and recompile. http://www.voxgratia.org/docs/h263_codec.html 2009/11/19 Josh Barth <jbarth@buttechc.com>:
Actually I just realized there is a reason:
“error loading /usr/lib/pwlib/avcodec - /usr/lib/pwlib/avcodec: ELF file data encoding not big-endian”
So I assume this means I need to compile the library myself? If so what is the process there get the 0.4.7 source and compile and place it? Or am I overlooking some details?
What is the deal with h263-ffmpeg_video_pwplugin.so included with the plugins tarball from the h323plus source page? How are these different?
Thanks,
Josh
From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Josh Barth Sent: Thursday, November 19, 2009 9:28 AM To: 'Prasad Mohire'; 'h323plus@lists.packetizer.com'
Subject: Re: [h323plus] OpenMCU Codec issues
I copied the libavcodec.so from tarball to $PWLIBPLUGINDIR/avcodec, but it still doesn’t appear.
Here is my $PWLIBPLUGINDIR:
drwxr-xr-x 5 root root 4096 2009-11-19 08:57 .
drwxr-xr-x 123 root root 36864 2009-11-17 17:21 ..
drwxr-xr-x 3 root root 4096 2009-08-03 12:31 1.10.10
drwxr-xr-x 3 root root 4096 2009-11-16 11:05 1.11.2
-rwxr-xr-x 1 root root 1773160 2009-11-19 08:57 avcodec
-rw-r--r-- 1 root root 47060 2004-04-22 06:27 avcodec.h
drwxr-xr-x 6 root root 4096 2009-11-17 14:40 codecs
-rw-r--r-- 1 root root 28985 2004-04-22 06:28 common.h
-rwxr-xr-x 1 root root 4311548 2009-11-19 08:56 libavcodec.so
And the trace
Set:
0:
0:
G.711-ALaw-64k <1>
G.711-uLaw-64k <2>
G.726-16k{sw} <3>
G.726-24k{sw} <4>
G.726-32k{sw} <5>
G.726-40k{sw} <6>
GSM-06.10{sw} <7>
GSM-AMR{sw} <8>
LPC-10{sw} <9>
MS-GSM{sw} <10>
MS-IMA-ADPCM{sw} <11>
SpeexIETFNarrow-11k{sw} <12>
SpeexIETFNarrow-15k{sw} <13>
SpeexIETFNarrow-18.2k{sw} <14>
SpeexIETFNarrow-24.6k{sw} <15>
SpeexIETFNarrow-5.95k{sw} <16>
SpeexIETFNarrow-8k{sw} <17>
SpeexIETFWide-20.6k{sw} <18>
SpeexWNarrow-8k{sw} <19>
SpeexWide-20.6k{sw} <20>
iLBC-13k3{sw} <21>
iLBC-15k2{sw} <22>
1:
H.261-CIF{sw} <23>
2:
UserInput/hookflash <24>
UserInput/basicString <25>
UserInput/dtmf <26>
UserInput/RFC2833 <27>
UserInput/Navigation <28>
UserInput/Softkey <29>
UserInput/PointDevice <30>
UserInput/Modal <31>
From: h323plus-bounces@lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Prasad Mohire Sent: Thursday, November 19, 2009 12:15 AM To: h323plus@lists.packetizer.com Subject: Re: [h323plus] OpenMCU Codec issues
HI Josh,
The H.263 plugin on h323plus.com is compatible with ffmpeg 0.4.7 version.
You can get the precompiled lib for it from:
http://www.voxgratia.org/bin/libavcodec-0.4.7-linux.bin.tar.gz
Put this so in $PWLIBPLUGINDIR with name avcodec.
Thanks, -- Prasad
2009/11/19 Josh Barth <jbarth@buttechc.com>
I used the PWPLUGINSDIR env. var. and it seems to work.....but.
I only get H.261 for video and do not see it load H.263.
I have the plugins in /usr/lib/pwlib and I have libavcodec.so there and avcodec symlinked to it.
I also get complaints from OpenMCU, "failed to compile regex 2" when trying to access the web console.
Josh ________________________________________ From: Marcos Fábio Jardini [marcos.f.jardini@gmail.com] Sent: Wednesday, November 18, 2009 5:43 AM To: Josh Barth Cc: h323plus@lists.packetizer.com
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!
-- ----- Jogue RPG, alimente o lado criativo!
participants (4)
-
Josh Barth -
Marcos Fábio Jardini -
Prasad Mohire -
Simon Horne