This fixed mine.
onreply_route[1] {
# Not all 2xx messages have a content body so here we
# make sure our Content-Length > 0 to avoid a parse error
if (status=~"(180)|(183)|2[0-9][0-9]") {
if (!search("^Content-Length:\ 0")) {
force_rtp_proxy();
};
};
if (nat_uac_test("1")) {
fix_nated_contact();
};
}
--- Ladislav Andel <ladia6(a)centrum.cz> wrote:
Hi everybody,
I'm trying to get SER working and I get these errors(below) during running of SER.
I've already found an answer in the list, but still don't know when this
situation happen.
After this, all UA's cannot register with SER.
Would anybody be able to tell me how can I fix this.
how can I set sending only INVITE, 183 and 200 messages to the rtpproxy?
I'm using nathelper.cfg from source package with minor changes.
Thanks for help
Ladia
This is from syslog:
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: extract_body: message body has
lenght
zero
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: force_rtp_proxy2: can't
extract body
from the message
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: on_reply processing failed
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: extract_body: message body has
lenght
zero
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: force_rtp_proxy2: can't
extract body
from the message
Dec 2 21:31:44 linux /usr/local/sbin/ser[9313]: ERROR: on_reply processing failed
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
__________________________________
Do you Yahoo!?
Jazz up your holiday email with celebrity designs. Learn more.
http://celebrity.mail.yahoo.com