Hi,
We have deployed many Cisco ATAs behind NAT devices. In order to keep the NAT session binding alive, we enabled a feature on the ATAs that basically send a small dummy packet to SER every 90 seconds. Everything works great. The question is, how can I suppress the WARNING/ERRORS that these dummy packets present to the SYSLOG? Is there a simple way to do this in the ser.cfg file?
These are the SYSLOG messages:
May 1 09:20:58 maui /usr/sbin/ser[23389]: WARNING: upstream bug - 0-terminated packet May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_first_line: message too short: 3 May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR:parse_first_line: bad message May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_msg: message=<> May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: receive_msg: parse_msg failed
Thanks, Ricardo
At 04:35 PM 5/1/2003, Ricardo Villa wrote:
Hi,
We have deployed many Cisco ATAs behind NAT devices. In order to keep the NAT session binding alive, we enabled a feature on the ATAs that basically send a small dummy packet to SER every 90 seconds.
Out of curiosity: how did you exactly make the ATAs to send the keep-alives for you? Did you write your own image?
Everything works great. The question is, how can I suppress the WARNING/ERRORS that these dummy packets present to the SYSLOG? Is there a simple way to do this in the ser.cfg file?
Send some SIP keep-alive messages. SER drops non-SIP messages. If you are sorry about too large messages, you could generate such which include only first line and topmost via (elements which are always checked) and include a method check in script, which drops them.
-Jiri
These are the SYSLOG messages:
May 1 09:20:58 maui /usr/sbin/ser[23389]: WARNING: upstream bug - 0-terminated packet May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_first_line: message too short: 3 May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR:parse_first_line: bad message May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_msg: message=<> May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: receive_msg: parse_msg failed Thanks, Ricardo
-- Jiri Kuthan http://iptel.org/~jiri/
We have deployed ATAs that come with images 2.14 and 2.15. Those images have a parameter called NatTimer (and NatServer). The manual describes NatTimer as: NatTimer Description
This parameter allows you to specify a retransmission interval for sending a dummy packet to NatServer.
The interval is in seconds and is specified in bits 0-11 of this parameter. The upper 20 bits are reserved
and should be set to 0.
Value Type
Bitmap
Default
0, which means that no dummy packets will be sent to the NatServer.
-----------
An ngrep of the dummy packet shows as: U 67.35.13.22:5060 -> 200.75.73.22:5060 00 00 00 00 ....
So it is basically an empty packet and it causes SER to generate those ERRORS in the SYSLOG. I do not mind that those errors ocurr, but it is causing our SYSLOG files to become full of this useless information. I guess an alternative for me would be to simply eliminate the source code that puts the ERRORs in the SYSLOG but I was looking for a simpler way.
Thanks, Ricardo
----- Original Message ----- From: "Jiri Kuthan" jiri@iptel.org To: "Ricardo Villa" ricvil@epm.net.co; serusers@lists.iptel.org Sent: Thursday, May 01, 2003 5:49 PM Subject: Re: [Serusers] SYSLOG Error Messages
At 04:35 PM 5/1/2003, Ricardo Villa wrote:
Hi,
We have deployed many Cisco ATAs behind NAT devices. In order to keep
the NAT session binding alive, we enabled a feature on the ATAs that basically send a small dummy packet to SER every 90 seconds.
Out of curiosity: how did you exactly make the ATAs to send the
keep-alives for you?
Did you write your own image?
Everything works great. The question is, how can I suppress the
WARNING/ERRORS that these dummy packets present to the SYSLOG? Is there a simple way to do this in the ser.cfg file?
Send some SIP keep-alive messages. SER drops non-SIP messages. If you are
sorry
about too large messages, you could generate such which include only first
line
and topmost via (elements which are always checked) and include a method
check
in script, which drops them.
-Jiri
These are the SYSLOG messages:
May 1 09:20:58 maui /usr/sbin/ser[23389]: WARNING: upstream bug -
0-terminated packet
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_first_line:
message too short: 3
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR:parse_first_line: bad
message
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_msg: message=<> May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: receive_msg: parse_msg
failed
Thanks, Ricardo
-- Jiri Kuthan http://iptel.org/~jiri/
Hello,
it is only possible to disable these warnings if you disable logging almost completely (which is probably not what you want). Did you compile the server or use some of the packages ? If you know how to compile it I can tell you how to disable it in the sources easily.
Jan.
On 01-05 19:53, Ricardo Villa wrote:
We have deployed ATAs that come with images 2.14 and 2.15. Those images have a parameter called NatTimer (and NatServer). The manual describes NatTimer as: NatTimer Description
This parameter allows you to specify a retransmission interval for sending a dummy packet to NatServer.
The interval is in seconds and is specified in bits 0-11 of this parameter. The upper 20 bits are reserved
and should be set to 0.
Value Type
Bitmap
Default
0, which means that no dummy packets will be sent to the NatServer.
An ngrep of the dummy packet shows as: U 67.35.13.22:5060 -> 200.75.73.22:5060 00 00 00 00 ....
So it is basically an empty packet and it causes SER to generate those ERRORS in the SYSLOG. I do not mind that those errors ocurr, but it is causing our SYSLOG files to become full of this useless information. I guess an alternative for me would be to simply eliminate the source code that puts the ERRORs in the SYSLOG but I was looking for a simpler way.
Thanks, Ricardo
----- Original Message ----- From: "Jiri Kuthan" jiri@iptel.org To: "Ricardo Villa" ricvil@epm.net.co; serusers@lists.iptel.org Sent: Thursday, May 01, 2003 5:49 PM Subject: Re: [Serusers] SYSLOG Error Messages
At 04:35 PM 5/1/2003, Ricardo Villa wrote:
Hi,
We have deployed many Cisco ATAs behind NAT devices. In order to keep
the NAT session binding alive, we enabled a feature on the ATAs that basically send a small dummy packet to SER every 90 seconds.
Out of curiosity: how did you exactly make the ATAs to send the
keep-alives for you?
Did you write your own image?
Everything works great. The question is, how can I suppress the
WARNING/ERRORS that these dummy packets present to the SYSLOG? Is there a simple way to do this in the ser.cfg file?
Send some SIP keep-alive messages. SER drops non-SIP messages. If you are
sorry
about too large messages, you could generate such which include only first
line
and topmost via (elements which are always checked) and include a method
check
in script, which drops them.
-Jiri
These are the SYSLOG messages:
May 1 09:20:58 maui /usr/sbin/ser[23389]: WARNING: upstream bug -
0-terminated packet
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_first_line:
message too short: 3
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR:parse_first_line: bad
message
May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: parse_msg: message=<> May 1 09:20:58 maui /usr/sbin/ser[23389]: ERROR: receive_msg: parse_msg
failed
Thanks, Ricardo
-- Jiri Kuthan http://iptel.org/~jiri/
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Jan,
I looked though the source code and commented out the places where I identified those particular LOG generating entries. I then generated the new "ser" executable using a plain "make". The problem is that the new "ser" does not look for the config in /etc/ser/ser.cfg. I have to give it the path by starting it with "ser -f /etc/ser/ser.cfg". What do I need to do for it to compile so that it defaults to look at /etc/ser/ser.cfg?
Thanks,
----- Original Message ----- From: "Jan Janak" jan@iptel.org To: "Ricardo Villa" ricvil@epm.net.co Cc: serusers@lists.iptel.org; "Jiri Kuthan" jiri@iptel.org Sent: Friday, May 02, 2003 4:48 AM Subject: Re: [Serusers] SYSLOG Error Messages
Hello Ricardo,
use cfg-target="/etc/ser/" when doing make all, i.e.: make all cfg-target="/etc/ser/"
Jan.
On 02-05 08:37, Ricardo Villa wrote:
Hi Jan,
I looked though the source code and commented out the places where I identified those particular LOG generating entries. I then generated the new "ser" executable using a plain "make". The problem is that the new "ser" does not look for the config in /etc/ser/ser.cfg. I have to give it the path by starting it with "ser -f /etc/ser/ser.cfg". What do I need to do for it to compile so that it defaults to look at /etc/ser/ser.cfg?
Thanks,
----- Original Message ----- From: "Jan Janak" jan@iptel.org To: "Ricardo Villa" ricvil@epm.net.co Cc: serusers@lists.iptel.org; "Jiri Kuthan" jiri@iptel.org Sent: Friday, May 02, 2003 4:48 AM Subject: Re: [Serusers] SYSLOG Error Messages
-
Jan Janak -
Jiri Kuthan -
Ricardo Villa