[OpenSER-Devel] [ openser-Bugs-1843645 ] TM Not Properly Fragmenting Oversize Messages

[SourceForge.net]

Bugs item #1843645, was opened at 2007-12-03 13:13
Message generated for change (Settings changed) made by unspin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1843645&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: modules
Group: ver devel
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: reticent (unspin)
Assigned to: Nobody/Anonymous (nobody)
Summary: TM Not Properly Fragmenting Oversize Messages

Initial Comment:
I ran into a situation where i was using a large Route set and i noticed that OpenSER was not fragmenting SIP messages that exceeded the MTU


This can be easily reproduced by adding the following to your openser.cfg just before a t_relay
---

if ( method=="INVITE" )
{
    append_hf("P-Asserted-Identity: <sip:laksjdflaksjklasjdhfkajsdhflkajsdhjkkfhasdfjkhaskdjfhkjsdhflkajsdhflkjashdlfkjahsdkjfhaksjdfhjkashdklfjahsdkjfkajsdhfkjasdhjkfahsjkdfhkajsdhfjkashdjkfhaksjdfhjkasdhffkljahsdkljfhaklsdfhlakjsdhfklajshdfkljashdlfkjahsldkfjhaslkdjfhaklsjdhfklajsdhflkasjhdfkljashdklfjashldkfjahsdklfjhaskldjfhaskldjfhklasjdfhlkasjdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfhlaskjdfhaskldjfhaklsdjfhaskldjfhaskldjfhklasdjfhklasfhsladkjhdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjf\r\n");
}

---


Using ngrep i see the following message being sent out with no fragments following it:
---

#
U 2007/12/03 21:04:03.994448 207.232.98.31:15061 -> 64.233.167.99:5060 33876 at 0:1480
:.....^.INVITE sip:200110005555 at google.com SIP/2.0.
Record-Route: <sip:207.232.98.31:15061;lr;ftag=aec3903fe85666f9o3;bid=bPP.x3v.E7g;nid=UX0.v9G.Wu3>.
Via: SIP/2.0/UDP 207.232.98.31:15061;branch=z9hG4bKfdd7.c32a2f24.0.
Via: SIP/2.0/UDP 172.16.1.109:5076;rport=5076;received=207.232.98.114;branch=z9hG4bK-8a7e8e11.
From: "unspin" <sip:200110005334 at spb1.hq.galnet.ca:15061>;tag=aec3903fe85666f9o3.
To: <sip:1234 at spb1.hq.galnet.ca:15061>.
Call-ID: 75d64637-5d166961 at 172.16.1.109.
CSeq: 102 INVITE.
Max-Forwards: 14.
Contact: "unspin" <sip:200110005334 at 207.232.98.114:5076>.
Expires: 240.
User-Agent: Linksys/SPA962-5.1.7.
Content-Length: 257.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: replaces.
Content-Type: application/sdp.
P-Asserted-Identity: <sip:<null>@>laksjdflaksjklasjdhfkajsdhflkajsdhfkljahsdkljfhaklsdfhlakjsdhfklajshdfkljashdlfkjahsldkfjhaslkdjfhaklsjdhfklajsdhflkasjhdfkljashdklfjashldkfjahsdklfjhaskldjfhaskldjfhklasjdfhlkasjdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfhlaskjdfhaskldjfhaklsdjfhaskldjfhaskldjfhklasdjfhklasfhsladkjhdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdklfjahskldfjhaskldjfhklasjdfhlaskdjfdhfklajsdhfkljashdfkljashkldjfhaskljdfhklasjdfhlkasjdhfklasjdfhlkajshdfkljashdfklashdk

---

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

Comment By: reticent (unspin)
Date: 2007-12-03 13:54

Message:
Logged In: YES 
user_id=1568212
Originator: YES

Ah, you are right Ovidiu

This ticket should be closed

tavis

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

Comment By: Ovidiu Sas (osas)
Date: 2007-12-03 13:26

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

ngrep doesn't show fragments.
Use tcpdump and capture to a file (tcpdump -n -s0 -w my_file.pcap).
Open the file with wireshark and you will see the reassembled packet.
I tested this many times and it is working great.

This bug should be closed as invalid.


Regards,
Ovidiu Sas

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

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