This is not going to be a bottleneck… Your going down the wrong road chasing this. Mike On Sep 30, 2013, at 4:05 PM, Cal Leeming [Simplicity Media Ltd] <cal.leeming@simplicitymedialtd.co.uk> wrote:
Any idea why libsofia only handles 1 thread per profile?
As mentioned before, you should run multiple profiles if this becomes a bottleneck, but running multiple profiles for inbound calls might not be suitable (i.e. if a provider gives you a number and will only send traffic to 1 IP/port at a time).
Are there any other alternative workarounds?
Cal
On Mon, Sep 30, 2013 at 8:36 PM, Guillermo Ruiz Camauer <grcamauer@gmail.com> wrote: Steven,
Ah, I think I get it now: profiles LISTEN on an IP:PORT combination, so I can have many IP:PORT combinations to MAKE calls, as long as I send them to my provider's IP on the 5060 port, but I would only receive calls from my provider on my one profile bount to the IP:5060 port. Is this correct?
Guillermo
On Mon, Sep 30, 2013 at 4:11 PM, Steven Ayre <steveayre@gmail.com> wrote: If I only have one Voip provider, can I still have more than one SIP profile? My provider authenticates via IP
Profiles bind to a single ip:port combination.
You could run multiple profiles each on a separate port. That way they'll all send to the provider using the same IP.
On 30 September 2013 18:54, Guillermo Ruiz Camauer <grcamauer@gmail.com> wrote: In the Wiki, under "Performance testing and configurations", one of the suggestions given under "Recommended SIP Settings" is:
libsofia only handles 1 thread per profile, so if that is your bottle neck use more profiles
If I only have one Voip provider, can I still have more than one SIP profile? My provider authenticates via IP. I currently run 240 concurrent calls through this Sip trunk, I I see CPU close to 12.5% on a 8 core machine. This means that one core is maxing out. How can I get more threads up to distribute the load?