Re: [Users] Content-Lenght problem with NOTIFYs

I guess there is a CR at the end of the packet - correct? I'm not sure about this, but as the CR is part of the content I think openser should forward it too - thus leave the content untouched. Thus, maybe its a bug in openser. regards klaus Tobias Lindgren wrote: > Hi all, > > thanks for the hint. I used Wireshark now and it reports "21 bytes" on > the message body on my package coming into my OpenSER and "20 bytes" on > the package going out from OpenSER. However "content-lenght" header is > still the same, "21". > > Br, > /Tobias > > Klaus Darilion said the following on 2007-05-23 12:12: >> Use ethereal/wireshark to find out the real length of the content. >> It looks like 21 is correct. Maybe the receiver does not like the single >> CR at the end of the content. >> >> regards >> klaus >> >> Tobias Lindgren wrote: >>> Hello, >>> >>> from what I can see (ngrep) it looks like the content-lenght is 21 (if >>> you count the characters), but traversing my OpenSER it seems that one >>> character is removed (a dot?) and the content-lenght then should be 20? >>> >>> Br, >>> /Tobias >>> >>> Andreas Granig said the following on 2007-05-23 11:12: >>>> Hi, >>>> >>>>> Please advice on what we are doing wrong here? >>>> What is the actual content length? If the GW sets it to 21 and the UA is >>>> only happy with 20, one of them has to be right. So it's either a bug in >>>> the GW's or UA's length calculation (and should be fixed there, not >>>> using OpenSER). >>>> >>>> Andreas >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users