On 04/08/15 16:41, Daniel Tryba wrote:
On Tuesday 04 August 2015 15:12:31 Daniel-Constantin Mierla wrote:
Anyhow, I can't remember any changes in ack processing that could add to this. Are you doing accounting of ACK requests?
Ehh, yes, accounting in mysql. That explains +/- 0.01 delay in routing the ACK. I think the previously it was myisam with db_insert_mode set to 1.
You can set the type of acc module to myisam -- we removed enforcing myisam, leaving it to the default setting of mysql server, it is not something like acc must not be myisam anymore.
Cheers, Daniel
I see there is now a 2 as value for db_insert_mode, to do this async. Sounds like the solution.
As of a solution, perhaps hash table comes handy again, filter on this customer and then of the ack and 2nd invite are received in really short time in between, then add some usleep() for invite, that should take the cpu from the process handling it.
I'm just usleeping for 5ms on all INVITEs within dialog for now. I'll look into the async inserting as the permanent solution.
Once again many thanks for your reply.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users