[SIPForum-discussion] Can SIP Layer handle Fragmentation
usman chaudhry
usman_chaudhry at yahoo.com
Thu Sep 11 07:35:15 UTC 2008
Hello Guys,
It is my understanding that SIP (RFC 3261) cannot handle fragmented packets. It is the responsibility of the lower layer protocols to do the packet reassembly i.e. for SIP via UDP it will be the IP layer that reassembles and for SIP via TCP it will be the the IP/TCP layer.
Can you please confirm if there is any requirement on the SIP Stack to reassemble fragmented SIP packets (i.e. Frames).
Regards
Usman
----- Original Message ----
From: mohab emara <mohabemara at gmail.com>
To: Stewart Bunce <Stewart.Bunce at telsis.com>
Cc: usman chaudhry <usman_chaudhry at yahoo.com>; discussion at sipforum.org
Sent: Thursday, September 11, 2008 4:36:34 AM
Subject: Re: [SIPForum-discussion] Contact Header being changed by a SIP Prxy.
Agree with Stewart, and find below the filtered data from table 2 concerning this point
Header field where proxy ACK BYE CAN INV OPT REG
___________________________________________________________
Contact R o - - m o o
Contact 1xx - - - o - -
Contact 2xx - - - m o o
Contact 3xx d - o - o o o
Contact 485 - o - o o o
Where Bold d stands for delete only.
Br,
Mohab
On Wed, Sep 10, 2008 at 4:02 PM, Stewart Bunce <Stewart.Bunce at telsis.com> wrote:
According to Table 2: Summary of header fields, A--O in RFC3261 a Proxy
can only modify the Contact header field in 3XX responses and even then it is
only allowed to delete it/them not modify.
Stew
-----Original Message-----
From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org]On Behalf Of usman chaudhry
Sent: 10 September 2008 10:41
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Contact Header being changed by a SIP Prxy.
Hello All,
According to RFC 3261 is a SIP proxy allowed to change the Contact Header for an
INVITE
regards
Usman.
________________________________
NOTICE & DISCLAIMER
This email including attachments (this "Document") is confidential and may contain legally privileged information. If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents. We cannot accept liability for any breaches of confidence arising through use of this Document.
The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement. The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk.
Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis. We will not accept responsibility for any commitments made by our employees outside the scope of our business.
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080911/27afb06f/attachment-0002.html>
More information about the discussion
mailing list