opalvoip-user Mailing List for OpalVOIP (Page 5)
Brought to you by:
csoutheren,
rjongbloed
Menu
▾
▴
opalvoip-user — Discussions relating to OpalVoip user questions
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(4) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(20) |
Feb
(11) |
Mar
(13) |
Apr
(13) |
May
(55) |
Jun
(17) |
Jul
(20) |
Aug
(26) |
Sep
(18) |
Oct
(23) |
Nov
(55) |
Dec
(48) |
| 2009 |
Jan
(89) |
Feb
(37) |
Mar
(50) |
Apr
(30) |
May
(50) |
Jun
(25) |
Jul
(82) |
Aug
(28) |
Sep
(29) |
Oct
(13) |
Nov
(30) |
Dec
(18) |
| 2010 |
Jan
(28) |
Feb
(46) |
Mar
(19) |
Apr
(54) |
May
(28) |
Jun
(15) |
Jul
(15) |
Aug
(28) |
Sep
(52) |
Oct
(27) |
Nov
(38) |
Dec
(5) |
| 2011 |
Jan
(15) |
Feb
(15) |
Mar
(4) |
Apr
(8) |
May
(104) |
Jun
(60) |
Jul
(40) |
Aug
(48) |
Sep
(32) |
Oct
(39) |
Nov
(75) |
Dec
(64) |
| 2012 |
Jan
(15) |
Feb
(31) |
Mar
(63) |
Apr
(17) |
May
(54) |
Jun
(34) |
Jul
(36) |
Aug
(88) |
Sep
(49) |
Oct
(22) |
Nov
(42) |
Dec
(19) |
| 2013 |
Jan
(26) |
Feb
(22) |
Mar
(34) |
Apr
(65) |
May
(79) |
Jun
(11) |
Jul
(78) |
Aug
(23) |
Sep
(32) |
Oct
(20) |
Nov
(42) |
Dec
(16) |
| 2014 |
Jan
(7) |
Feb
(13) |
Mar
(14) |
Apr
(19) |
May
(29) |
Jun
(2) |
Jul
(10) |
Aug
(3) |
Sep
(3) |
Oct
(26) |
Nov
(1) |
Dec
(19) |
| 2015 |
Jan
(3) |
Feb
(14) |
Mar
(4) |
Apr
|
May
(7) |
Jun
|
Jul
(10) |
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
|
Feb
(1) |
Mar
|
Apr
(2) |
May
(8) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
(7) |
Nov
(5) |
Dec
(1) |
| 2017 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(8) |
| 2018 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2019 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pete D. <pe...@le...> - 2015-05-10 14:54:28
|
Here are two links where more work has been done on t38modem: https://github.com/hehol/t38modem https://github.com/PeteDavidson/t38modem On Sun, May 10, 2015 at 9:44 AM, Slava Bendersky <vol...@sk...> wrote: > Hello Robert, > Yes, you right t38modem is require specific opal version. It > opal-24174.tgz > <http://sourceforge.net/projects/t38modem/files/t38modem/2.0.0/opal-24174.tgz/download>. > That the version I have the issue to compile with. > > Slava. > > ------------------------------ > *From: *"Robert Jongbloed" <ro...@vo...> > *To: *"volga629" <vol...@sk...> > *Cc: *"opalvoip-user" <opa...@li...> > *Sent: *Sunday, May 10, 2015 2:58:24 AM > *Subject: *Re: [Opalvoip-user] compile error > > t38modem only works with a very specific version of PTLib/OPAL. > Unfortunately, I cannot tell you what that version is. I hope someone else > on this list know ... > > Robert Jongbloed > *OPAL/OpenH323/PTLib Architect and Co-founder*. > > On 9 May 2015 at 13:57, Slava Bendersky <vol...@sk...> wrote: > >> Hello Everyone, >> Trying compile opal-voip for t38modem and getting the following error, >> any help thank you. >> >> Here build output: >> >> http://fpaste.org/220091/43114356/ >> >> [CC] src/codec/opalwavfile.cxx >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: >> In constructor 'PWAVFilePluginFactory<Factory, >> Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const >> PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, >> unsigned int>, Instance = PWAVFileFormatPlugin]': >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:411: >> instantiated from here >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: >> error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, unsigned >> int>::WorkerBase' >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: >> In constructor 'PWAVFilePluginFactory<Factory, >> Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const >> PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, >> PCaselessString>, Instance = PWAVFileFormatPlugin]': >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:412: >> instantiated from here >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: >> error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, >> PCaselessString>::WorkerBase' >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: >> In constructor 'PWAVFilePluginFactory<Factory, >> Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const >> PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileConverter, >> unsigned int>, Instance = PWAVFileConverterPlugin]': >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:415: >> instantiated from here >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: >> error: 'isDynamic' is not a member of 'PFactory<PWAVFileConverter, unsigned >> int>::WorkerBase' >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: >> In member function 'typename Factory::Abstract_T* >> PWAVFilePluginFactory<Factory, Instance>::Create(const typename >> Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, >> PCaselessString>, Instance = PWAVFileFormatPlugin]': >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: >> instantiated from here >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: >> error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: >> note: because the following virtual functions are pure within >> 'PWAVFileFormatPlugin': >> /usr/include/ptclib/pwavfile.h:107: note: virtual bool >> PWAVFileFormat::CanSetChannels(unsigned int) const >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: >> In member function 'typename Factory::Abstract_T* >> PWAVFilePluginFactory<Factory, Instance>::Create(const typename >> Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, unsigned >> int>, Instance = PWAVFileFormatPlugin]': >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: >> instantiated from here >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: >> error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' >> /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: >> note: since type 'PWAVFileFormatPlugin' has pure virtual functions >> make: *** >> [/home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/lib_linux_x86_64/obj/opalwavfile.o] >> Error 1 >> error: Bad exit status from /var/tmp/rpm-tmp.0KuYN2 (%build) >> >> >> Slava. >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> Opalvoip-user mailing list >> Opa...@li... >> https://lists.sourceforge.net/lists/listinfo/opalvoip-user >> >> > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > -- *Pete Davidson* Senior Software Developer Embedded Systems *O *+1 859 825 4999 *M* +1 859 338 3426 *F* +1 859 232 6267 Pete@Lexmark.com <http://www.lexmark.com/> www.lexmark.com |
|
From: Slava B. <vol...@sk...> - 2015-05-10 13:44:48
|
Hello Robert, Yes, you right t38modem is require specific opal version. It opal-24174.tgz . That the version I have the issue to compile with. Slava. From: "Robert Jongbloed" <ro...@vo...> To: "volga629" <vol...@sk...> Cc: "opalvoip-user" <opa...@li...> Sent: Sunday, May 10, 2015 2:58:24 AM Subject: Re: [Opalvoip-user] compile error t38modem only works with a very specific version of PTLib/OPAL. Unfortunately, I cannot tell you what that version is. I hope someone else on this list know ... Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder . On 9 May 2015 at 13:57, Slava Bendersky < vol...@sk... > wrote: Hello Everyone, Trying compile opal-voip for t38modem and getting the following error, any help thank you. Here build output: http://fpaste.org/220091/43114356/ [CC] src/codec/opalwavfile.cxx /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, unsigned int>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:411: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, unsigned int>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, PCaselessString>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:412: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, PCaselessString>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileConverter, unsigned int>, Instance = PWAVFileConverterPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:415: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileConverter, unsigned int>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In member function 'typename Factory::Abstract_T* PWAVFilePluginFactory<Factory, Instance>::Create(const typename Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, PCaselessString>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: note: because the following virtual functions are pure within 'PWAVFileFormatPlugin': /usr/include/ptclib/pwavfile.h:107: note: virtual bool PWAVFileFormat::CanSetChannels(unsigned int) const /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In member function 'typename Factory::Abstract_T* PWAVFilePluginFactory<Factory, Instance>::Create(const typename Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, unsigned int>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: note: since type 'PWAVFileFormatPlugin' has pure virtual functions make: *** [/home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/lib_linux_x86_64/obj/opalwavfile.o] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.0KuYN2 (%build) Slava. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Opalvoip-user mailing list Opa...@li... https://lists.sourceforge.net/lists/listinfo/opalvoip-user |
|
From: Robert J. <ro...@vo...> - 2015-05-10 06:58:32
|
t38modem only works with a very specific version of PTLib/OPAL. Unfortunately, I cannot tell you what that version is. I hope someone else on this list know ... Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 9 May 2015 at 13:57, Slava Bendersky <vol...@sk...> wrote: > Hello Everyone, > Trying compile opal-voip for t38modem and getting the following error, any > help thank you. > > Here build output: > > http://fpaste.org/220091/43114356/ > > [CC] src/codec/opalwavfile.cxx > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: > In constructor 'PWAVFilePluginFactory<Factory, > Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const > PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, > unsigned int>, Instance = PWAVFileFormatPlugin]': > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:411: > instantiated from here > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: > error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, unsigned > int>::WorkerBase' > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: > In constructor 'PWAVFilePluginFactory<Factory, > Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const > PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, > PCaselessString>, Instance = PWAVFileFormatPlugin]': > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:412: > instantiated from here > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: > error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, > PCaselessString>::WorkerBase' > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: > In constructor 'PWAVFilePluginFactory<Factory, > Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const > PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileConverter, > unsigned int>, Instance = PWAVFileConverterPlugin]': > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:415: > instantiated from here > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: > error: 'isDynamic' is not a member of 'PFactory<PWAVFileConverter, unsigned > int>::WorkerBase' > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: > In member function 'typename Factory::Abstract_T* > PWAVFilePluginFactory<Factory, Instance>::Create(const typename > Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, > PCaselessString>, Instance = PWAVFileFormatPlugin]': > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: > instantiated from here > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: > error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: > note: because the following virtual functions are pure within > 'PWAVFileFormatPlugin': > /usr/include/ptclib/pwavfile.h:107: note: virtual bool > PWAVFileFormat::CanSetChannels(unsigned int) const > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: > In member function 'typename Factory::Abstract_T* > PWAVFilePluginFactory<Factory, Instance>::Create(const typename > Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, unsigned > int>, Instance = PWAVFileFormatPlugin]': > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: > instantiated from here > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: > error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' > /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: > note: since type 'PWAVFileFormatPlugin' has pure virtual functions > make: *** > [/home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/lib_linux_x86_64/obj/opalwavfile.o] > Error 1 > error: Bad exit status from /var/tmp/rpm-tmp.0KuYN2 (%build) > > > Slava. > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > |
|
From: Slava B. <vol...@sk...> - 2015-05-09 04:16:15
|
Hello Everyone, Trying compile opal-voip for t38modem and getting the following error, any help thank you. Here build output: http://fpaste.org/220091/43114356/ [CC] src/codec/opalwavfile.cxx /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, unsigned int>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:411: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, unsigned int>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileFormat, PCaselessString>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:412: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileFormat, PCaselessString>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In constructor 'PWAVFilePluginFactory<Factory, Instance>::PWAVFilePluginFactory(const typename Factory::Key_T&, const PWAVFilePluginValidFormat&) [with Factory = PFactory<PWAVFileConverter, unsigned int>, Instance = PWAVFileConverterPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:415: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:388: error: 'isDynamic' is not a member of 'PFactory<PWAVFileConverter, unsigned int>::WorkerBase' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In member function 'typename Factory::Abstract_T* PWAVFilePluginFactory<Factory, Instance>::Create(const typename Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, PCaselessString>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: note: because the following virtual functions are pure within 'PWAVFileFormatPlugin': /usr/include/ptclib/pwavfile.h:107: note: virtual bool PWAVFileFormat::CanSetChannels(unsigned int) const /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx: In member function 'typename Factory::Abstract_T* PWAVFilePluginFactory<Factory, Instance>::Create(const typename Factory::Key_T&) const [with Factory = PFactory<PWAVFileFormat, unsigned int>, Instance = PWAVFileFormatPlugin]': /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:421: instantiated from here /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:394: error: cannot allocate an object of abstract type 'PWAVFileFormatPlugin' /home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/src/codec/opalwavfile.cxx:307: note: since type 'PWAVFileFormatPlugin' has pure virtual functions make: *** [/home/volga629/rpmbuild/BUILD/t38modem-2.0.0/opal/lib_linux_x86_64/obj/opalwavfile.o] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.0KuYN2 (%build) Slava. |
|
From: Robert J. <ro...@vo...> - 2015-05-06 00:14:48
|
Sorry, first thing I am going to say is "have you tried latest version"? 3.12.x is very, very old. And it is extremely unlikely there will be fixes made to it. Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 5 May 2015 at 21:14, Michael Prader <mic...@my...> wrote: > Dear All, > > > > we are using OpalVoip 3.12.9 to perform a direct sip call. In our case we > call from a 2N IP Vario outdoor sip station to our device running OpalVoip. > We have the problem, that the ContactUri of our OpalVoip is wrong: Contact: > "2000" <sip:2000@0.0.0.0>. In this case the outdoor station sends the ACK > to 0.0.0.0, OpalVoip doesn´t receive the ACK and hangs up after a while, > see the attached log. > > > > We are setting up OpalCmdSetGeneralParameters and > OpalCmdSetProtocolParameters but no registration parameters. Is there some > way to fix this problem? > > > Thanks > > Michael Prader > > > > > > > > INVITE sip:2000@192.168.2.252 SIP/2.0 > Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394 > From: "2N Helios IP Vario" <sip:2002@192.168.2.32>;tag=22942 > To: <sip:2000@192.168.2.252> > Call-ID: 13671 > CSeq: 20 INVITE > Contact: <sip:2002@192.168.2.32:5060> > Content-Type: application/sdp > Allow: REGISTER, INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, NOTIFY > Max-Forwards: 70 > User-Agent: 2N Helios IP Vario 2.11.1.20.4 > Content-Length: 572 > > ...... > > SIP/2.0 180 Ringing > CSeq: 20 INVITE > Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394 > From: "2N Helios IP Vario" <sip:2002@192.168.2.32>;tag=22942 > Call-ID: 13671 > To: "2000" <sip:2000@192.168.2.252 > >;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001 > Contact: "2000" <sip:2000@0.0.0.0> > Allow: > INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING,PRACK > Content-Length: 0 > > SIP/2.0 200 OK > CSeq: 20 INVITE > Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394 > From: "2N Helios IP Vario" <sip:2002@192.168.2.32>;tag=22942 > Call-ID: 13671 > To: "2000" <sip:2000@192.168.2.252 > >;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001 > *Contact: "2000" <sip:2000@0.0.0.0 <sip%3A2000@0.0.0.0>>* > Allow: > INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING,PRACK > Content-Length: 179 > Content-Type: application/sdp > > > .... > > > > > > ACK sip:2000@0.0.0.0 SIP/2.0 > Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK27652 > From: "2N Helios IP Vario" <sip:2002@192.168.2.32>;tag=22942 > To: "2000" <sip:2000@192.168.2.252 > >;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001 > Call-ID: 13671 > CSeq: 20 ACK > Contact: <sip:2002@192.168.2.32:5060> > Allow: REGISTER, INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, NOTIFY > Max-Forwards: 70 > User-Agent: 2N Helios IP Vario 2.11.1.20.4 > Content-Length: 0 > > > > .... > > > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > |
|
From: Michael P. <mic...@my...> - 2015-05-05 11:30:56
|
Dear All,
we are using OpalVoip 3.12.9 to perform a direct sip call. In our case
we call from a 2N IP Vario outdoor sip station to our device running
OpalVoip. We have the problem, that the ContactUri of our OpalVoip is
wrong: Contact: "2000" . In this case the outdoor station sends the
ACK to 0.0.0.0, OpalVoip doesn´t receive the ACK and hangs up
after a while, see the attached log.
We are setting up OpalCmdSetGeneralParameters and
OpalCmdSetProtocolParameters but no registration parameters. Is there
some way to fix this problem?
Thanks
Michael Prader
INVITE sip:2000@192.168.2.252 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394
From: "2N Helios IP Vario" ;tag=22942
To:
Call-ID: 13671
CSeq: 20 INVITE
Contact:
Content-Type: application/sdp
Allow: REGISTER, INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, NOTIFY
Max-Forwards: 70
User-Agent: 2N Helios IP Vario 2.11.1.20.4
Content-Length: 572
......
SIP/2.0 180 Ringing
CSeq: 20 INVITE
Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394
From: "2N Helios IP Vario" ;tag=22942
Call-ID: 13671
To: "2000" ;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001
Contact: "2000"
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING,PRACK
Content-Length: 0
SIP/2.0 200 OK
CSeq: 20 INVITE
Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK5394
From: "2N Helios IP Vario" ;tag=22942
Call-ID: 13671
To: "2000" ;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001
CONTACT: \"2000\"
Allow:
INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING,PRACK
Content-Length: 179
Content-Type: application/sdp
....
ACK sip:2000@0.0.0.0 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.32:5060;rport;branch=z9hG4bK27652
From: "2N Helios IP Vario" ;tag=22942
To: "2000" ;tag=542dc84f-84f1-e411-9aa1-ac0dfe300001
Call-ID: 13671
CSeq: 20 ACK
Contact:
Allow: REGISTER, INVITE, ACK, CANCEL, OPTIONS, BYE, INFO, NOTIFY
Max-Forwards: 70
User-Agent: 2N Helios IP Vario 2.11.1.20.4
Content-Length: 0
....
|
|
From: Robert J. <ro...@vo...> - 2015-03-08 11:05:26
|
Fixed by renaming conf listen to conf hear Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 25 February 2015 at 13:34, Alexander Sbitnev <ale...@gm... > wrote: > Just notice that "conf list" command isn't working. At the same time > by commenting out "conf listen" command, "conf list" starts working. > I suppose something wrong with command line parsing. > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, > sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for > all > things parallel software development, from weekly thought leadership blogs > to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > |
|
From: Robert J. <ro...@vo...> - 2015-03-08 10:13:56
|
Can you send me the logs? Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 20 February 2015 at 11:34, Sasa Davidovic <Sas...@ca...> wrote: > Hi all, > > I'm experiencing interesting problem when trying to register SIP or > H.323 client (in this case callgen sample program) to SIP registrar or > H.323 gatekeeper, in case when host(linux) have more than one IP address > (IP aliases). > > When using any other IP address, except first one ( by using -H and -S > callgen options), client, either SIP or H.323, fails to register to > appropriate SIP registrar or H.323 gatekeeper. > > According to logs, although started and listening on IP address provided > by -H or -S option, client always uses first (default ) IP address for > communication toward SIP registrar or H.323 gatekeeper. > > There is an option for H.323 client (--gk-interface <arg> : Gatekeeper > network interface to use for RAS. ) which forces which IP address will > be used for registration, however it seems that there isn't anything > similar for SIP (or I'm missing something? :) ) > > Does anybody have similar problem? I would appreciate if someone have > any kind of solution(s), especially for SIP. > > System OS: Linux Debian stable > Versions: ptlib 2.14.4 (revision 33370), opal 3.14.4 (revision 33370) > Sample program: callgen > > Older versions of opal/ptlib doesn't have similar problem, and normally > worked (and still does) with multiple IP addresses. > > I suppose that there is a reason why this is changed in recent versions > (introduced --gk-interface option), and it would be nice if anybody is > willing to clarify that to me. :) > > Thanks in advance. > > cheers, > > Sasha D. > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > |
|
From: Robert J. <ro...@vo...> - 2015-03-08 10:12:41
|
This is a benign error. At a point in the heuristic for deciding how to
interpret the h323 URI, OPAL will try and see if the name used is a valid
hostname, hence the "name lookup". The failure just means that it will be
interpreted as a username and not a hostname. I canot say as to why
000000010 did not also give the error.
So, what is the actual problem you are having?
Perhaps sending the whole log file would help. Do not send to the list,
send to me directly.
Robert Jongbloed
*OPAL/OpenH323/PTLib Architect and Co-founder*.
On 25 February 2015 at 07:33, Sagar Joshi <sag...@gs...> wrote:
> Hi All,
>
>
>
> We have OPAL based Telepresence Gateway implemented for SIP and H.323 call
> in and call out scenarios.
>
> I am facing an call connect issue for both H.323 and SIP . I am using the
> opal 3.14 Lacaille.
>
>
>
> In case of H.323 call received by Opal the logs are as follows
>
>
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1683) OpalMan Searching for route "
> h323:HDX1235@115.113.154.10 mcu:00000085"
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
> (h323:[1-9][0-9]{6,9}@.*)$" (h323:.*\th323:[1-9][0-9]{6,9}@.*=fuze:<du>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
> (sip:[1-9][0-9]{6,9}@.*)$" (h323:.*\tsip:[1-9][0-9]{6,9}@.*=fuze:<du >)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
> ([1-9][0-9]{6,9}@.*)$" (h323:.*\t[1-9][0-9]{6,9}@.*=fuze:<du>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
> (sip:[1-9][0-9]{6,9}@.*)$" (sip:.*\tsip:[1-9][0-9]{6,9}@.*=fuze:<du>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
> (h323:[1-9][0-9]{6,9}@.*)$" (sip:.*\th323:[1-9][0-9]{6,9}@.*=fuze:<du>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
> ([1-9][0-9]{6,9}@.*)$" (sip:.*\t[1-9][0-9]{6,9}@.*=fuze:<du>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
> ([1-9][0-9]{6,9})$" (h323:.*\t[1-9][0-9]{6,9}=fuze:<db>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
> ([1-9][0-9]{6,9})$" (sip:.*\t[1-9][0-9]{6,9}=fuze:<db>)
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> manager.cxx(1589) OpalMan Matched regex "^(h323:.*)
> (mcu:[0-9]+)$" (h323:.*\tmcu:[0-9]+=mcu:<du>)
>
> *2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> sockets.cxx(633) Socket Name lookup of "00000085" failed:
> errno=-5*
>
> 2015/02/24 13:05:48.546 3 Opal Answe...97bf774700
> manager.cxx(802) OpalMan Set up connection to "mcu:00000085"
>
> 2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
> opalmixer.cxx(827) MixerEP Making connection to "mcu:00000085"
>
>
>
> The strange thing is that I get name lookup successful for earlier e.g.*
> 00000010 . * Is there a limitation in the Opal code for searching a ID ?
>
>
>
> In case of SIP of SIP call received by OPAL , there is SIP CANCEL sent.
>
>
>
> Thanks and Regards
>
> Sagar Joshi
>
> Lead Software Engineer, Convergence Practice
>
> Great Software Laboratory (GS Lab)
>
>
>
> *“It’s Attitude and not Aptitude that’s decides your Altitude” *
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
>
|
|
From: Alexander S. <ale...@gm...> - 2015-02-25 13:34:19
|
Just notice that "conf list" command isn't working. At the same time by commenting out "conf listen" command, "conf list" starts working. I suppose something wrong with command line parsing. |
|
From: Sagar J. <sag...@gs...> - 2015-02-25 07:58:59
|
Hi All,
We have OPAL based Telepresence Gateway implemented for SIP and H.323 call
in and call out scenarios.
I am facing an call connect issue for both H.323 and SIP . I am using the
opal 3.14 Lacaille.
In case of H.323 call received by Opal the logs are as follows
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1683) OpalMan Searching for route "
h323:HDX1235@115.113.154.10 mcu:00000085"
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
(h323:[1-9][0-9]{6,9}@.*)$" (h323:.*\th323:[1-9][0-9]{6,9}@.*=fuze:<du>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
(sip:[1-9][0-9]{6,9}@.*)$" (h323:.*\tsip:[1-9][0-9]{6,9}@.*=fuze:<du >)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
([1-9][0-9]{6,9}@.*)$" (h323:.*\t[1-9][0-9]{6,9}@.*=fuze:<du>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
(sip:[1-9][0-9]{6,9}@.*)$" (sip:.*\tsip:[1-9][0-9]{6,9}@.*=fuze:<du>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
(h323:[1-9][0-9]{6,9}@.*)$" (sip:.*\th323:[1-9][0-9]{6,9}@.*=fuze:<du>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
([1-9][0-9]{6,9}@.*)$" (sip:.*\t[1-9][0-9]{6,9}@.*=fuze:<du>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(h323:.*)
([1-9][0-9]{6,9})$" (h323:.*\t[1-9][0-9]{6,9}=fuze:<db>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Did not match regex "^(sip:.*)
([1-9][0-9]{6,9})$" (sip:.*\t[1-9][0-9]{6,9}=fuze:<db>)
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
manager.cxx(1589) OpalMan Matched regex "^(h323:.*)
(mcu:[0-9]+)$" (h323:.*\tmcu:[0-9]+=mcu:<du>)
*2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
sockets.cxx(633) Socket Name lookup of "00000085" failed:
errno=-5*
2015/02/24 13:05:48.546 3 Opal Answe...97bf774700
manager.cxx(802) OpalMan Set up connection to "mcu:00000085"
2015/02/24 13:05:48.546 4 Opal Answe...97bf774700
opalmixer.cxx(827) MixerEP Making connection to "mcu:00000085"
The strange thing is that I get name lookup successful for earlier e.g.*
00000010 . * Is there a limitation in the Opal code for searching a ID ?
In case of SIP of SIP call received by OPAL , there is SIP CANCEL sent.
Thanks and Regards
Sagar Joshi
Lead Software Engineer, Convergence Practice
Great Software Laboratory (GS Lab)
*“It’s Attitude and not Aptitude that’s decides your Altitude” *
|
|
From: Sasa D. <Sasa.Davidovic@CARNet.hr> - 2015-02-20 11:51:16
|
Hi all, I'm experiencing interesting problem when trying to register SIP or H.323 client (in this case callgen sample program) to SIP registrar or H.323 gatekeeper, in case when host(linux) have more than one IP address (IP aliases). When using any other IP address, except first one ( by using -H and -S callgen options), client, either SIP or H.323, fails to register to appropriate SIP registrar or H.323 gatekeeper. According to logs, although started and listening on IP address provided by -H or -S option, client always uses first (default ) IP address for communication toward SIP registrar or H.323 gatekeeper. There is an option for H.323 client (--gk-interface <arg> : Gatekeeper network interface to use for RAS. ) which forces which IP address will be used for registration, however it seems that there isn't anything similar for SIP (or I'm missing something? :) ) Does anybody have similar problem? I would appreciate if someone have any kind of solution(s), especially for SIP. System OS: Linux Debian stable Versions: ptlib 2.14.4 (revision 33370), opal 3.14.4 (revision 33370) Sample program: callgen Older versions of opal/ptlib doesn't have similar problem, and normally worked (and still does) with multiple IP addresses. I suppose that there is a reason why this is changed in recent versions (introduced --gk-interface option), and it would be nice if anybody is willing to clarify that to me. :) Thanks in advance. cheers, Sasha D. |
|
From: Robert J. <ro...@vo...> - 2015-02-20 01:02:14
|
OK, hard to find the problem when not exhibited. Oh well, works for you
now, I suppose.
Some notes on OpalInitialise, having had a quick look at the code:
It only loads the audio and video plug ins. It should not open any, except
perhaps to determine if there are any devices available. I am not an expert
in the fine details of that part of the code.
The only reasons for OpalInitialise to return NULL are invalid arguments to
it, or there are no valid endpoints or "protocols" specified. Neither seems
to be the case in your initial code, so it is a complete mystery why it is
doing what you said it did.
Oh, final point, only having "sip" as an endpoint might not work. You would
need to indicate what the SIP connections are connecting to,
e.g. OPAL_PREFIX_PCSS. As it is, I think you would only be able to make
B2BUA calls.
Robert Jongbloed
*OPAL/OpenH323/PTLib Architect and Co-founder*.
On 20 February 2015 at 11:43, jeremy ardley <jer...@gm...> wrote:
> I am unable to replicate exactly the behaviour I experienced earlier.
> Previously the code attempted to open the V4L device and aborted when it
> was not found.
>
> The difference now is I have installed a bunch of V4L dev packages on my
> Wheezy system and plugged in and then removed a video device.
>
> Now it searches for the v4L device but does not abort when it doesn't find
> one. I also rebooted to clear any remnant device information.
>
> This is the present log. You can see the code is hard wired to find a v4L
> device early on in the piece. It doesn't mention searching for or opening
> other plug-in devices including ALSA. It mentions the other devices
> including ALSA later on after I start the shutdown.
>
> My program opens OPAL using SIP transport only, prints "hello world", and
> then shuts the system down and exits (I'm actually looking at the
> feasibility of converting a much larger application from a different TAPI
> to OPAL - this is just an experiment to get used to OPAL.)
>
>
> Starting: /home/jeremy/Projects/pirad/build/pirad
> 0:00.545 Version 1.0.1 by on Unix
> Linux (3.2.0-4-amd64-x86_64) with PTLib (v2.10.4 (svn:26606)) at 2015/2/20
> 8:26:18.957
> 0:00.545 OpalC Start Up, OPAL version
> 3.10.4 (svn:26616)
> 0:00.545 Detecting V4L2 devices
> 0:00.545 Unable to detect v4l2 directory
> 0:00.548 PWLib File handle high water
> mark set: 7 Thread unblock pipe
> 0:00.548 PTLib Thread high water mark
> set: 2
> 0:00.548 OpalMan Created manager.
> 0:00.549 OpalMan Attached endpoint with
> prefix sip
> 0:00.549 OpalEP Created endpoint: sip
> 0:00.549 PWLib File handle high water
> mark set: 8 PUDPSocket
> 0:00.549 IfaceMon Initial interface
> list:
> 127.0.0.1 <00-00-00-00-00-00> (lo)
> 203.31.40.68 <C8-60-00-9D-73-1D> (eth0)
> 192.168.100.67 <C8-60-00-9D-73-1D> (eth0:0)
> 192.168.0.9 <C8-60-00-9D-73-1D> (eth0:1)
> fe80::ca60:ff:fe9d:731d <C8-60-00-9D-73-1D> (eth0)
> ::1 <00-00-00-00-00-00> (lo)
>
> 0:00.549 PTLIB Opened NetLink socket
> 0:00.549 PWLib File handle high water
> mark set: 18 Thread unblock pipe
> 0:00.549 PTLib Thread high water mark
> set: 3
> 0:00.549 PWLib File handle high water
> mark set: 20 Thread unblock pipe
> 0:00.549 PTLib No permission to set
> priority level 4
> 0:00.549 PTLib Thread high water mark
> set: 4
> 0:00.549 Network In...0xa93a0700 IfaceMon Started interface
> monitor thread.
> 0:00.550 OpalMan Attached endpoint with
> prefix sips
> 0:00.550 SIP Created endpoint.
> 0:00.550 OpalMan Added route "sip:.*="
> Hello, world!
> 0:00.550 OpalMan Shutting down
> endpoints.
> 0:00.550 OpalMan Clearing all calls and
> waiting, primary thread.
> 0:02.549 OpalMan All calls cleared.
> 0:02.549 SIP Shutting down.
> 0:02.649 OpalEP sip endpoint shutting
> down.
> 0:02.649 IfaceMon Awaiting thread
> termination
> 0:02.649 Network In...0xa93a0700 IfaceMon Finished interface
> monitor thread.
> 0:02.649 Network In...0xa93a0700 PWLib File handle high water
> mark set: 21 PTextFile
> 0:02.650 Network In...0xa93a0700 PTLib Thread ended:
> name="Network Interface Monitor:0xa93a0700", real=2.100, kernel=0.000 (0%),
> user=0.000 (0%), both=0.000 (0%)
> 0:02.680 OpalEP sip endpoint destroyed.
> 0:02.680 OpalMan Shutting down
> endpoints.
> 0:02.680 OpalMan Clearing all calls and
> waiting, primary thread.
> 0:03.549 OpalMan All calls cleared.
> 0:03.549 Opal Garbage:0xa93e1700 PWLib File handle low water
> mark set: 8 PTextFile
> 0:03.549 Opal Garbage:0xa93e1700 PTLib Thread ended: name="Opal
> Garbage:0xa93e1700", real=3.001, kernel=0.000 (0%), user=0.000 (0%),
> both=0.000 (0%)
> 0:03.559 OpalMan Deleted manager.
> 0:03.560 OpalC Shut Down.
> 0:03.560 OpalPlugin Using default
> handler for plugin codec lpc10_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec g726_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec silk_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec gsmamrcodec_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec g7222_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec g722_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec ima_adpcm_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec g7221_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec gsm0610_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec speex_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec mpeg4_ffmpeg_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec theora_ptplugin
> 0:03.560 OpalPlugin Using default
> handler for plugin codec h261_vic_ptplugin
> 0:03.561 OpalPlugin Using default
> handler for plugin codec h263_ffmpeg_ptplugin
> 0:03.561 OpalPlugin Using default
> handler for plugin codec spandsp_ptplugin
> 0:03.561 UDLL Closing
> /usr/lib/opal-3.10.4/fax/spandsp_ptplugin.so
> 0:03.561 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/video/h263_ffmpeg_ptplugin.so
> 0:03.561 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/video/h261_vic_ptplugin.so
> 0:03.561 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/video/theora_ptplugin.so
> 0:03.561 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/video/mpeg4_ffmpeg_ptplugin.so
> 0:03.562 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/speex_ptplugin.so
> 0:03.562 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/gsm0610_ptplugin.so
> 0:03.562 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/g7221_ptplugin.so
> 0:03.562 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/ima_adpcm_ptplugin.so
> 0:03.562 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/g722_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/g7222_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/gsmamrcodec_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/silk_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/g726_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/opal-3.10.4/codecs/audio/lpc10_ptplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/ptlib-2.10.4/devices/sound/pulse_pwplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/ptlib-2.10.4/devices/sound/alsa_pwplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/ptlib-2.10.4/devices/sound/oss_pwplugin.so
> 0:03.563 UDLL Closing
> /usr/lib/ptlib-2.10.4/devices/videoinput/v4l2_pwplugin.so
> 0:13.560 Housekeeper:0xa935f700 PWLib File handle low water
> mark set: 6 PTextFile
> 0:13.560 Housekeeper:0xa935f700 PTLib Thread ended:
> name="Housekeeper:0xa935f700", real=13.011, kernel=0.000 (0%), user=0.000
> (0%), both=0.000 (0%)
> *** Exited normally ***
>
>
>
>
>
> On 20/02/15 07:37, Robert Jongbloed wrote:
>
> I am bit confused by your requirement, as V4L is video and ALSA is audio,
> they are not interchangeable!
>
> There is nothing to be called before OpalInitialise() it is the first
> function you call.
>
> I do not understand why not having a V4L device causes OpalInitialise to
> return NULL. It should not care. Can you provide the trace log?
>
>
>
> Robert Jongbloed
> *OPAL/OpenH323/PTLib Architect and Co-founder*.
>
> On 19 February 2015 at 16:01, jeremy ardley <jer...@gm...>
> wrote:
>
>> I use a small snippet of code to open the OPAL device in a SIP voice
>> application
>>
>> OpalHandle hOPAL;
>>
>> unsigned version;
>>
>> version = OPAL_C_API_VERSION;
>>
>> if ((hOPAL = OpalInitialise(&version, OPAL_PREFIX_SIP " TraceLevel=4"))
>> == NULL)
>>
>> {
>>
>> fputs("Could not initialise OPAL\n", stderr);
>>
>> return false;
>>
>> }
>>
>> However the OPAL instance wants to open a V4L2 device and fails since I
>> don't have one.
>>
>> Can I prevent the OPAL instance from trying to open a V4L device and
>> instead open an ALSA device?
>>
>> What calls prior to the OplaInitialise are required? Or is using the
>> wrapper functions not suitable for this and I should use low level
>> calls? Or does it require compile time switches? In all cases is there a
>> link or tutorial I can use?
>>
>> I did searches on the error message phrase and not found much of use
>> other than similar messages from apps using OPAL. I also looked through
>> the doxygen documentation but it's a bit obscure about this. I also
>> installed a 4VL device and got it to work O.K. but my target application
>> won't have V4L.
>>
>> Any advice appreciated.
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Opalvoip-user mailing list
>> Opa...@li...
>> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
>
|
|
From: jeremy a. <jer...@gm...> - 2015-02-20 00:43:28
|
I am unable to replicate exactly the behaviour I experienced earlier.
Previously the code attempted to open the V4L device and aborted when it
was not found.
The difference now is I have installed a bunch of V4L dev packages on my
Wheezy system and plugged in and then removed a video device.
Now it searches for the v4L device but does not abort when it doesn't
find one. I also rebooted to clear any remnant device information.
This is the present log. You can see the code is hard wired to find a
v4L device early on in the piece. It doesn't mention searching for or
opening other plug-in devices including ALSA. It mentions the other
devices including ALSA later on after I start the shutdown.
My program opens OPAL using SIP transport only, prints "hello world",
and then shuts the system down and exits (I'm actually looking at the
feasibility of converting a much larger application from a different
TAPI to OPAL - this is just an experiment to get used to OPAL.)
Starting: /home/jeremy/Projects/pirad/build/pirad
0:00.545 Version 1.0.1 by on Unix
Linux (3.2.0-4-amd64-x86_64) with PTLib (v2.10.4 (svn:26606)) at
2015/2/20 8:26:18.957
0:00.545 OpalC Start Up, OPAL version
3.10.4 (svn:26616)
0:00.545 Detecting V4L2 devices
0:00.545 Unable to detect v4l2 directory
0:00.548 PWLib File handle high water
mark set: 7 Thread unblock pipe
0:00.548 PTLib Thread high water mark
set: 2
0:00.548 OpalMan Created manager.
0:00.549 OpalMan Attached endpoint
with prefix sip
0:00.549 OpalEP Created endpoint: sip
0:00.549 PWLib File handle high water
mark set: 8 PUDPSocket
0:00.549 IfaceMon Initial interface list:
127.0.0.1 <00-00-00-00-00-00> (lo)
203.31.40.68 <C8-60-00-9D-73-1D> (eth0)
192.168.100.67 <C8-60-00-9D-73-1D> (eth0:0)
192.168.0.9 <C8-60-00-9D-73-1D> (eth0:1)
fe80::ca60:ff:fe9d:731d <C8-60-00-9D-73-1D> (eth0)
::1 <00-00-00-00-00-00> (lo)
0:00.549 PTLIB Opened NetLink socket
0:00.549 PWLib File handle high water
mark set: 18 Thread unblock pipe
0:00.549 PTLib Thread high water mark
set: 3
0:00.549 PWLib File handle high water
mark set: 20 Thread unblock pipe
0:00.549 PTLib No permission to set
priority level 4
0:00.549 PTLib Thread high water mark
set: 4
0:00.549 Network In...0xa93a0700 IfaceMon Started interface
monitor thread.
0:00.550 OpalMan Attached endpoint
with prefix sips
0:00.550 SIP Created endpoint.
0:00.550 OpalMan Added route "sip:.*="
Hello, world!
0:00.550 OpalMan Shutting down endpoints.
0:00.550 OpalMan Clearing all calls
and waiting, primary thread.
0:02.549 OpalMan All calls cleared.
0:02.549 SIP Shutting down.
0:02.649 OpalEP sip endpoint shutting
down.
0:02.649 IfaceMon Awaiting thread
termination
0:02.649 Network In...0xa93a0700 IfaceMon Finished interface
monitor thread.
0:02.649 Network In...0xa93a0700 PWLib File handle high water
mark set: 21 PTextFile
0:02.650 Network In...0xa93a0700 PTLib Thread ended:
name="Network Interface Monitor:0xa93a0700", real=2.100, kernel=0.000
(0%), user=0.000 (0%), both=0.000 (0%)
0:02.680 OpalEP sip endpoint destroyed.
0:02.680 OpalMan Shutting down endpoints.
0:02.680 OpalMan Clearing all calls
and waiting, primary thread.
0:03.549 OpalMan All calls cleared.
0:03.549 Opal Garbage:0xa93e1700 PWLib File handle low water
mark set: 8 PTextFile
0:03.549 Opal Garbage:0xa93e1700 PTLib Thread ended:
name="Opal Garbage:0xa93e1700", real=3.001, kernel=0.000 (0%),
user=0.000 (0%), both=0.000 (0%)
0:03.559 OpalMan Deleted manager.
0:03.560 OpalC Shut Down.
0:03.560 OpalPlugin Using default
handler for plugin codec lpc10_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec g726_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec silk_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec gsmamrcodec_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec g7222_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec g722_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec ima_adpcm_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec g7221_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec gsm0610_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec speex_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec mpeg4_ffmpeg_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec theora_ptplugin
0:03.560 OpalPlugin Using default
handler for plugin codec h261_vic_ptplugin
0:03.561 OpalPlugin Using default
handler for plugin codec h263_ffmpeg_ptplugin
0:03.561 OpalPlugin Using default
handler for plugin codec spandsp_ptplugin
0:03.561 UDLL Closing
/usr/lib/opal-3.10.4/fax/spandsp_ptplugin.so
0:03.561 UDLL Closing
/usr/lib/opal-3.10.4/codecs/video/h263_ffmpeg_ptplugin.so
0:03.561 UDLL Closing
/usr/lib/opal-3.10.4/codecs/video/h261_vic_ptplugin.so
0:03.561 UDLL Closing
/usr/lib/opal-3.10.4/codecs/video/theora_ptplugin.so
0:03.561 UDLL Closing
/usr/lib/opal-3.10.4/codecs/video/mpeg4_ffmpeg_ptplugin.so
0:03.562 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/speex_ptplugin.so
0:03.562 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/gsm0610_ptplugin.so
0:03.562 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/g7221_ptplugin.so
0:03.562 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/ima_adpcm_ptplugin.so
0:03.562 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/g722_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/g7222_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/gsmamrcodec_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/silk_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/g726_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/opal-3.10.4/codecs/audio/lpc10_ptplugin.so
0:03.563 UDLL Closing
/usr/lib/ptlib-2.10.4/devices/sound/pulse_pwplugin.so
0:03.563 UDLL Closing
/usr/lib/ptlib-2.10.4/devices/sound/alsa_pwplugin.so
0:03.563 UDLL Closing
/usr/lib/ptlib-2.10.4/devices/sound/oss_pwplugin.so
0:03.563 UDLL Closing
/usr/lib/ptlib-2.10.4/devices/videoinput/v4l2_pwplugin.so
0:13.560 Housekeeper:0xa935f700 PWLib File handle low water
mark set: 6 PTextFile
0:13.560 Housekeeper:0xa935f700 PTLib Thread ended:
name="Housekeeper:0xa935f700", real=13.011, kernel=0.000 (0%),
user=0.000 (0%), both=0.000 (0%)
*** Exited normally ***
On 20/02/15 07:37, Robert Jongbloed wrote:
> I am bit confused by your requirement, as V4L is video and ALSA is
> audio, they are not interchangeable!
>
> There is nothing to be called before OpalInitialise() it is the first
> function you call.
>
> I do not understand why not having a V4L device causes OpalInitialise
> to return NULL. It should not care. Can you provide the trace log?
>
>
>
> Robert Jongbloed
> /OPAL/OpenH323/PTLib Architect and Co-founder/.
>
>
> On 19 February 2015 at 16:01, jeremy ardley <jer...@gm...
> <mailto:jer...@gm...>> wrote:
>
> I use a small snippet of code to open the OPAL device in a SIP voice
> application
>
> OpalHandle hOPAL;
>
> unsigned version;
>
> version = OPAL_C_API_VERSION;
>
> if ((hOPAL = OpalInitialise(&version, OPAL_PREFIX_SIP "
> TraceLevel=4")) == NULL)
>
> {
>
> fputs("Could not initialise OPAL\n", stderr);
>
> return false;
>
> }
>
> However the OPAL instance wants to open a V4L2 device and fails
> since I
> don't have one.
>
> Can I prevent the OPAL instance from trying to open a V4L device and
> instead open an ALSA device?
>
> What calls prior to the OplaInitialise are required? Or is using the
> wrapper functions not suitable for this and I should use low level
> calls? Or does it require compile time switches? In all cases is
> there a
> link or tutorial I can use?
>
> I did searches on the error message phrase and not found much of use
> other than similar messages from apps using OPAL. I also looked
> through
> the doxygen documentation but it's a bit obscure about this. I also
> installed a 4VL device and got it to work O.K. but my target
> application
> won't have V4L.
>
> Any advice appreciated.
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and
> Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration
> & more
> Get technology previously reserved for billion-dollar
> corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> <mailto:Opa...@li...>
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
>
|
|
From: Robert J. <ro...@vo...> - 2015-02-19 23:37:36
|
I am bit confused by your requirement, as V4L is video and ALSA is audio,
they are not interchangeable!
There is nothing to be called before OpalInitialise() it is the first
function you call.
I do not understand why not having a V4L device causes OpalInitialise to
return NULL. It should not care. Can you provide the trace log?
Robert Jongbloed
*OPAL/OpenH323/PTLib Architect and Co-founder*.
On 19 February 2015 at 16:01, jeremy ardley <jer...@gm...> wrote:
> I use a small snippet of code to open the OPAL device in a SIP voice
> application
>
> OpalHandle hOPAL;
>
> unsigned version;
>
> version = OPAL_C_API_VERSION;
>
> if ((hOPAL = OpalInitialise(&version, OPAL_PREFIX_SIP " TraceLevel=4"))
> == NULL)
>
> {
>
> fputs("Could not initialise OPAL\n", stderr);
>
> return false;
>
> }
>
> However the OPAL instance wants to open a V4L2 device and fails since I
> don't have one.
>
> Can I prevent the OPAL instance from trying to open a V4L device and
> instead open an ALSA device?
>
> What calls prior to the OplaInitialise are required? Or is using the
> wrapper functions not suitable for this and I should use low level
> calls? Or does it require compile time switches? In all cases is there a
> link or tutorial I can use?
>
> I did searches on the error message phrase and not found much of use
> other than similar messages from apps using OPAL. I also looked through
> the doxygen documentation but it's a bit obscure about this. I also
> installed a 4VL device and got it to work O.K. but my target application
> won't have V4L.
>
> Any advice appreciated.
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
|
|
From: Joseph R. <jro...@gm...> - 2015-02-19 05:05:15
|
Have you looked at any of the sample programs? I know those let you remove
codecs and choose output devices. I'm pretty sure you can restrict your
input devices as well. Why don't you take a look at those for this?
On Wed Feb 18 2015 at 9:02:42 PM jeremy ardley <jer...@gm...>
wrote:
> I use a small snippet of code to open the OPAL device in a SIP voice
> application
>
> OpalHandle hOPAL;
>
> unsigned version;
>
> version = OPAL_C_API_VERSION;
>
> if ((hOPAL = OpalInitialise(&version, OPAL_PREFIX_SIP " TraceLevel=4"))
> == NULL)
>
> {
>
> fputs("Could not initialise OPAL\n", stderr);
>
> return false;
>
> }
>
> However the OPAL instance wants to open a V4L2 device and fails since I
> don't have one.
>
> Can I prevent the OPAL instance from trying to open a V4L device and
> instead open an ALSA device?
>
> What calls prior to the OplaInitialise are required? Or is using the
> wrapper functions not suitable for this and I should use low level
> calls? Or does it require compile time switches? In all cases is there a
> link or tutorial I can use?
>
> I did searches on the error message phrase and not found much of use
> other than similar messages from apps using OPAL. I also looked through
> the doxygen documentation but it's a bit obscure about this. I also
> installed a 4VL device and got it to work O.K. but my target application
> won't have V4L.
>
> Any advice appreciated.
>
> ------------------------------------------------------------
> ------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&
> iu=/4140/ostg.clktrk
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
|
|
From: jeremy a. <jer...@gm...> - 2015-02-19 05:02:08
|
I use a small snippet of code to open the OPAL device in a SIP voice
application
OpalHandle hOPAL;
unsigned version;
version = OPAL_C_API_VERSION;
if ((hOPAL = OpalInitialise(&version, OPAL_PREFIX_SIP " TraceLevel=4")) == NULL)
{
fputs("Could not initialise OPAL\n", stderr);
return false;
}
However the OPAL instance wants to open a V4L2 device and fails since I
don't have one.
Can I prevent the OPAL instance from trying to open a V4L device and
instead open an ALSA device?
What calls prior to the OplaInitialise are required? Or is using the
wrapper functions not suitable for this and I should use low level
calls? Or does it require compile time switches? In all cases is there a
link or tutorial I can use?
I did searches on the error message phrase and not found much of use
other than similar messages from apps using OPAL. I also looked through
the doxygen documentation but it's a bit obscure about this. I also
installed a 4VL device and got it to work O.K. but my target application
won't have V4L.
Any advice appreciated.
|
|
From: Joseph R. <jro...@gm...> - 2015-02-07 03:32:40
|
HI Peter,
Take a look at the wiki page for how to build PTLIB and Opal. It also
has other useful information. Be very careful with the required
environmental variables.
http://wiki.opalvoip.org/
-JD
On Fri Feb 06 2015 at 7:18:27 PM Peter Morreale <pmo...@br...>
wrote:
> On Sat, 2015-02-07 at 11:02 +1100, Robert Jongbloed wrote:
> > That's very strange message. MP4V-ES is the MEGP4 video codec, and
> > very rare. In fact I would go so far as to say I have never seen
> > another client do it!
> >
> >
> > If using conopal you might try adding -D MPEG4 to command line to
> > remove it. I think that still works with simpleopal.
> >
> Just ran a quick test adding the above to simplopal.
>
> The h225 packet seems to have cleared wireshark as correct, both on the
> outbound host and the in-bound host.
>
> Thanks for that. Its a little step closer. I need to do more analysis
> to see where I am at now.
> >
> >
> > As an aside, that fact the you are using simpleopal and sine the
> > current stable release (Lacaille, 3.14.x) it is in a directory called
> > "deprecated", I am wondering if you are using an older version of
> > OPAL? If not, why are you using a program that is no longer supported
> > and discouraged from use, which is effectively what deprecated means
> > in this context.
> >
> I'm using 3.10.4, which is the default version supplied in the Debian
> Wheezy release. conopal is not available from the Debian repositories.
>
> I have not (yet) tried building from src. Is conopal in the
> http://sourceforge.net/projects/opalvoip/files/latest/download
>
> ptlib? Is there another set of sources I need?
>
> Appreciate the help, thank you.
>
> Kind Regards
> -PWM
>
>
>
> > Robert Jongbloed
> > OPAL/OpenH323/PTLib Architect and Co-founder.
> >
> >
> >
> > On 6 February 2015 at 10:14, Peter Morreale <pmo...@br...>
> > wrote:
> >
> > Hi all,
> >
> > I'm working on a router platform and am trying to generate
> > simple
> > h323/et al. traffic on a set of Debian Wheezy VMs.
> >
> > I'm able to simulate a call using simpleopal and SIP, however
> > when I try
> > the call using the h323 option, wireshark tells me that I'm
> > sending out
> > a bad h225 packet. "Malformed Packet: MP4V-ES"
> >
> > I generate the above with:
> >
> > % simpleopal h323:192.168.22.222
> >
> > and am listening with on another VM with:
> >
> > % simpleopal -l -t
> >
> > The goal here is to get the H* protocol handshaking passing
> > through the
> > router, nothing more. I'm not concerned about the RTP
> > traffic.
> >
> > Is this even possible using simpleopal? Are there some other
> > options I
> > can use? Barring that, is there some other H* test tool I
> > could use?
> >
> > My hope is to get the listener to the point of recognizing and
> > accepting
> > the call.
> >
> > Kind Regards,
> > -PWM
> >
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Dive into the World of Parallel Programming. The Go Parallel
> > Website,
> > sponsored by Intel and developed in partnership with Slashdot
> > Media, is your
> > hub for all things parallel software development, from weekly
> > thought
> > leadership blogs to news, videos, case studies, tutorials and
> > more. Take a
> > look and join the conversation now.
> > http://goparallel.sourceforge.net/
> > _______________________________________________
> > Opalvoip-user mailing list
> > Opa...@li...
> > https://lists.sourceforge.net/lists/listinfo/opalvoip-user
> >
> >
> > ------------------------------------------------------------
> ------------------
> > Dive into the World of Parallel Programming. The Go Parallel Website,
> > sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> > hub for all things parallel software development, from weekly thought
> > leadership blogs to news, videos, case studies, tutorials and more. Take
> a
> > look and join the conversation now. http://goparallel.sourceforge.net/
> > _______________________________________________
> > Opalvoip-user mailing list
> > Opa...@li...
> > https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
>
>
> ------------------------------------------------------------
> ------------------
> Dive into the World of Parallel Programming. The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Opalvoip-user mailing list
> Opa...@li...
> https://lists.sourceforge.net/lists/listinfo/opalvoip-user
>
|
|
From: Peter M. <pmo...@br...> - 2015-02-07 03:17:48
|
On Sat, 2015-02-07 at 11:02 +1100, Robert Jongbloed wrote: > That's very strange message. MP4V-ES is the MEGP4 video codec, and > very rare. In fact I would go so far as to say I have never seen > another client do it! > > > If using conopal you might try adding -D MPEG4 to command line to > remove it. I think that still works with simpleopal. > Just ran a quick test adding the above to simplopal. The h225 packet seems to have cleared wireshark as correct, both on the outbound host and the in-bound host. Thanks for that. Its a little step closer. I need to do more analysis to see where I am at now. > > > As an aside, that fact the you are using simpleopal and sine the > current stable release (Lacaille, 3.14.x) it is in a directory called > "deprecated", I am wondering if you are using an older version of > OPAL? If not, why are you using a program that is no longer supported > and discouraged from use, which is effectively what deprecated means > in this context. > I'm using 3.10.4, which is the default version supplied in the Debian Wheezy release. conopal is not available from the Debian repositories. I have not (yet) tried building from src. Is conopal in the http://sourceforge.net/projects/opalvoip/files/latest/download ptlib? Is there another set of sources I need? Appreciate the help, thank you. Kind Regards -PWM > Robert Jongbloed > OPAL/OpenH323/PTLib Architect and Co-founder. > > > > On 6 February 2015 at 10:14, Peter Morreale <pmo...@br...> > wrote: > > Hi all, > > I'm working on a router platform and am trying to generate > simple > h323/et al. traffic on a set of Debian Wheezy VMs. > > I'm able to simulate a call using simpleopal and SIP, however > when I try > the call using the h323 option, wireshark tells me that I'm > sending out > a bad h225 packet. "Malformed Packet: MP4V-ES" > > I generate the above with: > > % simpleopal h323:192.168.22.222 > > and am listening with on another VM with: > > % simpleopal -l -t > > The goal here is to get the H* protocol handshaking passing > through the > router, nothing more. I'm not concerned about the RTP > traffic. > > Is this even possible using simpleopal? Are there some other > options I > can use? Barring that, is there some other H* test tool I > could use? > > My hope is to get the listener to the point of recognizing and > accepting > the call. > > Kind Regards, > -PWM > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel > Website, > sponsored by Intel and developed in partnership with Slashdot > Media, is your > hub for all things parallel software development, from weekly > thought > leadership blogs to news, videos, case studies, tutorials and > more. Take a > look and join the conversation now. > http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user |
|
From: Robert J. <ro...@vo...> - 2015-02-07 00:31:17
|
Hmm, you are right, that got lost somewhere along the way. I have added that functionality back in. Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 6 February 2015 at 19:53, Alexander Sbitnev <ale...@gm...> wrote: > simpleopal is outdated as Robert states. Use conopal instead. > But it is not possible to put h323:192.168.22.222 in the conopal command > line though. > You can manually enter connect command from inside of conopal or start > it with a command script > if you don't want to type address each time. > And yes. Opal working fine with at least some of H323 capable devices. > Can't say how it works with NAT. > Try also faststart options. Maybe it will make a difference. > > On 02/06/2015 02:14 AM, Peter Morreale wrote: > > Hi all, > > > > I'm working on a router platform and am trying to generate simple > > h323/et al. traffic on a set of Debian Wheezy VMs. > > > > I'm able to simulate a call using simpleopal and SIP, however when I try > > the call using the h323 option, wireshark tells me that I'm sending out > > a bad h225 packet. "Malformed Packet: MP4V-ES" > > > > I generate the above with: > > > > % simpleopal h323:192.168.22.222 > > > > and am listening with on another VM with: > > > > % simpleopal -l -t > > > > The goal here is to get the H* protocol handshaking passing through the > > router, nothing more. I'm not concerned about the RTP traffic. > > > > Is this even possible using simpleopal? Are there some other options I > > can use? Barring that, is there some other H* test tool I could use? > > > > My hope is to get the listener to the point of recognizing and accepting > > the call. > > > > Kind Regards, > > -PWM > > > > > > > > > > > ------------------------------------------------------------------------------ > > Dive into the World of Parallel Programming. The Go Parallel Website, > > sponsored by Intel and developed in partnership with Slashdot Media, is > your > > hub for all things parallel software development, from weekly thought > > leadership blogs to news, videos, case studies, tutorials and more. Take > a > > look and join the conversation now. http://goparallel.sourceforge.net/ > > _______________________________________________ > > Opalvoip-user mailing list > > Opa...@li... > > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > |
|
From: Robert J. <ro...@vo...> - 2015-02-07 00:02:24
|
That's very strange message. MP4V-ES is the MEGP4 video codec, and very rare. In fact I would go so far as to say I have never seen another client do it! If using conopal you might try adding -D MPEG4 to command line to remove it. I think that still works with simpleopal. As an aside, that fact the you are using simpleopal and sine the current stable release (Lacaille, 3.14.x) it is in a directory called "deprecated", I am wondering if you are using an older version of OPAL? If not, why are you using a program that is no longer supported and discouraged from use, which is effectively what deprecated means in this context. Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 6 February 2015 at 10:14, Peter Morreale <pmo...@br...> wrote: > > Hi all, > > I'm working on a router platform and am trying to generate simple > h323/et al. traffic on a set of Debian Wheezy VMs. > > I'm able to simulate a call using simpleopal and SIP, however when I try > the call using the h323 option, wireshark tells me that I'm sending out > a bad h225 packet. "Malformed Packet: MP4V-ES" > > I generate the above with: > > % simpleopal h323:192.168.22.222 > > and am listening with on another VM with: > > % simpleopal -l -t > > The goal here is to get the H* protocol handshaking passing through the > router, nothing more. I'm not concerned about the RTP traffic. > > Is this even possible using simpleopal? Are there some other options I > can use? Barring that, is there some other H* test tool I could use? > > My hope is to get the listener to the point of recognizing and accepting > the call. > > Kind Regards, > -PWM > > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > |
|
From: Alexander S. <ale...@gm...> - 2015-02-06 08:53:10
|
simpleopal is outdated as Robert states. Use conopal instead. But it is not possible to put h323:192.168.22.222 in the conopal command line though. You can manually enter connect command from inside of conopal or start it with a command script if you don't want to type address each time. And yes. Opal working fine with at least some of H323 capable devices. Can't say how it works with NAT. Try also faststart options. Maybe it will make a difference. On 02/06/2015 02:14 AM, Peter Morreale wrote: > Hi all, > > I'm working on a router platform and am trying to generate simple > h323/et al. traffic on a set of Debian Wheezy VMs. > > I'm able to simulate a call using simpleopal and SIP, however when I try > the call using the h323 option, wireshark tells me that I'm sending out > a bad h225 packet. "Malformed Packet: MP4V-ES" > > I generate the above with: > > % simpleopal h323:192.168.22.222 > > and am listening with on another VM with: > > % simpleopal -l -t > > The goal here is to get the H* protocol handshaking passing through the > router, nothing more. I'm not concerned about the RTP traffic. > > Is this even possible using simpleopal? Are there some other options I > can use? Barring that, is there some other H* test tool I could use? > > My hope is to get the listener to the point of recognizing and accepting > the call. > > Kind Regards, > -PWM > > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user |
|
From: Peter M. <pmo...@br...> - 2015-02-05 23:45:30
|
Hi all, I'm working on a router platform and am trying to generate simple h323/et al. traffic on a set of Debian Wheezy VMs. I'm able to simulate a call using simpleopal and SIP, however when I try the call using the h323 option, wireshark tells me that I'm sending out a bad h225 packet. "Malformed Packet: MP4V-ES" I generate the above with: % simpleopal h323:192.168.22.222 and am listening with on another VM with: % simpleopal -l -t The goal here is to get the H* protocol handshaking passing through the router, nothing more. I'm not concerned about the RTP traffic. Is this even possible using simpleopal? Are there some other options I can use? Barring that, is there some other H* test tool I could use? My hope is to get the listener to the point of recognizing and accepting the call. Kind Regards, -PWM |
|
From: Robert J. <ro...@vo...> - 2015-01-05 22:19:34
|
There is always a transcoder from OpalPCM16 to OpalG711_ULAW_64K, so I am perplexed as to why it not able to establish the call. Can you send me a level 4 trace log? Don't post the log to the list, just send to me directly. Robert Jongbloed *OPAL/OpenH323/PTLib Architect and Co-founder*. On 5 January 2015 at 05:24, Henning Holtschneider <he...@lo...> wrote: > Happy new year everybody, > > I'm trying to make my fork of t38modem compatible with OPAL 3.14. The > current state of work is available at < > https://github.com/hehol/t38modem/tree/opal314>. > > The modified code compiles and starts up correctly and I'm able to > register with my SIP server. Unfortunately, I'm unable to make a successful > call (neither SIP->modem nor modem->SIP) because there seem to be internal > codec issues. The message coming from OPAL is: > > Call[C693736ba1] cleared (Call failed as could not find common media > capabilities) > > If I understand correctly, the problem is an internal codec mismatch > between the OpalEndPoint implemented in < > https://github.com/hehol/t38modem/blob/opal314/opal/modemep.cxx> and the > SIPEndPoint implemented in < > https://github.com/hehol/t38modem/blob/opal314/opal/sipep.cxx>. The > ModemEndPoint only supports the OpalPCM16 codec, whereas the SIPEndPoint > supports OpalG711_ULAW_64K, OpalG711_ALAW_64K and OpalT38. With OPAL 3.10, > no explicit transcoding was required for the connection to work but this > doesn't seem to be the case anymore. > > Can anyone provide some help on what changes are required to get the call > to work with OPAL 3.14? > > Thanks, > Henning Holtschneider > -- > LocaNet oHG - http://www.loca.net > Baroper Straße 239 b, D-44227 Dortmund > tel +49 231 91596-25, fax +49 231 91596-55 > > Registergericht Amtsgericht Dortmund HRA 14208 > Geschäftsführer Sven Haufe, Henning Holtschneider > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > |
|
From: Jan W. <ja...@wi...> - 2015-01-05 09:58:36
|
I am pleased to announce a new release of the GNU Gatekeeper, version 3.8, now available from http://www.gnugk.org/h323download.html. Please see the attached notes for details. This release includes source code suitable for (Linux, Windows, MacOS, FreeBSD, NetBSD, OpenBSD and Solaris) and executables for Linux. -- Jan Whats new in GnuGk 3.8 ? In response to the current wave of H.323 spam / hacking GnuGk 3.8 has a number of improvements to security related features and older versions should be updated. - endpoint IDs are now completely random and not as easily guessable as they were before - GnuGk is now using better random numbers in security relevant places - new authentication modules using LUA scripts called LuaAuth - new switch [RasSrv::ARQFeatures] CheckSenderIP=1 to make sure ARQs come from the same IP as the initial registration - FileIPAuth is now able to check ARQ messages - AliasAuth updated to work with H.460.18 endpoint - PrefixAuth was extended to support unregistered calls - SQLAuth can now operate on SrcInfo fields using %{SrcInfo} - improvements to the addpasswd utility for the new web interface Other new non-security related features include: - The CatchAll policy now rewrites the destination alias which makes it easier to send CatchAll calls to MCU rooms. - You can now filter out whole capability classes, eg. all video or H.239 capabilities if some of your endpoints have trouble handling them - A new switch [Gatekeeper::Main] MinH323Version= lets you set the H.323 version GnuGk identifies itself as using (up to the latest version 7). This is mainly to deal with endpoint that switch features when they believe they are talking to older endpoints (which one shouldn't be doing...) - a number bugs and crashes fixed Download from http://www.gnugk.org/h323download.html -- Jan Willamowius, Founder of the GNU Gatekeeper Project EMail : ja...@wi... Website: http://www.gnugk.org Support: http://www.willamowius.com/gnugk-support.html Relaxed Communications GmbH Frahmredder 91 22393 Hamburg Geschäftsführer: Jan Willamowius HRB 125261 (Amtsgericht Hamburg) USt-IdNr: DE286003584 |
41 messages has been excluded from this view by a project administrator.