Re: [reSIProcate] DnsResult::lookupInternal assert(0)
The resiprocate project has moved to https://svn.resiprocate.org/rep/
resiprocate/main, so you won't be able to get the latest revisions at
sipfoundry.org anymore.
Best regards,
Byron Campen
Hello,
Thank you for taking the time to look into this,
Sorry what is the revision I should use?
Currently I am using 6800 checked out from "https://
scm.sipfoundry.org/rep/resiprocate/main"
Thank you again!
Julien
Ok, I have committed a fix. Give it a shot just to make sure
your problem is solved.
Best regards,
Byron Campen
After a quick look, I am convinced this is a bug in
DnsResult. It
appears to be triggered when you attempt to resolve a uri with a
non-
numerical hostname, a specified port, no transport param, with
scheme
sip, in a stack that does not have a UDP transport. Does this match
your situation? I will try to have a fix sometime this morning.
Best regards,
Byron Campen
Hello everyone,
I am having some problems when calling stack->process(fdset);
I often get an assertion error inside DnsResult:lookupInternal
(line 330)
Could someone give me some informations on how to avoid this
assertion
error?
Sorry to be so vague, but I am having trouble identifying the cases
when
this assertion occur...
Thank you for your help
else // port specified so we know the transport
{
mPort = uri.port();
if (mInterface.isSupported(mTransport, V6) ||
mInterface.isSupported(mTransport, V4))
{
lookupHost(mTarget);
}
else
{
-> assert(0);
if (mHandler) mHandler->handle(this);
}
}
--Julien Saito
ジュリアン 齋藤
julien@xxxxxxxxxxx
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxxx
https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
--
Julien Saito
ジュリアン 齋藤
julien@xxxxxxxxxxx