Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - billsimon

Pages: [1]
Other Yate server issues / Optimize TCP SIP accounts
« on: June 25, 2018, 12:27:11 PM »
I am running a large number of TCP SIP accounts (outbound registrations from yate to provider) and looking for ways to optimize. I believe the problem is too many threads.

On a 4-core server the CPU is saturated with 700 outbound TCP registrations, no calls.

On an 8-core server I can handle up to 1000 outbound TCP registrations.

When I was previously running a large number of jabber client registrations they were easily handled by a 1- or 2- core server, more than 1000 registrations per server.

Thanks for your advice. For this specific routing need I was not able to do it with the register module but accomplished it fine with Javascript.

Thank you Monica. I am doing everything else with register.conf and regexroute and hate to load Javascript just for this. Does Javascript perform better than register or regexroute? If so I may try to convert my logic.

If I dispatch a database message from regexroute, e.g.

^1$=dispatch database;account=something;query=SELECT ...;results=true

how do I get the SELECT results out of the message answer?

Yate bugs / Re: SIP SRV lookup
« on: March 16, 2015, 09:36:46 AM »
Thank you!

Yate bugs / Re: SIP SRV lookup
« on: March 16, 2015, 09:14:26 AM »
Yes, I know.

I would be most grateful if you would fix this. :)

SRV lookup is standard procedure since 2002 (RFC 3263).

Yate bugs / SIP SRV lookup
« on: March 13, 2015, 10:56:02 AM »
Yate does not appear to look up SRV records when sending a call to a SIP URI. Examination of the SIP debug log shows that it looks up only the A record of the host part of the URI and does not perform a SRV lookup.

Yate bugs / Yate crash from yjinglechan
« on: December 07, 2012, 01:58:08 PM »
On a daily basis Yate (from current SVN) is crashing with the following error in syslog:

Code: [Select]
kernel: YJGEngineWorker[9350]: segfault at 7fd4c0ec7e90 ip 00007fd4c0ec7e90 sp 00007fd50cbe6a68 error 15
and this error in the Yate log:

Code: [Select]
Supervisor: child 9342 died on signal 11
I have turned up debug to level 10 on jingle and am waiting for another failure to see if any additional information is available. Has anyone else seen crashing due to yjinglechan in current SVN?

Pages: [1]