msg:len is too large

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

msg:len is too large

vivid333
hello:
      
        Why OpenSips  returns 513? is  that SIP Message Buffer is too large/or full ? is that mean that include previous message?
 below is opensips.cfg:

        route {
  
                if (!mf_process_maxfwd_header("70")) {
                    sl_send_reply("483","Too Many Hops...");
                    exit;
                };

                ###when a message comes, I print $ml, 

                if (msg:len >= 2048 ) {
                        sl_send_reply("513", "Message too big...");
                        exit;
                };
               
                if (method == "OPTIONS") {
                        sl_send_reply("200", "OK");
                        return;
                };
          
        ................
        }




Wireshark Capture:

OPTIONS <a class="moz-txt-link-freetext" href="sip:+14089664381@74.3.165.159">sip:+14089664381@74.3.165.159 SIP/2.0                                                         406Bytes
Via: SIP/2.0/UDP 10.191.132.71:1087;rport;branch=z9hG4bK1218259554
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=829085183
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>
Call-ID: 277470534
CSeq: 20 OPTIONS
Accept: application/sdp
Max-Forwards: 70
User-Agent: FafaYou/1.0 (SingFafa/1.1)
Content-Length: 0

 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.191.132.71:1087;rport=3247;branch=z9hG4bK1218259554;received=117.136.0.214
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=829085183
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>;tag=36ab34ed4546465d12e494a13d8598e2.9cde
Call-ID: 277470534
CSeq: 20 OPTIONS
Server: OpenSIPS (1.6.4-2-notls (x86_64/linux))
Content-Length: 0
 
OPTIONS <a class="moz-txt-link-freetext" href="sip:+14089664381@74.3.165.159">sip:+14089664381@74.3.165.159 SIP/2.0                                                         406Bytes
Via: SIP/2.0/UDP 10.191.132.71:1087;rport;branch=z9hG4bK1218259554
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=829085183
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>
Call-ID: 277470534
CSeq: 20 OPTIONS
Accept: application/sdp
Max-Forwards: 70
User-Agent: FafaYou/1.0 (SingFafa/1.1)
Content-Length: 0

 
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.191.132.71:1087;rport=3247;branch=z9hG4bK1218259554;received=117.136.0.214
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=829085183
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>;tag=36ab34ed4546465d12e494a13d8598e2.9cde
Call-ID: 277470534
CSeq: 20 OPTIONS
Server: OpenSIPS (1.6.4-2-notls (x86_64/linux))
Content-Length: 0
 
INVITE <a class="moz-txt-link-freetext" href="sip:+14089664381@74.3.165.159">sip:+14089664381@74.3.165.159 SIP/2.0                                                                  806Bytes
Via: SIP/2.0/UDP 10.191.132.71:1087;rport;branch=z9hG4bK954496617
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=2053583849
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>
Call-ID: 343535350
CSeq: 20 INVITE
Contact: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@117.136.0.214:3247"><sip:+8615811008009@117.136.0.214:3247>
Content-Type: application/sdp
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
Max-Forwards: 70
User-Agent: FafaYou/1.0 (SingFafa/1.1)
Subject: Phone call
Content-Length:   238
 
v=0
o=+8615811008009 123456 654321 IN IP4 10.191.132.71
s=A conversation
c=IN IP4 10.191.132.71
b=AS:256
t=0 0
m=audio 7076 RTP/AVP 114 101
a=rtpmap:114 AMR/8000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-11
a=sendrecv
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 10.191.132.71:1087;rport=3247;branch=z9hG4bK954496617;received=117.136.0.214
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=2053583849
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>
Call-ID: 343535350
CSeq: 20 INVITE
Server: OpenSIPS (1.6.4-2-notls (x86_64/linux))
Content-Length: 0

 
SIP/2.0 513 Message too big...
Via: SIP/2.0/UDP 10.191.132.71:1087;received=117.136.0.214;rport=3247;branch=z9hG4bK954496617
From: <a class="moz-txt-link-rfc2396E" href="sip:+8615811008009@223.4.90.214"><sip:+8615811008009@223.4.90.214>;tag=2053583849
To: "+14089664381" <a class="moz-txt-link-rfc2396E" href="sip:+14089664381@74.3.165.159"><sip:+14089664381@74.3.165.159>;tag=36ab34ed4546465d12e494a13d8598e2.f51e
Call-ID: 343535350
CSeq: 20 INVITE
Server: OpenSIPS (1.6.4-2-notls (x86_64/linux))
Content-Length: 0



 I really don't know the reason. Looking forword to have your reply.
Thanking for your helps in advance.
_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: msg:len is too large

Brett Nemeroff


On Tue, Sep 13, 2011 at 9:02 PM, vivid333 <[hidden email]> wrote:
hello:
      
        Why OpenSips  returns 513? is  that SIP Message Buffer is too large/or full ? is that mean that include previous message?
 below is opensips.cfg:


I'm not entirely sure where your trace is coming from, but typically you run into this if you relay the call without modifying the RURI; thus causing a huge loop. The stacked vias make the packet larger and larger until you hit the msg too big limit. You may not see this on a normal trace, you might have to watch on the loopback interface.

-Brett
 

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: msg:len is too large

Faisal Rehman
Hi Brett,

It can be a routing problem, so please see that link http://www.openser.org/pipermail/users/2007-September/013083.html which may help to solve your problem.


With Best Regards,


Faisal Rehman


From: Brett Nemeroff <[hidden email]>
To: OpenSIPS users mailling list <[hidden email]>
Sent: Wednesday, September 14, 2011 7:11 AM
Subject: Re: [OpenSIPS-Users] msg:len is too large



On Tue, Sep 13, 2011 at 9:02 PM, vivid333 <[hidden email]> wrote:
hello:
      
        Why OpenSips  returns 513? is  that SIP Message Buffer is too large/or full ? is that mean that include previous message?
 below is opensips.cfg:


I'm not entirely sure where your trace is coming from, but typically you run into this if you relay the call without modifying the RURI; thus causing a huge loop. The stacked vias make the packet larger and larger until you hit the msg too big limit. You may not see this on a normal trace, you might have to watch on the loopback interface.

-Brett
 

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users