Billy,
I am unsure what a MMS message is ?. But if the intent of a user
is to establish RTP then this is expressed as an offer in SDP attached to
the SIP messaging - if the far end is capable and available then this will
be communicated back to the offerer and if not that will also be
communicated back. So as you say "once the SIP connection negogiations have
successfully completed" the RTP will be established like magic !.
RFC3264 explains the Offer / Answer model, the mechanics of how it
works is in RFC3261 and other RFCs but they can be heavy reading if you
have high level questions.
Read on for a very average example: SIP phones are made today to
provide telephony capability just like a POTS phone, when you pick up the
handset on your SIP phone and dial digits the SIP phone will form a SIP
INVITE request with it's audio capabilities detailed in SDP attached to
this request this is the Offer. Lets assume that all is well and your
request gets to the 'far-end' and alerts your target for communication. If
the target is capable of audio and available it will respond with a subset
of what was in the audio offer, this is the Answer (hence Offer - Answer
model). The RTP is now established end to end - the local ringback will
stop and the two parties can talk to each other.
Regards,
Wayne.
Billy Carr <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
28/12/2004 11:10 AM
To: [email protected]
cc:
Subject: [Sip-implementors] Establishing An Rtp Session
Hey All!
I am interested in using SIP and RTP stacks to send MMS messages. What
is not clear is how to establish an RTP session
once the SIP connection negogiations have successfully completed.
Can I buy a vowel? :-)
Thanks in Advance for your help.
Bill Carr
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
******************************************************************************
- NOTICE FROM DIMENSION DATA AUSTRALIA
This message is confidential, and may contain proprietary or legally privileged
information. If you have received this email in error, please notify the
sender and delete it immediately.
Internet communications are not secure. You should scan this message and any
attachments for viruses. Under no circumstances do we accept liability for any
loss or damage which may result from your receipt of this message or any
attachments.
******************************************************************************
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
