Comments inline.
Rub�n
Paul Kyzivat escribi�:
Comments inline.
Paul
Rub�n Mazariegos del Rey wrote:
Paul Kyzivat escribi�:
Rub�n Mazariegos del Rey wrote:
> At the moment I am developing a messaging platform (SMS and MMS) over
> SIP networks. 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 first question is: how are these capabilities manifested in SIP? That
may affect how the capabilities are advertised. AFAIK, SMS and MMS are
not capabilities that are themselves meaningful in SIP - they are
specific PSTN protocols. So I would imagine that they would be
manifested in SIP as gateway functions, much as the PSTN voice network
is connected to SIP via PSTN gateways, with the mapping of PSTN phone
numbers to sip addresses. I don't know much about SMS and MMS, but I
have the impression that they at least share the same address space with
the PSTN voice network.
The SMS and MMS facilities will be implemented in the platform as a service provided by an Application Server. A user willing to send or receive a short message or a multimedia message doesn't need to use a PSTN phone. In fact, the service is intended only for SIP users.
I'm sorry, but I still don't get it, especially if the service is intended only for SIP users.
How do these SMS and MMS services differ from simple basic IM using MESSAGE? Why does the support for SMS and MMS need to be conveyed to anyone? And how does the SMS service differ from the MMS service?
I have a feeling you are trying to draw a distinction where there is no difference.
Perhaps it would help if you could provide a complete use case involving sender, application server(s), and recipient, giving expected message flows and content types.
The application server needs to know if the user has a device just with text capabilities, multimedia capabilities (image, video, sound...), or both.
Imagine a user's device with just a text display, the application server should not send it a multimedia message containing an image or a video. Instead, the application server would send it a short message (if the device supports SMS) with an URL where it can fetch the content of the multimedia message.
Would be appropriate something like the following?
Contact: <sip:[EMAIL PROTECTED]> ;+sip.sms;+sip.mms
or
Contact: <sip:[EMAIL PROTECTED]> ;+mycompany.sms;+mycompany.mms
What we *really* don't need is fragmentation of features down to the company level so that interoperation is minimized. I strongly suspect that distinguishing SMS from MMS and both of them from general IM is also an unnecessary distinction.
Thanks again for your answers Rub�n
So for instance, if you have simply extended a PSTN gateway to accept
and generate MESSAGE messages containing certain content types, then we
can easily find a way to represent the capability to handle this kind of
messaging.
> My questions are: > > - Is the mechamism described in RFC 3840 aproppiate to inform the > server side about the messaging capabilities of the UA?
In general, yes. I reserve judgement on how appropriate it is for what you plan to do, until I know more.
> Which is the > feature tag that should be used to indicate that the UA has SMS > capabilities? And MMS capabilities?
Depends on how you are mapping the functionality onto SIP. If you are using MESSAGE, then perhaps something like:
methods="MESSAGE";type="text/plain"
might work for SMS. For MMS you would need to figure out what types are used to convey multimedia content.
> - Is there a better mechanism by which the UA could indicate its > messaging capabilities in the SIP Register method?
Not that I know of, but I reserve judgement until I know more about what
your have in mind.
> Thanks in advance for your time and your answers.
Thanks, Paul
> Yours sincerely, > > Rub�n >
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
begin:vcard fn;quoted-printable:Rub=C3=A9n Mazariegos del Rey n;quoted-printable:Mazariegos del Rey;Rub=C3=A9n org;quoted-printable:;Mensajer=C3=ADa en Red Fija adr;quoted-printable:Puesto 1503-CA1;;Parque Tecnol=C3=B3gico de Boecillo, Parcelas 119-120;Boecillo;Valladolid;47151;Spain email;internet:[EMAIL PROTECTED] title:Ingeniero I+D tel;work:983 367 567 tel;fax:983 367 664 url:http://www.tid.es version:2.1 end:vcard
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
