1:24 a.m.
Hi all,
I am currently working on Sierra modem (MC5728V). Looks like CDMA is not
fully supported for the voicecall yet.
What I see from ofono master branch there are only probe, remove, dial,
hangup had been implemented. I am working
on other's method step by step. I am wondering is it worth it to change the
dbus service path from org.ofono.cdma.voicecallmanager
to org.ofono.voicecallmanager? In this case, application doesn't need to
care about it's GSM modem or CDMA modem,
what they need to do is connecting to the same dbus path.
Sincerely,
TengChou Yang
4:58 p.m.
Hi,
On 06/19/2013 07:24 PM, TengChou Yang wrote:
Hi all,
I am currently working on Sierra modem (MC5728V). Looks like CDMA is not
fully supported for the voicecall yet.
What I see from ofono master branch there are only probe, remove, dial,
hangup had been implemented. I am working
on other's method step by step. I am wondering is it worth it to change
the dbus service path from org.ofono.cdma.voicecallmanager
Err, that is not a dbus service path. The service path is always the
same, org.ofono. What you're referring to is the dbus interface name.
to org.ofono.voicecallmanager? In this case, application doesn't
need to
care about it's GSM modem or CDMA modem,
what they need to do is connecting to the same dbus path.
No, the API has been specifically designed to separate CDMA and GSM
details. There are too many differences in the two systems and their
respective capabilities to mash them together.
Regards,
-Denis
6:49 p.m.
Hi Denis,
Date: Fri, 21 Jun 2013 10:58:53 -0500
From: denkenz(a)gmail.com
To: ofono(a)ofono.org
Subject: Re: CDMA voicecall driver
Hi,
On 06/19/2013 07:24 PM, TengChou Yang wrote:
> Hi all,
> I am currently working on Sierra modem (MC5728V). Looks like CDMA is not
> fully supported for the voicecall yet.
> What I see from ofono master branch there are only probe, remove, dial,
> hangup had been implemented. I am working
> on other's method step by step. I am wondering is it worth it to change
> the dbus service path from org.ofono.cdma.voicecallmanager
Err, that is not a dbus service path. The service path is always the
same, org.ofono. What you're referring to is the dbus interface name.
Thanks for the correction, I was referring to interface name.
> to org.ofono.voicecallmanager? In this case, application
doesn't need to
> care about it's GSM modem or CDMA modem,
> what they need to do is connecting to the same dbus path.
No, the API has been specifically designed to separate CDMA and GSM
details. There are too many differences in the two systems and their
respective capabilities to mash them together.
They do have a lot of differences but not in dbus method layer. For example,
ofono_voicecall_driver has methods like dial, answer, hangup all, hold_all_active...etc, I
believe cdma will have almost same methods like GSM. When we are using them in application
layer, we will call the same method name but different kind of modem driver.I am wondering
why ofono created two different interface name and providethe same call method?
Regards,
-Denis
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
6:04 p.m.
Hi,
They do have a lot of differences but not in dbus method layer. For
example,
ofono_voicecall_driver has methods like dial, answer, hangup all,
hold_all_active...etc,
I believe cdma will have almost same methods like GSM. When we are using
them in
application layer, we will call the same method name but different kind
of modem driver.
I am wondering why ofono created two different interface name and provide
the same call method?
The basics are the same, sure. However, once you get into the details
of three way calls, call waiting, multiparty calls, etc the logic and
API becomes vastly different.
Not to mention the various differences between carriers and their
specific extensions.
Bottom line is, compared to insanity of GSM/UMTS, CDMA is even more of a
mess and the API needs to evolve on its own. In the future, if it makes
sense to unify them, then we can do so. That time is not now.
Regards,
-Denis
8:44 p.m.
Date: Fri, 21 Jun 2013 12:04:04 -0500
From: denkenz(a)gmail.com
To: ofono(a)ofono.org
Subject: Re: CDMA voicecall driver
Hi,
> They do have a lot of differences but not in dbus method layer. For
> example,
> ofono_voicecall_driver has methods like dial, answer, hangup all,
> hold_all_active...etc,
> I believe cdma will have almost same methods like GSM. When we are using
> them in
> application layer, we will call the same method name but different kind
> of modem driver.
> I am wondering why ofono created two different interface name and provide
> the same call method?
The basics are the same, sure. However, once you get into the details
of three way calls, call waiting, multiparty calls, etc the logic and
API becomes vastly different.
Not to mention the various differences between carriers and their
specific extensions.
Bottom line is, compared to insanity of GSM/UMTS, CDMA is even more of a
mess and the API needs to evolve on its own. In the future, if it makes
sense to unify them, then we can do so. That time is not now.
> Regards,
-Denis
_______________________________________________
ofono mailing list
ofono(a)ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
Hi Denis,I get it. Thanks a lot for your answer.
Sincerely,TengChou Yang
3:11 a.m.
Hi,
On Wed, Jun 19, 2013 at 05:24:50PM -0700, TengChou Yang wrote:
Hi all,
I am currently working on Sierra modem (MC5728V). Looks like CDMA is not fully
supported for the voicecall yet.
I did not do anything with voicecall functionality, but you may want to look at
my (not accepted) Sierra Wireless CDMA patches from earlier this year. I am
also using the MC5728V.
https://lists.ofono.org/pipermail/ofono/2012-December/013981.html
Thanks,
Forest
--
Forest Bond
http://www.alittletooquiet.net
http://www.rapidrollout.com
3342
days inactive
3347
days old
5 comments
4 participants
participants (4)
-
Denis Kenzior -
Forest Bond -
TengChou Yang -
Yang TengChou