Skip to contentSkip to conversation

How to dismiss incoming call?

DISCUSSION Marko Saukko 3 participants 5 messages Aug 4, 2009 – Aug 7, 2009

lore
Share & tools
lore
#0 lore raw

Hi,

How can I dismiss incoming call without answering to it?

I tried the Busy method, as shown below:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Busy
method return sender=:1.277 -> dest=:1.284 reply_serial=2

Here is what the ofonod prints out:
...
ofonod[2049]: clcc_poll_cb got result: 1
ofonod[2049]: Final response: OK
ofonod[2049]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145 ofonod[2049]: cring_notify got result: 1
ofonod[2049]: Final response: (null)
ofonod[2049]: Response line: +CRING: VOICE
ofonod[2049]: clip_notify got result: 1
ofonod[2049]: Final response: (null)
ofonod[2049]: Response line: +CLIP: "+358000000000",145 ofonod[2049]: clip_notify: +358000000000 145 0
ofonod[2049]: Got a voicecall event, status: 4, id: 1, number: +358000000000 ofonod[2049]: Found call with id: 1
ofonod[2049]: clcc_poll_cb got result: 1
ofonod[2049]: Final response: OK
ofonod[2049]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145
...

...
ofonod[2049]: generic_cb got result: 1
ofonod[2049]: Final response: OK
...

These messages do not have any effect to the call itself. With E51 the only way to dismiss the call in receiving end is to first answer and then hangup.

In above tests the Nokia E51 was used (connected with USB cable).

With Nokia 6100 connected with USB cable the the busy method worked (call was ended), however the dbus send an error message as a response:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Busy
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

And here is the output by ofonod:

...
ofonod[1514]: Response line: +CRING: VOICE
ofonod[1514]: cring_notify
ofonod[1514]: clip_notify got result: 1
ofonod[1514]: Final response: (null)
ofonod[1514]: Response line: +CLIP: "+358000000000",145 ofonod[1514]: clip_notify: +358000000000 145 0
ofonod[1514]: Got a voicecall event, status: 4, id: 1, number: +358000000000 ofonod[1514]: Did not find a call with id: 1
ofonod[1514]: Resetting updating flag
ofonod[1514]: clcc_poll_cb got result: 0
ofonod[1514]: Final response: ERROR
ofonod[1514]: We are polling CLCC and CLCC resulted in an error ofonod[1514]: All bets are off for call management

after this nothing else was printed even when the busy was sent.

oFono version 0.2 was used.

Regards,
Marko

#1 lore raw

Well its been a long time since i work with mobile fones but there should be some blockking scripts which just directly reject the call. cant remember how but if i do i can answer

2009/8/4 Marko Saukko <[email protected]>

Quoted 87 lines

Hi,

How can I dismiss incoming call without answering to it?

I tried the Busy method, as shown below:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Busy
method return sender=:1.277 -> dest=:1.284 reply_serial=2

Here is what the ofonod prints out:
...
ofonod[2049]: clcc_poll_cb got result: 1
ofonod[2049]: Final response: OK
ofonod[2049]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145 ofonod[2049]: cring_notify got result: 1
ofonod[2049]: Final response: (null)
ofonod[2049]: Response line: +CRING: VOICE ofonod[2049]: clip_notify got result: 1
ofonod[2049]: Final response: (null)
ofonod[2049]: Response line: +CLIP: "+358000000000",145 ofonod[2049]: clip_notify: +358000000000 145 0 ofonod[2049]: Got a voicecall event, status: 4, id: 1, number:
+358000000000
ofonod[2049]: Found call with id: 1
ofonod[2049]: clcc_poll_cb got result: 1
ofonod[2049]: Final response: OK
ofonod[2049]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145
...

...
ofonod[2049]: generic_cb got result: 1
ofonod[2049]: Final response: OK
...

These messages do not have any effect to the call itself. With E51 the only way to dismiss the call in receiving end is to first answer and then hangup.

In above tests the Nokia E51 was used (connected with USB cable).

