7 Oct
2015
7 Oct
'15
8:54 p.m.
Can you add log_prefix to print the callid, message type (request/reply)
and cseq header with each log message? That should reveal what sip
message is processed when such case happens.
I will look also at the code, maybe the stats are not decreased in such
case. If the transactions are staying in memory, then the share memory
usage is going to increase as well. Have you observed share memory
evolution?
Cheers,
Daniel
On 07/10/15 18:52, Daniel Tryba wrote:
On Wednesday 07 October 2015 18:19:25
Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
How many outgoing branches can there be? More
than 12?
I didn't configure this, so the default whatever that is.
There are no explicit branches, the called trunk might have more that 1 AoR,
so there may be parallel forks.
This worked fine for a couple of million testcalls, but field testing with an
actual trunk that makes less that 100 calls per day this problem triggered
twice in 3 weeks (out of nowhere as far as I can see).
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users