Oh, namesevers.... Sorry it my fault. I just set #define PJ_IOQUEUE_MAX_HANDLES 5000 in config_site.h, I still have same error. Maybe I do something wrong? I prefer to recreate transport and not whole stack... ________________________________ From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of Benny Prijono Sent: Wednesday, August 27, 2008 1:55 PM To: pjsip list Subject: Re: Network card added or enabled after app init problem On Wed, Aug 27, 2008 at 11:12 AM, Ilya Kalinin <ilyak at skuku.com> wrote: LOG: Aug 27 12:49:48 DEBUG pjsip [resolver.c]: Nameserver 0.0.0.0:53 state changed Active --> Probing You don't seem to have the nameserver IP address configured properly there, and this doesn't seem to have anything to do with transport (i.e. you'll get this error even if you don't change the transport). Also if close transport with pjsua_transport_close() with "force" set to non-zero, do I destroy this transport completely? Yes. But it's generally a bad idea to do this, as some objects transactions may still reference it so it may lead to crash. If you omit the transport, then it will be destroyed once it's safe to do so, that is when it's reference counter reaches zero. Because if I create and close transport some limited number of times I get an error: Error creating transport: Too many objects of the specified type (PJ_ETOOMANY) [status=70010] That's true, I presume because the old transport are still alive since there are objects that reference it. IMO this is fine, I don't think people will want to change NIC every seconds or so. But if you want to recreate the transport so many times, then you'd also want to increase some limits such as PJ_IOQUEUE_MAX_HANDLES. As I said previously, destroying and recreating the stack is indeed the easiest option and you'll avoid all these troubles. Cheers Benny -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080827/a9a80908/attachment-0001.html
