Re: Outgoing call from AG fails

Re: Outgoing call from AG fails

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

Hi Bret,

On 08/07/2012 04:58 PM, Bret Hassler wrote:
> I have a handsfree unit with ofono connecting to a VTech landline phone
> as audio gateway. On outgoing calls, the only HFP notification for the
> call is only a +CIEV: call status,1.
>

call indicator should not be going to 1 without first having the 
callsetup indicator going to 1.  Doesn't sound like this is a proper HFP 
device.  What type of device is this?

> drivers/hfpmodem/voicecall.c: ciev_call_notify() will not do anything if
> without a call already created. The VTech phone also returns error to
> AT+CLCC command.
>
> I am thinking to create the ofono_call in drivers/hfpmodem/voicecall.c:
> ciev_call_notify() if no call has been created. However, this might have
> big impacts other phones. Specifically, does “+CIEV: call status,1” get
> emitted outside of standard phone calls, such as for alarms or
> notifications with some phones? Any thoughts on this?
>

Instead of hcidump you might want to use the built-in oFono AT logging. 
  See HACKING for details.

Regards,
-Denis

Outgoing call from AG fails

[Bret Hassler]

[-- Attachment #1: Type: text/plain, Size: 2740 bytes --]

I have a handsfree unit with ofono connecting to a VTech landline phone as audio gateway. On outgoing calls, the only HFP notification for the call is only a +CIEV: call status,1.
drivers/hfpmodem/voicecall.c: ciev_call_notify() will not do anything if without a call already created.  The VTech phone also returns error to AT+CLCC command.

I am thinking to create the ofono_call in drivers/hfpmodem/voicecall.c: ciev_call_notify() if no call has been created. However, this might have big impacts other phones. Specifically, does "+CIEV: call status,1" get emitted outside of standard phone calls, such as for alarms or notifications with some phones? Any thoughts on this?

The following is the hcidump for an outgoing call and hangup from the audio gateway:

> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 1 mode 0x00 interval 0
    Mode: Active
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 1 slots 5
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 1 slots 1
> HCI Event: Connect Request (0x04) plen 10
    bdaddr 00:11:A0:23:54:B6 class 0x000000 type eSCO
< HCI Command: Accept Synchronous Connection (0x01|0x0029) plen 21
    bdaddr 00:11:A0:23:54:B6
    @ . . . @ . . . . . ` . . ? .
> HCI Event: Command Status (0x0f) plen 4
    Accept Synchronous Connection (0x01|0x0029) status 0x00 ncmd 1
> HCI Event: Synchronous Connect Complete (0x2c) plen 17
    status 0x00 handle 257 bdaddr 00:11:A0:23:54:B6 type eSCO
    Air mode: CVSD
> ACL data: handle 1 flags 0x02 dlen 22
    L2CAP(d): cid 0x0041 len 18 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 8 pf 0 ilen 14 fcs 0x80
      . . + C I E V :   1 , 1 . .
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 1 mode 0x02 interval 150
    Mode: Sniff
> HCI Event: Sniff Subrate (0x2e) plen 11
    status 0x00 handle 1
    max latency transmit 150 receive 1200
    min timeout remote 0 local 2

> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 257 reason 0x13
    Reason: Remote User Terminated Connection
> ACL data: handle 1 flags 0x02 dlen 22
    L2CAP(d): cid 0x0041 len 18 [psm 3]
      RFCOMM(d): UIH: cr 0 dlci 8 pf 0 ilen 14 fcs 0x80
      . . + C I E V :   1 , 0 . .
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 1 mode 0x00 interval 0
    Mode: Active
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 1 slots 5
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 1 slots 1
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 1 mode 0x02 interval 798
    Mode: Sniff
> HCI Event: Sniff Subrate (0x2e) plen 11
    status 0x00 handle 1
    max latency transmit 798 receive 798
    min timeout remote 0 local 2


Regards,
Bret


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 7510 bytes --]

RE: Outgoing call from AG fails

[Bret Hassler]

[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]

It's a Vtech DS6321-3.
https://www.bluetooth.org/tpg/EPL_Detail.cfm?ProductID=13096
It provides a Handsfree Gateway service. I was wondering if it doesn't send any callsetup indicators because it is not cellular. Otherwise, you're probably correct that it's not a proper device.

-Bret

-----Original Message-----
From: Denis Kenzior [mailto:denkenz(a)gmail.com] 
Sent: Tuesday, August 07, 2012 8:17 AM
To: ofono(a)ofono.org
Cc: Bret Hassler
Subject: Re: Outgoing call from AG fails

Hi Bret,

On 08/07/2012 04:58 PM, Bret Hassler wrote:
> I have a handsfree unit with ofono connecting to a VTech landline 
> phone as audio gateway. On outgoing calls, the only HFP notification 
> for the call is only a +CIEV: call status,1.
>

call indicator should not be going to 1 without first having the callsetup indicator going to 1.  Doesn't sound like this is a proper HFP device.  What type of device is this?

> drivers/hfpmodem/voicecall.c: ciev_call_notify() will not do anything 
> if without a call already created. The VTech phone also returns error 
> to
> AT+CLCC command.
>
> I am thinking to create the ofono_call in drivers/hfpmodem/voicecall.c:
> ciev_call_notify() if no call has been created. However, this might 
> have big impacts other phones. Specifically, does "+CIEV: call 
> status,1" get emitted outside of standard phone calls, such as for 
> alarms or notifications with some phones? Any thoughts on this?
>

Instead of hcidump you might want to use the built-in oFono AT logging. 
  See HACKING for details.

Regards,
-Denis

Re: Outgoing call from AG fails

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]

Hi Bret,

Just a heads up: it is customary to not top-post on open source mailing 
lists.  So please don't do that in the future ;)

On 08/08/2012 07:36 AM, Bret Hassler wrote:
> It's a Vtech DS6321-3.
> https://www.bluetooth.org/tpg/EPL_Detail.cfm?ProductID=13096
> It provides a Handsfree Gateway service. I was wondering if it doesn't send any callsetup indicators because it is not cellular. Otherwise, you're probably correct that it's not a proper device.
>

HFP 1.6 does explicitly state that callsetup is required in the case of 
an outgoing call being dialed from the HF.  There is no equivalent 
sequence diagram for the call being dialed from the AG, however this is 
mandated by TR002.  So from that standpoint you're a little bit unlucky 
in that your device is not really compliant.

Just quickly glancing at the product page, it does indicate mobile phone 
compatibility.  Maybe the HFP part is only meant when you're using it 
with a mobile network.

That said, you can try to hack around this a bit by detecting the call=0 
-> call=1 transition regardless of callsetup, but you'd still be missing 
any sort of dialed number information, etc.  Not sure how really useful 
oFono would be for this usecase.

Regards,
-Denis