With Nokia 6100 connected with USB cable the the busy method worked (call was ended), however the dbus send an error message as a response:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Busy
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

And here is the output by ofonod:

...
ofonod[1514]: Response line: +CRING: VOICE ofonod[1514]: cring_notify
ofonod[1514]: clip_notify got result: 1
ofonod[1514]: Final response: (null)
ofonod[1514]: Response line: +CLIP: "+358000000000",145 ofonod[1514]: clip_notify: +358000000000 145 0 ofonod[1514]: Got a voicecall event, status: 4, id: 1, number:
+358000000000
ofonod[1514]: Did not find a call with id: 1 ofonod[1514]: Resetting updating flag
ofonod[1514]: clcc_poll_cb got result: 0 ofonod[1514]: Final response: ERROR
ofonod[1514]: We are polling CLCC and CLCC resulted in an error ofonod[1514]: All bets are off for call management

after this nothing else was printed even when the busy was sent.

oFono version 0.2 was used.

Regards,
Marko
_______________________________________________
ofono mailing list
ofono(a)ofono.org
http://lists.ofono.org/listinfo/ofono

Signature · 1 line
Ceyhun ALYEŞİL
#2 lore raw
In reply to Marko Saukko

Hi,

Nokia 6100 responds ERROR when AT+CLCC is sent:

AT+CLCC
ERROR

With 6100 the Hangup returns timeout:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Hangup
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

When sending Busy with the nokia 6100 the first time it seems to works as it should (Even though CLCC is returning ERROR). When trying second time in a row, without closing ofonod, it also sends busy to the originator, but to the dbus message Error org.freedesktop.DBus.Error.NoReply is returned.

With Nokia E51 when Hangup is sent to incoming call the result is following:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Hangup
Error org.ofono.Error.Failed: Operation failed

And during this the ofonod prints following:

...
ofonod[1812]: clcc_poll_cb got result: 1
ofonod[1812]: Final response: OK
ofonod[1812]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145 ofonod[1812]: release_id_cb got result: 0
ofonod[1812]: Final response: ERROR
ofonod[1812]: command failed with error: (null) ofonod[1812]: clcc_poll_cb got result: 1
ofonod[1812]: Final response: OK
ofonod[1812]: Response line: +CLCC: 1,1,4,0,0,"+358000000000",145
...

Ps. Nokia 6290 has similar behavior than Nokia E51.

These tests were done with the latest git version.

Regards,
Marko

#3 lore raw

Hi Marko,

Quoted 5 lines

When sending Busy with the nokia 6100 the first time it seems to works as it should (Even though CLCC is returning ERROR). When trying second time in a row, without closing ofonod, it also sends busy to the originator, but to the dbus message Error org.freedesktop.DBus.Error.NoReply is returned.

If CLCC is returning an error, there's no hope of the default plugin working. You will need to do some digging to figure out whether its possible to support this device.

Quoted 6 lines

With Nokia E51 when Hangup is sent to incoming call the result is following:

$ sudo dbus-send --system --print-reply --dest=org.ofono
/modem1/voicecall01 org.ofono.VoiceCall.Hangup
Error org.ofono.Error.Failed: Operation failed

For hangup oFono sends a AT+CHLD=1<callid>, which is most likely 1. So AT+CHLD=11. For busy, oFono sends AT+CHLD=0. If these result in errors, the default plugin will not work.

It might be that the modem is using a neutered command set. Can you find out whether CHLD=11 works, whether AT+CHLD=0 works, whether AT+CHUP works and whether ATH works? Most likely this hardware will need a custom driver.

Regards,
-Denis

#4 lore raw

Hi Denis,

With Nokia E51 AT+CHLD=11 returned ERR0R, AT+CHLD=0 and ATH returned OK however they did not have effect to the call. AT+CHUP returned OK and call was terminated (Caller received busy signal).

RING
AT+CHLD=11
ERROR

RING

RING
AT+CHLD=0
OK

RING

RING
ATH
OK

RING

RING
AT+CHUP
OK

Regards,
Marko