[mythtv] [mythtv-users] MythPhone - any ongoing activities on this?

[Blazej Lewcio]

<<<<<<<<<<<<<<
Blazej,

It's great that somebody pick again MythPhone area within Myth.

I'm greatly interested in integration of myth and home phone system.

Sometime ago I started do such integration with help of perl.
So for my conceptual considerations led me to following solution definition
(and partial implementation):

A: myth as parallel system to home voip system.
In such scenario, voip and myth are loosely coupled, where myth is usually
slave to voip system and working more as snooping than controlling
component.
In such case I would consider following functionality:
1.it should be able pause/resume when SIP calls are incoming/ended;
2.When we have video playback - it should present via osd calling/caller
numbers. When calls ends, it can present call duration/costs;
3.When myth is in non-video - presentation is based on myth-ui. It should
pop-up windows with the same info as in point 2;
4.It will be nice to have pictures of calling person when call is incoming;
5.It would be nice when user will be able to refuse and redirect to voice
mail when call is incoming.e.g. on OSD user will see "press 1 to refuse
call, 2 for record, 3 for redirect";
6.When call is ongoing it would be nice when user will be able to switch
from currently running SIP UA to myth as UA (speakers will be used for
listening, attached to fe mic - for speaking);



B: myth is home voip system
In such scenario, voip and myth are tightly coupled, where myth is main home
SIP proxy and is controlling home voip services.
In such case I would propose following functionality:
-all features from scenario A;
1.possibility to initiate SIP calls;
2.dictionary for SIP calling (with pictures);
3.voice mail function;
4.voice mails list presentation and play;
5.video calls reception;
6.video calls initiation;
7.all other function requested by other users;
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


Warpme,

your list has a big overlap with the design I work on. That's good :-)

My idea is to stay in C,C++,Qt avoiding scripting languages. (At least at
the beginning).

The current plan looks as follows:
(1) As the first milenstone of this project, I see a generic/modular User
Agent capable of typical VoIP functionality (contact/call management, dtmf,
history, registration etc.). (2) As second milenstone, I would like to add
other communication engines available via e.g. Telephaty (e.g. googletalk).
All additional features, video, voicemail, chat  could be considered, after
the base functionality is stable.

I encourage you to contribute.

Blazej
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20091204/bc40fb25/attachment.htm>