16 Aug
2006
16 Aug
'06
9:06 p.m.
There is a check for message size (which is the same as it's always been):
if (msg:len >= 2048 ) {
sl_send_reply("513", "Message too big");
break;
};
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.
N.
On Wed, 16 Aug 2006 19:59:58 +0200, Weiter Leiter wrote
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
findthis check in nearly all sample configs). Or some other SER downstreamwhich returns
it?
On 8/16/06, sip <sip(a)arcdiv.com> wrote:Okay,
Since I've been unable to pass SIP MESSAGEs back and forth through our server,
but knowing full well that I once was able, I decided to take our
configuration and remove everything in it that we've added over time (slowly
regressing back to the beginning of our SVN code repository for the SER
config) and see if I could tell what had changed so that I can no longer pass
a SIP MESSAGE back and forth between clients.
It didn't work.
SO... I decided to take the hello-world config and try with it.
No luck.
What am I missing here? Is there some special handling that is needed to pass
a SIP MESSAGE in SER 0.9.6? Is there a chance that something basic would have
changed between 0.9.0 (our original server) and 0.9.6 that would have broken
our ability to pass the MESSAGE method without additional tinkering?
Sure, if I put in a block like:
if(method=="MESSAGE")
{
sl_send_reply("200", "OK");
};
... it's clear the message gets there and I receive the 200 OK, but of course
it doesn't go anywhere after that.
Without that block in there, it ends up getting a 513 Message too big response
(which seems to be somewhat of a default for messages that don't end up
getting handled in any other way that SER understands).
I'm now completely at a loss. Pointers. Tips. Snide remarks. Anything helpful
would be greatly appreciated.
N.
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers