Juniper Firewall Logging a problem

Today looked at the computer room firewall, suddenly a continuous and short but very obvious English through my eyes into my brain, a bit wrong, open the detailed content to see.

SIP Parser Error Message:cannot find CRLF

SIP Parser Error Message:cannot find CRLF

SIP Parser Error Message:cannot find CRLF

SIP Parser Error Message:cannot find CRLF

SIP Parser Error Message:cannot find CRLF

SIP parsing error not found CRLF? It's a question of God's code. The firewall is juniper.

-------------------------------

SIP (Session Initiation Protocol) is an IETF-defined, ip-based application-layer Control protocol. Since SIP is based on a text-only signaling protocol, it can manage meetings on different access networks. A meeting can be any type of communication between terminal devices, such as video meetings, both time information processing, or collaborative meetings.
 
The protocol does not define or limit the business that can be used, and issues such as transmission, quality of service, billing, security, etc. are handled by the basic core network and other protocols. There is nothing in the-------------------------------------server to use this protocol, how can this be the problem? Strange, odd? Go to the official website to find out the situation is this: What does SIP PARSER ERROR message:cannot found CRLF mean Categories: * Firewalls ISG/NS/SSG Serie S * ScreenOS updated:18 Aug version:3.0 Summary:problem or goal:the following is getting thi s message in the event logs: "Sip PARSER error Message:cannot find CRLF What does sip PARSER error message:cannot FI
ND CRLF mean? 
System Notif 00767 NSCos45683 solution:this Log event message was indicating that Juniper NetScreen Device is has problems parsing SIP packets because it cannot find the carriage return line feed Commands-crlf in th E SIP request or SIP response. SDP (Session Description Protocol) requires that there should is a CRLF terminating in EAch line with either a SIP request or response for distinguishing between message boundaries. There are some SIP implementations that leave out of trailing CRLF after the SDP and compute the CONTENT-LENGTH ACC
 
ordingly, which does, not comply with RFCs and which the Juniper NetScreen. Device. Workaround:to eliminate these logs messages, define the policy by specifying the ' IGNORE ' option in the application Pulld
 
 
 
Own.
 Basically, it says:
This log event message indicates that the Junipernetscreen Firewall/VPN device
A problem occurred while parsing the SIP packet, it could not find the return line feed character for the command-CRLF
SIP request or SIP response. SDP (Session Description protocol) requires that there should be a CRLF
End a SIP request or differentiate the message boundary response in each row.
Some SIP implements the CRLF of the tail of the SDP after leaving, and calculates
Content length Therefore, this does not conform to RFC and juniper company NetScreen Equipment
Not currently supported.
WORKAROUND: To eliminate these log information, you need to create a new policy protocol sip and specify the Ignore option

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Network/Firewall/

This article is from the "Shadow Knight" blog, please be sure to keep this source http://andylhz2009.blog.51cto.com/728703/749730