[Devel] [ openser-Bugs-1724291 ] Content-Length problem with NOTIFY

[SourceForge.net]

Bugs item #1724291, was opened at 2007-05-23 17:55
Message generated for change (Comment added) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1724291&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.2.x
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Tobias Lindgren (effeks)
Assigned to: Bogdan (bogdan_iancu)
Summary: Content-Length problem with NOTIFY

Initial Comment:
Hi,

I'm having trouble with the Content-Lenght
header when a NOTIFY-message goes through our OpenSER 1.2.0.

Here is what seem to happend.

SIP NOTIFY from our PSTN-gateway to our OpenSER:
--- CUT ---
Content-Length: 21.
.
SIP/2.0 100 Trying.
.
--- CUT ---

SIP NOTIFY from our OpenSER to another SIP Proxy:
--- CUT ---
Content-Length: 21.
.
SIP/2.0 100 Trying.
--- CUT ---

I used Wireshark to check the message body length and it reports "21 bytes" on the package coming into my OpenSER and "20 bytes" on the package going out from OpenSER. However "content-lenght" header remains the same, "21".

Br,
/Tobias

----------------------------------------------------------------------

>Comment By: Bogdan (bogdan_iancu)
Date: 2007-05-25 19:38

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi Tobias,

found the problem - it was more than silly as it happend because of an old
test (if the proxy receives 0 terminated packages). Now it seams you can
have such packages (with the 0 in body), so the test became bogus. I
removed it SVN trunk, 1.2 and 1.1

Thanks and regards,
Bogdan

----------------------------------------------------------------------

Comment By: Bogdan (bogdan_iancu)
Date: 2007-05-25 18:07

Message:
Logged In: YES 
user_id=1275325
Originator: NO

ok- got some dumps from Tobias to work on...I will try to reproduce it and
see where is the problem.

regards,
bogdan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1724291&group_id=139143