[reSIProcate] REFER
Resip Team,
Does the resip stack support the REFER method? When I send a REFER to the resip stack it replies with a 405 method not understood/supported.
PM
On Mar 28, 2005, at 4:31 PM, Scott Godin wrote:
Yes - I did that at the same time.
-----Original Message-----
From: Mariano Stokle [mailto:mstokle@xxxxxxxxx]
Sent: Monday, March 28, 2005 4:46 PM
To: Scott Godin
Cc: jason@xxxxxx; resiprocate-devel@xxxxxxxxxxxxxxxxxxx; Dennis Dupont
Subject: Re: [reSIProcate] Re: Building problem with resiprocate 0.5.0
BTW, the abstract method is need to be implemented is:
onRequestRetry from ClientRegistrationHandle class. I implemented an
empty method.
Regards,
On Mon, 28 Mar 2005 12:34:01 -0500, Scott Godin <slgodin@xxxxxxxxxxxx>
wrote:
I've committed this fix - thanks.
-----Original Message-----
From: Mariano Stokle [mailto:mstokle@xxxxxxxxx]
Sent: Sunday, March 27, 2005 5:31 PM
To: jason@xxxxxx
Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx; Dennis Dupont
Subject: Re: [reSIProcate] Re: Building problem with resiprocate 0.5.0
Hi again,
I was doing some research and got the answer. Here is the diff file:
440c440
< auto_ptr<AppDialogSetFactory> uac_dsf(new testAppDialogSetFactory);
---
auto_ptr<testAppDialogSetFactory> uac_dsf(new
testAppDialogSetFactory);
482c482
< auto_ptr<AppDialogSetFactory> uas_dsf(new testAppDialogSetFactory);
---
auto_ptr<testAppDialogSetFactory> uas_dsf(new
testAppDialogSetFactory);
Regards,
On Sun, 27 Mar 2005 18:12:00 -0300, Mariano Stokle <mstokle@xxxxxxxxx>
wrote:
Hi,
me again. Thanks for your comments. I finally could build both
libraries, resiprocate and dum. Test applications also worked. I am
analysing now BasicCall.cxx. When I trie to compile, I found some
errors with abstract functions I solved in TestUac and TestUas
classes, but I could not figured out about this:
BasicCall.cxx:428: error: no matching function for call to `
std::auto_ptr<resip::AppDialogSetFactory>::auto_ptr(
std::auto_ptr<resip::AppDialogSetFactory>)'
/usr/include/g++/memory:334: error: candidates are:
std::auto_ptr<_Tp>::auto_ptr(std::auto_ptr_ref<_Tp>) [with _Tp =
resip::AppDialogSetFactory]
/usr/include/g++/memory:204: error:
std::auto_ptr<_Tp>::auto_ptr(std::auto_ptr<_Tp1>&) [with _Tp1 =
resip::AppDialogSetFactory, _Tp = resip::AppDialogSetFactory]
/usr/include/g++/memory:192: error:
std::auto_ptr<_Tp>::auto_ptr(std::auto_ptr<_Tp>&) [with _Tp =
resip::AppDialogSetFactory]
BasicCall.cxx:428: error: initializing argument 1 of `void
resip::DialogUsageManager::setAppDialogSetFactory(std::auto_ptr<resip::AppDi
alogSetFactory>)
' from result of `std::auto_ptr<_Tp>::operator std::auto_ptr<_Tp1>()
[with
_Tp1 = resip::AppDialogSetFactory, _Tp = testAppDialogSetFactory]'
I am not an expert about auto_ptr, so I am askin for S.O.S. here. Any
one has introduced any changes in the code to make it work?
Regards,
Mariano
On Fri, 25 Mar 2005 08:33:37 -0800, Fischl jason
<jason.fischl@xxxxxxxxx>
wrote:
Hi all,
I think I inadvertently didn't reply my answer to the main list. The
autotools build system is currently broken. I recommend that you use
the default build system which can be used by just typing make. Have a
look at sip/build/Makefile.conf if you want to customize the build
(e.g. build shared libraries, enable IPV6, SSL, DTLS, etc.)
The problem you are seeing occurs because gperf is not installed on
your system. After installing gperf, delete the file MethodHash.cxx
and everything will be ok. Alternatively, delete MethodHash.cxx and
rerun svn update. The build should be fine after that.
If somebody knows how to hack the Makefile to solve this problem, it
would be great. The problem occurs because svn timestamps the files to
the time of the checkout instead of the time of the checkin
(differently from cvs). As a result, make decides that it needs to
rebuild MethodHash.cxx from MethodHash.gperf. If gperf doesn't exist,
it produces an empty file.
jason
On Fri, 25 Mar 2005 07:23:05 -0600, Dennis Dupont
<ddupont@xxxxxxxxxxxxxxx> wrote:
Mariano
I was seeing the same problems. I started over yesterday (3/24)
with
a
fresh copy
from svn. This time I did *not* use autotools, I just ran make. I
was
able to build
libresiprocate.a and libdum.a that way (using make -k). However,
none
of the test
programs would build. I am getting the following link error:
../../build/../resiprocate/obj.debug.Linux.i686/libresiprocate.a(MethodT
ypes.o)(.text+0x78): In function `resip::getMethodType(char const*,
int)':
/home/ddupont/devel/resiprocate-050319/main/sip/resiprocate/MethodTypes.
cxx:62: undefined reference to `resip::MethodHash::in_word_set(char
const*, unsigned)'
Dennis Dupont
Senior Systems Architect
Intelemedia Communications, Inc.
-----Original Message-----
From: Mariano Stokle [mailto:mstokle@xxxxxxxxx]
Sent: Thursday, March 24, 2005 7:16 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Re: Building problem with resiprocate 0.5.0
I solved that rpoblem forcing to rebuild ARES. Now I found another:
There is no relue defined to build target "Dialog.cxx" necessary for
"Dialog.lo"
Anyone with same problem?
On Thu, 24 Mar 2005 18:45:04 -0300, Mariano Stokle
<mstokle@xxxxxxxxx>
wrote:
Hi,
I just updated resiprocate using svn to Revision 4045. I
followed the regular procedure to build using autotools: at sip:
sh use-autotools.sh
sh autogen.sh
and then at sip/compile:
../configure -C --enable-shared --enable-ipv6
--enable-data-local-size=16 --disable-elog
then:
make
but I got an error in AresDns.cxx
../../resiprocate/AresDns.cxx:12:2: #error Must have ARES
I did not have this problem before..Any one had this problem?
--
Mariano Stokle
SIP Rules
--
Mariano Stokle
SIP Rules
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
--
Mariano Stokle
SIP Rules
--
Mariano Stokle
SIP Rules
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
--
Mariano Stokle
SIP Rules
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel