Hi Benny, Thanks for your quick reply. Following is the error traces which I just got after enabling traces in pjmedia stack. 17:03:53.283 transport_udp. Binding rtp port 4112 to socket 178 17:04:05.143 transport_udp. In udp Rtp key: rtp socket to be invalidated 178 17:04:05.143 ioq_select In pj_ioqueue_unregister: closing socket 178 17:04:05.453 transport_udp. Binding rtp port 4112 to socket 178 17:04:05.453 transport_udp. pj_sock_socket ERR3 120098 As you can see from the last three lines that the same socket and ports are getting closed and the getting reopened within same second.I just have a feeling that might be that previous port was not yet closed but we trying to reopen it which might be giving this error. Your comments ! Regards, Parveen Jain On Thu, Aug 26, 2010 at 8:48 AM, Benny Prijono <bennylp at teluu.com> wrote: > On Wed, Aug 25, 2010 at 6:08 PM, Parveen Kumar Jain > <parveen.jain at one97.net> wrote: > > Hi All, > > I am trying to evaluate "pjmedia" project from quite some time for one > of > > my IVR based solution.The Application initiates bulk sip calls and then > > starts the media using pjmedia stack.I am facing following issue while > its > > usage in this way: > > - I was trying to use it one of my Bulk call scenario where I was trying > to > > make 40 G729 calls(I am using intel IPP for achieving that).but pjmedia > > gives socket bind error after some uncertain time period(sometime I don't > > get this error even after 2 days of testing but sometime I get it after > 2-3 > > hours of testing).Just to add this, my local UDP port management is fine > > where I ask pjmedia to bind only those rtp/rtcp ports which are not > already > > in use. > > The bind() error comes from the OS, so I'd say there's something wrong > with your port management. > > > Though I have found a very interesting fact while compiling the pjmedia. > I > > found that "sock_bsd.c" is getting compiled on my linux system, as I was > > expecting it should have been ''sock_linux_kernel.c".can this be a cause > of > > this "bind error" behavior ? > > The "bsd" stands for BSD socket API, not BSD OS, so it's the right > implementation to use. The "linux_kernel" stuff is for running PJLIB > inside Linux kernel, something that we used to support in the old > days. > > It's been long time since I tested bulk calling, I've forgotten what > the result was, so I'll let others comment on your questions below. > > -Benny > > > Besides, I have a few more questions regarding its usage for bulk > calling: > > - Is someone already tried to use it in this way or I mean if anybody > tried > > to use it for making bulk calls ? > > - What are the maximum simultaneous calls it can support using > G711U/G711A > > on a dual core Intel based Linux system(if someone has tried to do so) ? > > Also what would be its call rate if try to use it using G729 ? > > > > > > Regards, > > Parveen Jain > > _______________________________________________ > > Visit our blog: http://blog.pjsip.org > > > > pjsip mailing list > > pjsip at lists.pjsip.org > > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > -- Parveen Jain Technical Lead ? Network Engineering One97 Communications (P) Ltd B121, Sector 5, Noida, UP 201301 P: + 91 120 4770770 Extn:352 M: + 91 9212708203 W: www.one97world.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20100827/c0f119da/attachment.html>
