On Apr 8, 2013, at 11:32 AM, SamyGo wrote: > Hi AG, > I understand your point, so in this matter we should not only consider the > latency between dispatcher and relay but also consider the processing > capability of both components as high CPS might require significant resources > on relays as well. >
The resources required on the relays don't affect how fast your proxy can handle SIP traffic. Since the proxy needs to ask the relay to allocate a pair of ports, the delay of the answer to this question is what could potentially increase the overall time for call processing. > Are there any particular areas which you can point out for me to optimize > this? > > Thanks > Sammy > > On Apr 7, 2013 6:40 PM, "Adrian Georgescu" <[email protected]> wrote: > As OpenSIPS core is not async, the whole chain of processing a message can > cause this. Practically, summing up all RTT for all your database queries, > DNS lookups, Radius requests, media reservations can cause this. > > The farther away each component is the poorest the performance as that child > cannot process any new packet until is done with the previous. > > Adrian > > On Apr 7, 2013, at 3:27 PM, SamyGo wrote: > >> Hi Sir, >> Yes, we've optimized our opensips to have enough shared memory as well as >> the number of children have been increased as well but this situation is >> still the same. >> >> What I can logically think why this is happening is as follow: >> >> 1- Media-relays are in another DC, >> 2- Dispatcher queries relays to get the port info to update the SDP with >> >> The delay or slowness of relays might be something causing overall queue >> length to shoot up. >> >> Let me know what you think, >> >> -- >> Sammy >> >> >> >> On Sat, Apr 6, 2013 at 2:43 AM, Muhammad Shahzad <[email protected]> >> wrote: >> Well, if you have very high CPS then typically need more opensips children >> processes to handle load. So you need to, >> >> 1. increase no. of children. >> 2. optimize per child and shared memory sizes. >> >> BTW what does it has to do with media proxy as you are reporting SIP UDP >> port only gets hanged? >> >> Thank you. >> >> >> >> On Fri, Apr 5, 2013 at 8:42 PM, SamyGo <[email protected]> wrote: >> Hello, >> >> I'm working with opensips with heavy CPS, recently I added >> mediaproxy-dispatcher on the server and couple of relays on different >> servers in different Data Center. Everything worked fine until we observed >> that opensips SIP UDP port 5060 got huge queued packets. >> >> That obviously impacts the call processing. I want to know if this is a >> usual behavior? or can this be treated/tuned ? >> >> Thanks, >> Sammy >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> >> -- >> Mit freundlichen Grüßen >> Muhammad Shahzad >> ----------------------------------- >> CISCO Rich Media Communication Specialist (CRMCS) >> CISCO Certified Network Associate (CCNA) >> Cell: +49 176 99 83 10 85 >> MSN: [email protected] >> Email: [email protected] >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Saúl Ibarra Corretgé AG Projects _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
