12 Sep
2005
12 Sep
'05
2:02 p.m.
Andreas Granig wrote:
Klaus Darilion wrote:
I couldn't find the SIP message yet. It happens when testing against
protos. Sometimes after 50 requests, sometimes after 4000 requests.
regards
klaus
1. Sometime the UDP threads get screwed up. Fifo
and TCP threads are
still working (also TCP in and UDP out) but UDP packets sent to
openser are not processed.
Could this be related to the problem I reported here?
http://mail.iptel.org/pipermail/serusers/2005-September/023638.html
What exactly does happen in your case? Does the load also go up? What's
the SIP message which screws up SER? 2. Sometimes
the tm module rans out of memory. The tm module keeps old
transactions in memory but apparently it does not delete them when
they get expired.
Hmm... I've 2GB of RAM for the SER hosts, but I've to restart SER every
other week or so because it eats up quite a lot of memory.
But bugs haven't appeared yet in normal
usage, but when testing
against the protos test suite.
We've some Cisco ATA 186 running with a 3.1.1 firmware, and they quite
often send broken SIP messages ("%d" instead of ports and so on). Maybe
these sometimes cause the errors, but I'm not sure.
Andy