[Bug 24905] Emergency call identification

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=24905


Mikhail Zabaluev <mikhail.zabaluev at nokia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppessi+telepathy at gmail.com




--- Comment #1 from Mikhail Zabaluev <mikhail.zabaluev at nokia.com>  2010-02-02 06:45:20 PST ---
Some comments on the Maemo interfaces with a view to generic applicability:

Connection.Interface.Emergency -- rename to EmergencyContacts for extra
disambiguation and to reflect the purpose better?

The type Emergency_Service: Are all fields necessary? Is exposure of URNs
appropriate with other protocols in Telepathy (which operates with opaque
"string IDs" elsewhere)? Are the values of the alias list meant to be other
URNs or human-readable strings? If the latter, is it too much information,
compared to use of aliases elsewhere in Telepathy?

The property Channel.Interface.Emergency.InitialEmergencyService should be
recommended to be made requestable, this being the recommended way to request
an emergency call. Then one could have a separate connection (and even a
separate connection manager) for emergency calls, clearly designated as such
through requestable channel classes and contact capabilities.

The contacts retrieved from Connection.Interface.Emergency could provide the
property discussed above in their capabilities.

Documentation for Channel.Interface.Emergency.EmergencyServiceChanged leaves it
unclear when the signal is initially emitted as a "tag" signal for emergency
calls, as the documentation elsewhere suggests. Should it be treated as "the
moment when it becomes clear that the call is directed to a particular
emergency service"? Is it a use case relevant for telephony?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.