Hi Chris,
What svn version are you using?
The first critical log appears when you try a BYE for a dialog in EARLY
state (without a 200OK). But this
errors should have been suppressed in the latest svn version.
The second error appears because there are two dialog identifiers in the
received command and OpenSIPS doesn't handle them properly.
The last error appears when an error occurs in RTPProxy. The latest svn
verison also has implemented proper handling of RTPProxy errors.
Regards,
Razvan Crainea
OpenSIPS Developer
On 27.06.2011 11:01, Chris Martineau wrote:
Hi,
Just doing some load testing on 1.7 and I am getting the following
errors occurring.
CRITICAL:dialog:log_next_state_dlg: bogus event 7 in state 2 for dlg
........
ERROR:rtpproxy:timeout_listener_process: Wrong formatted message
received from rtpproxy [118.921329779 1529.1978833588 ]
I also get a lot more
ERROR:rtpproxy:force_rtp_proxy_body: incorrect port 0 in reply from
rtp proxy?
The only obvious problems this seems to be causing is incorrectly time
stamped cdr records where the timestamp contains 0.
Any ideas as to what this can be?
Regards
Chris
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
