Bug 36159 - Add a 'pstn' status identifier as part of Connection_Presence_Type_Available
Summary: Add a 'pstn' status identifier as part of Connection_Presence_Type_Available
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-12 05:57 UTC by Danielle Madeley
Modified: 2011-04-20 07:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Danielle Madeley 2011-04-12 05:57:52 UTC
Some protocols can store phone numbers in their contact roster. It should be possible for clients to display these with a little phone next to them, and indicate the "contact" is in fact a just a phone number (clients could also then choose to filter them out).

I propose adding a status identifier 'pstn' which is part of Connection_Presence_Type_Available.

Rationale: the number is always AVAILABLE to be called/SMSed (exactly what channels come from the contact caps as per usual), but it's different to a regular AVAILABLE contact in that it's actually a phone number.
Comment 1 Will Thompson 2011-04-15 05:38:32 UTC
I agree. Here's a branch which adds this: <http://cgit.collabora.co.uk/git/user/wjt/telepathy-spec-wjt.git/log/?h=more-status-identifiers>

It also adds a "chat" identifier, matching what we already implement in Gabble.

I also took the opportunity to make the table look a bit nicer. You can see the result at <http://people.freedesktop.org/~wjt/telepathy-spec-more_status_identifiers/spec/Connection_Interface_Simple_Presence.html#description>!

Lemme know if these look good, and I'll merge them up.
Comment 2 Danielle Madeley 2011-04-15 18:52:43 UTC
I approve of this work. ++
Comment 3 Will Thompson 2011-04-20 07:52:55 UTC
Great. Merged for 0.22.2.


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.