20 Sep
2005
20 Sep
'05
12:52 a.m.
Hi All
I hope someone can help me with an issue I"ve had since installing ser. For
some reason, whenever I call fix_nated_sdp or force_rtp_proxy I get the
following errors
Sep 19 10:31:06 localhost ser[3921]: Mon Sep 19 10:31:06 2005 18 a.b.c.d
62141 ****** Fixing NAT on reply with rtp
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: fix_nated_sdp: cannot extract
body from msg!
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: force_rtp_proxy2: can't extract
body from the message
Sep 19 10:31:06 localhost ser[3921]: ERROR: on_reply processing failed
Here is the part of the script that is generating the error
onreply_route[1] {
xlog("L_ALERT", "%Tf %mf ****** On Reply From: <%si>
<%tu> <%fu>
<%rm> <%rs> <%rr>\n");
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")) {
fix_nated_contact();
force_rport();
};
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")
&&
src_port>=10000) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing NAT
on reply with rtp\n");
fix_nated_sdp("3");
force_rtp_proxy();
} else if(status=~"[12][0-9][0-9]" &&
nat_uac_test("19")) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing NAT on
reply
with sdp\n");
fix_nated_sdp("3");
};
}
Any help would be appreciated.
Thanks
Rick
20 Sep
20 Sep
12:59 a.m.
Rick,
Not all messages will have an SDP payload. In other words the
<Content-Length> head may be zero for some messages.
If you call fix_nated_contact() for these types of message then you
will see these sorts of errors.
We usually do some tests on the SIP message prior to calling these NAT
functions. Check out the Getting Started document www.onsip.org for a
good NAT traversal example.
Regards,
Paul
On 9/19/05, Rick Thompson <rthompson(a)vir2com.com> wrote:
Hi All
I hope someone can help me with an issue I"ve had since installing ser. For
some reason, whenever I call fix_nated_sdp or force_rtp_proxy I get the
following errors
Sep 19 10:31:06 localhost ser[3921]: Mon Sep 19 10:31:06 2005 18 a.b.c.d
62141 ****** Fixing NAT on reply with rtp
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: fix_nated_sdp: cannot extract
body from msg!
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: force_rtp_proxy2: can't extract
body from the message
Sep 19 10:31:06 localhost ser[3921]: ERROR: on_reply processing failed
Here is the part of the script that is generating the error
onreply_route[1] {
xlog("L_ALERT", "%Tf %mf ****** On Reply From: <%si>
<%tu> <%fu>
<%rm> <%rs> <%rr>\n");
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")) {
fix_nated_contact();
force_rport();
};
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")
&&
src_port>=10000) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing
NAT
on reply with rtp\n");
fix_nated_sdp("3");
force_rtp_proxy();
} else if(status=~"[12][0-9][0-9]" &&
nat_uac_test("19")) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing NAT on
reply
with sdp\n");
fix_nated_sdp("3");
};
}
Any help would be appreciated.
Thanks
Rick
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
12:48 p.m.
Thanks Paul
Ser is new to me and the script I'm using was developed by another person
but I have one question.
I know that in this statement
if(method!="REGISTER") {.....};
the ! means not equal to but what is it used for in this statement
if (!lookup("location")) {.....};
and is ; always required unless it's the last curly bracket in the section?
----Original Message-----
From: Paul Hazlett [mailto:javarockx@gmail.com]
Sent: Monday, September 19, 2005 10:59 AM
To: rthompson(a)vir2com.com
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] sdp and rtp errors
Rick,
Not all messages will have an SDP payload. In other words the
<Content-Length> head may be zero for some messages.
If you call fix_nated_contact() for these types of message then you
will see these sorts of errors.
We usually do some tests on the SIP message prior to calling these NAT
functions. Check out the Getting Started document www.onsip.org for a
good NAT traversal example.
Regards,
Paul
On 9/19/05, Rick Thompson <rthompson(a)vir2com.com> wrote:
Hi All
I hope someone can help me with an issue I"ve had since installing ser.
For
some reason, whenever I call fix_nated_sdp or
force_rtp_proxy I get the
following errors
Sep 19 10:31:06 localhost ser[3921]: Mon Sep 19 10:31:06 2005 18 a.b.c.d
62141 ****** Fixing NAT on reply with rtp
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: fix_nated_sdp: cannot extract
body from msg!
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: force_rtp_proxy2: can't
extract
body from the message
Sep 19 10:31:06 localhost ser[3921]: ERROR: on_reply processing failed
Here is the part of the script that is generating the error
onreply_route[1] {
xlog("L_ALERT", "%Tf %mf ****** On Reply From: <%si>
<%tu> <%fu>
<%rm> <%rs> <%rr>\n");
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")) {
fix_nated_contact();
force_rport();
};
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")
&&
src_port>=10000) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing
NAT
on reply with rtp\n");
fix_nated_sdp("3");
force_rtp_proxy();
} else if(status=~"[12][0-9][0-9]" &&
nat_uac_test("19")) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing NAT on
reply
with sdp\n");
fix_nated_sdp("3");
};
}
Any help would be appreciated.
Thanks
Rick
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
21 Sep
21 Sep
1:39 a.m.
!= means "not equal"
! by itself means the inverse of the result, like in C, where !TRUE ==
FALSE and !FALSE == TRUE
I'd recommend you get that Getting Started document from www.onsip.org
if you new to SER because it is a rather complex project.
Regards,
Paul
On 9/19/05, Rick Thompson <rthompson(a)vir2com.com> wrote:
Thanks Paul
Ser is new to me and the script I'm using was developed by another person
but I have one question.
I know that in this statement
if(method!="REGISTER") {.....};
the ! means not equal to but what is it used for in this statement
if (!lookup("location")) {.....};
and is ; always required unless it's the last curly bracket in the section?
----Original Message-----
From: Paul Hazlett [mailto:javarockx@gmail.com]
Sent: Monday, September 19, 2005 10:59 AM
To: rthompson(a)vir2com.com
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] sdp and rtp errors
Rick,
Not all messages will have an SDP payload. In other words the
<Content-Length> head may be zero for some messages.
If you call fix_nated_contact() for these types of message then you
will see these sorts of errors.
We usually do some tests on the SIP message prior to calling these NAT
functions. Check out the Getting Started document www.onsip.org for a
good NAT traversal example.
Regards,
Paul
On 9/19/05, Rick Thompson <rthompson(a)vir2com.com> wrote:
Hi All
I hope someone can help me with an issue I"ve had since installing ser.
For
some reason, whenever I call fix_nated_sdp or
force_rtp_proxy I get the
following errors
Sep 19 10:31:06 localhost ser[3921]: Mon Sep 19 10:31:06 2005 18 a.b.c.d
62141 ****** Fixing NAT on reply with rtp
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: fix_nated_sdp: cannot extract
body from msg!
Sep 19 10:31:06 localhost ser[3921]: ERROR: extract_body: message body has
length zero
Sep 19 10:31:06 localhost ser[3921]: ERROR: force_rtp_proxy2: can't
extract
body from the message
Sep 19 10:31:06 localhost ser[3921]: ERROR: on_reply processing failed
Here is the part of the script that is generating the error
onreply_route[1] {
xlog("L_ALERT", "%Tf %mf ****** On Reply From: <%si>
<%tu> <%fu>
<%rm> <%rs> <%rr>\n");
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")) {
fix_nated_contact();
force_rport();
};
if(status=~"[12][0-9][0-9]" && nat_uac_test("19")
&&
src_port>=10000) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing
NAT
on reply with rtp\n");
fix_nated_sdp("3");
force_rtp_proxy();
} else if(status=~"[12][0-9][0-9]" &&
nat_uac_test("19")) {
xlog("L_ALERT", "%Tf %mf %si %sp ****** Fixing NAT on
reply
with sdp\n");
fix_nated_sdp("3");
};
}
Any help would be appreciated.
Thanks
Rick
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
7078
days inactive
7079
days old
3 comments
2 participants
participants (2)
-
Paul Hazlett -
Rick Thompson