Hi Nicola,

> that's happen with oFono 0.38 on freerunner with debian sid on the
> first incoming/outgoing call:
> 
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() id:1,
> msgtype:0, direction:1, mode:0
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() Len > 0
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() type obtained
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify()
> num:+xxxxxxxxxxxx, type:145
> ofonod[6232]: drivers/calypsomodem/voicecall.c:cpi_notify() cause:892800, line:0
> ofonod[6232]: src/voicecall.c:ofono_voicecall_notify() Got a voicecall
> event, status: 4, id: 1, number: +xxxxxxxxxxx
> ofonod[6232]: src/voicecall.c:ofono_voicecall_notify() Did not find a
> call with id: 1
> ofonod[6232]: System bus has disconnected!

this happens if something in a D-Bus message is corrupted and the D-Bus
daemon complains. The result is that it kicks us off the bus.

You need to track down which D-Bus API call causes this. Wild assumption
is that it is either a wrong message parameter or an invalid object
path.

Regards

Marcel