Hi Cindy!
for TCP: the error seems to occur while reading the message. Are you
sure the error route is not called for this type?
for UDP: Are you passing any flags to the sipmsg_validate() function?
Have you tried using the 's' flag [1]?
[1] http://www.opensips.org/html/docs/modules/1.9.x/sipmsgops.html#id293070
Best regards,
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 03/22/2013 02:30 AM, Cindy Leung wrote:
Hi all,
So we encountered a malformed SIP message one day that looks like this...
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.1.1:5060;branch=z9hG4bK-15598-12-0
From: sipp <sip:[email protected]>;tag=12
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 1 INVITE
Contact: "1234" <sip:[email protected]:5060;transport=udp>
User-Agent: SIPp
Max-Forwards: 70
Content-Type: application/sdp
Content-Lenght: 0
Typo in Content-Length.
This message successfully passed through error_route
and sipmsg_validate() and continue through the rest of the config.
Interesting enough, I get different errors when I send it over
different protocol.
TCP:
/usr/local/sbin/opensips[18814]: ERROR:core:tcp_read_req: bad request,
state=4, error=4 buf: <SIP message here>
UDP:
/usr/local/sbin/opensips[18804]: ERROR:core:clen_builder: no message
body found (missing crlf?)
/usr/local/sbin/opensips[18804]:
ERROR:core:build_req_buf_from_sip_req: failed to adjust Content-Length
/usr/local/sbin/opensips[18804]: ERROR:tm:print_uac_request: no more
shm_mem
/usr/local/sbin/opensips[18804]: ERROR:tm:t_forward_nonack: failure to
add branches
Can you let me know if I have missed anything please? Thanks!
Cindy
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
