| Summary: | Should implement Channel.Interface.SMS | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
| Component: | rakia | Assignee: | Mikhail Zabaluev <mikhail.zabaluev> |
| Status: | RESOLVED MOVED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | enhancement | ||
| Priority: | medium | CC: | chandniverma2112 |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Guillaume Desmottes
2011-05-04 05:40:01 UTC
What is the suggested SIP specification to send SMS messages? The 3GPP one is pretty ugly, but can be done if it is the only one in wide use. I have no idea how it works in SIP but I already sent SMS using tp-sofiasip and Empathy with with voipbuster account. They appeared as normal messages in Empathy though. (In reply to comment #2) > I have no idea how it works in SIP but I already sent SMS using tp-sofiasip and > Empathy with with voipbuster account. They appeared as normal messages in > Empathy though. They probably just convert plain SIP messages to SMS for recipients that they route to phone numbers. If they have some way to inform the SIP client that they support this feature, I'd be glad to know about this. This feature can be also controlled locally by a connection manager option. Perhaps while we are at it, we should make the option enumerable to allow for the multiple known ways of payloading an SMS. Yeah, if we can't discover it when connecting to the server I think a "This account supports SMS sending" would be better than nothing. The N900 has something like that to tell to use an account to make calls. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-rakia/issues/19. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.