27 May
2008
27 May
'08
10:31 a.m.
Hi Peter,
This is what I call a good news :).
Usually this is the main problem when you have multiple systems
integrated in only one platform - at a point, if something goes wrong,
it is not obviously (not to say difficult) to say who's fault is - and
this because the effects are more visible than the cause itself ;)
Regards,
Bogdan
Peter Lemenkov wrote:
Hello All!
2008/5/27 Bogdan-Andrei Iancu <bogdan(a)voice-system.ro>ro>:
Hi Peter,
First you need to find out if the delay comes from the network or from
processing - just print a timestamp in the beginning of the request route
and compare it with the timestamp from ngrep/tcpdump - by doing this you
will find out if the message is delayed at socket level.
If the delay is in script, use benchmark or timestamps to locate the area
that uses the largest amount of time.
Folks, I'm really sorry for noise - after some debugging and testing
we found that this is a definitely an issue with our software. More
particularly, there is a bug in our Oracle PL/SQL-scripts. We did some
mistakes that can be visible only under heavy load.
OpenSER is still reliable and stable :)