Problems with voice call.

Hi,

I'm trying to make a voice call with oFono. I'm using Option GlobeSurfer ICON 225 HSDPA/UMTS USB as the modem. If I understood correctly voice call should be possible with the dbus-messages used below. However, I end up with an error "Operation failed".

$ dbus-send --system --print-reply --dest=org.ofono /
org.ofono.at.Manager.Create string:"dev:/dev/ttyHS0" string:"at"
method return sender=:1.540 -> dest=:1.544 reply_serial=2
   object path "/modem1"

$ dbus-send --system --print-reply --dest=org.ofono /modem1
org.ofono.VoiceCallManager.Dial string:"+000000000000" string:"default"
Error org.ofono.Error.Failed: Operation failed

When the second dbus-message is sent the following messages are printed by the ofonod:

ofonod[19113]: atd_cb got result: 0 ofonod[19113]: Final response: ERROR ofonod[19113]: Dial callback returned error: (null)

Are the messages I sent to the ofonod correct?

Regards,
Marko

Hi Marko,

Yes, it can use dbus-message but python script will be more visibility
Also you can try use d-feet
As I haven't modem in hand so I use phonesim as simulator, I didn't meet your problem and the Voice call work fine with simulator

My result:
dbus-send --system --print-reply --dest=org.ofono /modem1 org.ofono.VoiceCallManager.Dial string:"+234" string:"default" method return sender=:1.829 -> dest=:1.851 reply_serial=2
object path "/modem1/voicecall01"

So you can check if your modem could receive the ATD command first. If not, perhaps something wrong in driver part.

Zhigang

Hi Marko,

I am not sure this hardware actually does support voice calls. We haven't tried it. So it is up to you to figure this out.

Regards

Marcel

Hi Marko,

Operation failed literally means the modem replied with an error of some sort.

Looks good.

For wrong arguments, the error would be something like InvalidArguments or InvalidFormat.

This means that ATD final response was ERROR. Are you sure your modem actually supports voice calls?

Regards,
-Denis

Hi denkenz,

thanks for the reply. I was not sure about the voice call features of the modem. Now when I searched the answer I found out that the modem does not in fact support voice calls.

I did not realize this at first, because ofono offered the possibility for voice calls (loaded for example the VoiceCallManager interface). For SMS ofonod says

ofonod[7906]: SMS not supported by this modem. If this is in error please submit patches to support this hardware

however the modem has a support for SMS, which I also tested with the windows drivers that were delivered with the modem.

Maybe there could be similar "not supported" feature for the voice call plugins?

Regards,
Marko

Hi Marko,

we need better hardware detection and enumeration and might have to add detailed feature mask to each modem. So we can tell if such a modem supports voice calls etc.

Regards

Marcel

Hi Marko,

Yes, oFono's current implementation does not understand hardware specifics. The current atmodem driver assumes a fully featured modem with perfect fluency in 27.007 & 27.005. Obviously this is wrong for real modems. Mostly this is because we were concentrating on getting the high level features working, before delving into hardware specifics.

I've seen this reported at least twice now. Which means that my SMS support detection in atmodem driver is probably not quite correct. Would you be able to report at which point in the drivers/atmodem/sms.c initialization that this fails?

27.005 defines at least some rudimentary way to detect whether SMS is supported by the modem or not. Unfortunately 27.007 doesn't have an equivalent for voice calls. The generic driver will do its best to figure out what is supported or not supported, but it will be up to the device-specific driver to have the final say.

Regards,
-Denis

Hi Denis,

With the Option iCON 225 USB modem the SMS error is sent in function at_cmgf_query_cb() at line 795.

795 return at_sms_not_supported(modem);

This is because the mode variable is always set to 0 at line 788 (while loop is executed only onces) and the supported stays at value FALSE:

788 while (g_at_result_iter_next_number(&iter, &mode))
789 if (mode == 1)
790 supported = TRUE;

