<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="Open WebMail 2.20 20031014" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">There is a check for message size (which is the same as it's always been):
<br />
<br />if (msg:len >= 2048 ) {
<br /> sl_send_reply("513", "Message too big");
<br /> break;
<br /> };
<br />
<br />
<br />Modifying this has no real effect on the return, and the MESSAGE being sent shouldn't in any way have gone beyond that size. That check's always been there, though, and I know this has worked before... so I'm wondering what might have changed, if anything... or if there's a 'standard' way of handling SIP MESSAGE methods that I'm completely missing.
<br />
<br />N.
<br /><b>
<br />
<br />On Wed, 16 Aug 2006 19:59:58 +0200, Weiter Leiter wrote</b>
<br />> A quick look seems to shows that this error is not generated by code;
probably there is a check in your script for message size (you can find
this check in nearly all sample configs). Or some other SER downstream
which returns it?
<br />>
<br />> <span class="gmail_quote">On 8/16/06, <b class="gmail_sendername">sip</b> <<a href="mailto:sip@arcdiv.com">sip@arcdiv.com</a>> wrote:</span><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
Okay,
<br />>
<br />> Since I've been unable to pass SIP MESSAGEs back and forth through our server,
<br />> but knowing full well that I once was able, I decided to take our
<br />> configuration and remove everything in it that we've added over time (slowly
<br />> regressing back to the beginning of our SVN code repository for the SER
<br />> config) and see if I could tell what had changed so that I can no longer pass
<br />> a SIP MESSAGE back and forth between clients.
<br />>
<br />> It didn't work.
<br />>
<br />> SO... I decided to take the hello-world config and try with it.
<br />>
<br />> No luck.
<br />>
<br />> What am I missing here? Is there some special handling that is needed to pass
<br />> a SIP MESSAGE in SER 0.9.6? Is there a chance that something basic would have
<br />> changed between 0.9.0 (our original server) and 0.9.6 that would have broken
<br />> our ability to pass the MESSAGE method without additional tinkering?
<br />>
<br />> Sure, if I put in a block like:
<br />>
<br />> if(method=="MESSAGE")
<br />> {
<br />> sl_send_reply("200", "OK");
<br />> };
<br />>
<br />> ... it's clear the message gets there and I receive the 200 OK, but of course
<br />> it doesn't go anywhere after that.
<br />>
<br />> Without that block in there, it ends up getting a 513 Message too big response
<br />> (which seems to be somewhat of a default for messages that don't end up
<br />> getting handled in any other way that SER understands).
<br />>
<br />> I'm now completely at a loss. Pointers. Tips. Snide remarks. Anything helpful
<br />> would be greatly appreciated.
<br />>
<br />> N.
<br />> _______________________________________________
<br />> Serusers mailing list
<br />> <a href="mailto:Serusers@lists.iptel.org">Serusers@lists.iptel.org</a>
<br />> <a href="http://lists.iptel.org/mailman/listinfo/serusers">
http://lists.iptel.org/mailman/listinfo/serusers</a>
<br />> </blockquote>
<br />
<br />
<br />
</font>
</BODY>
</HTML>