If the SIP MESSAGE will carry the payload of the sms or mms, the question is if the UA supports a specific content-type.
I belive you will put a specific conect-type for each type of message and the UA will have to render it as apropiated for the type of message:
Show the txt of an SMS, connect to an RTSP server for fetching an MMS content or whatever.
The Accept header is optional in REGISTER request but may be usefull to advertise UA's Accepted content-types.
Regards Diego B
Rub�n Mazariegos del Rey wrote:
Hi,
At the moment I am developing a messaging platform (SMS and MMS) over SIP networks. Basically, the short messages and multimedia messages will be transmited embeded in a SIP MESSAGE. When a UA registers to the network, on the message server side we need to know if the device that is being used has SMS capabilities, MMS capabilities or both. I have read the RFC 3840, which is intended to indicate UA capabilities in SIP protocol.
My questions are:
- Is the mechamism described in RFC 3840 appropriate to inform the server side about the messaging capabilities of the UA? Which is the feature tag that should be used to indicate that the UA has SMS capabilities? And MMS capabilities?
- Is there a better mechanism by which the UA could indicate its messaging capabilities in the SIP Register method?
Thanks in advance for your time and your answers.
Rub�n
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
