[SIPForum-discussion] Transferring large MIME attachments within the SIP MESSAGE request.

[Onur Cinar]

Hi,

I am working on a SIP based client side application that will be sending and
receiving rich instant messages (embedded pictures and audio).

The generated instant messages will be MIME encapsulated, and they will be
transported through SIP MESSAGE requests.

Regarding the RFC 3438, the size of a MESSAGE request should not exceed 1300
bytes due to MTU limitations. Based on that, transferring the embedded
elements through SIP MESSAGE requests does not seem like an efficient way.

I am trying to follow the RFCs as much as possible in order to be compatible
with 3rd party proxies.

So, rather than using a proprietary transport mechanism between clients for
transferring those embedded elements outside SIP signaling; I wanted to ask
for your comments on what would be the most convenient way of doing this
with SIP only messaging/transport.

I thought about sending unique IDs for each embedded element within the SIP
MESSAGE requests, and expecting the other client to initiate a set of
subsequent INVITE requests (with TFTP/FSP/... media types) to fetch those
referred elements?

Thanks in advance for your help,

Best regards,
-Onur

---
A. Onur Cinar
Senior Software Engineer
ARGELA Technologies
http://www.argela.com.tr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20060328/3b4f0a70/attachment-0001.html>