I also tested oFono with the Nokia E51 phone which if I have understood correctly supports of sending SMS messages at least on Windows with PC Suite software. The result is a bit different.

With E51 the SMS error is returned from function at_cpms_query_cb() on line 764.

764 return at_sms_not_supported(modem);

This is because it does not go inside the while loop starting at line 741, and the me_supported and sm_supported stays FALSE:

740
741 while (g_at_result_iter_next_string(&iter, &store)) {
742 if (!strcmp(store, "ME"))
743 me_supported[mem] = TRUE;
744 else if (!strcmp(store, "SM"))
745 sm_supported[mem] = TRUE;
746 }
747

Regards,
Marko

Hi Marko,

This is me being dyslexic. It should be looking for mode == 0 instead.

This is strange, what does the E51 return for "AT+CPMS=?"

I've pushed fixes to the initialization and this is working at least for the Neo and on our simulator. Can you report if your devices get further?

Regards,
-Denis

Hi Denis,

With Option iCON 225 the SMS service started to work and I was also able to send SMS message with the following command:

$ dbus-send --system --print-reply --dest=org.ofono /modem1
org.ofono.SmsManager.SendMessage array:string:"+358000000000"
string:"ofono test message"

The Nokia E51 returns still the SMS error thing. To AT+CPMS=? the E51 returns the following:
+CPMS: (),(),()

OK

There is also following errors printed by the ofonod when modem is created with E51:

...
ofonod[14999]: at_crsm_info_cb got result: 0 ofonod[14999]: Final response: ERROR
ofonod[14999]: cops_numeric_cb got result: 1
...
ofonod[14999]: at_crsm_info_cb got result: 0 ofonod[14999]: Final response: ERROR
ofonod[14999]: cmgf_query_cb got result: 1
...
ofonod[14999]: at_crsm_info_cb got result: 0 ofonod[14999]: Final response: ERROR
ofonod[14999]: cpms_query_cb got result: 1
ofonod[14999]: Response line: +CPMS: (),(),() ofonod[14999]: SMS not supported by this modem. If this is in error please submit patches to support this hardware

Regards,
Marko

Hi,

I am using Nokia 6021 and there seems to be same problem(I guess):

ofonod[8320]: at_cpms_query_cb got result: 1 ofonod[8320]: Final response: OK
ofonod[8320]: Response line: +CPMS: ("ME","SM"),("ME","SM"),("MT") ofonod[8320]: at_cpms_query_cb
ofonod[8320]: SMS not supported by this modem. If this is in error please submit patches to support this hardware

Juha Korpi


Lainaus Marko Saukko <[email protected]>:

Hi Marko,

Excellent.

Are you running this over bluetooth? Perhaps this has a really cut down at command set in bluetooth serial profile. The other possibility is that you need to send some initialization commands first, (maybe AT+CFUN=1 would do it?)

Regards,
-Denis

Hi Juha,

Your problem is a bit different. CPMS here reports:
mem1: "ME", "SM"
mem2: "ME", "SM"
mem3: "MT"

oFono was confused by "MT" setting. I've added experimental support for such devices. Please report back if oFono gets further in the initialization process.

Regards,
-Denis

Hi Denis,

the experimental support was working fine. I was even able to send a SMS.

Thanks
Juha Korpi

Lainaus Denis Kenzior <[email protected]>:

Hi Denis,

I'm running the E51 over USB connection. The AT+CFUN=1 did not help:

AT+CFUN=1
OK
AT+CPMS=?
+CPMS: (),(),()

OK

P.S. The SMS service is also now working with Nokia 6100 (connected with
Nokia CA-42 cable).

Regards,
Marko

Hi Marko,

It sounds like the E51 doesn't have a proper AT command set for it to be supported by the generic driver. You can try to investigate whether it still sends the proper +CMT or +CMTI notifications on sms delivery (see 3GPP 27.005). If it does, then a custom sms driver for E51 could be feasible.

Regards,
-Denis