[Home]

Summary:ASTERISK-12122: Multipile issues with chan_mobile
Reporter:BrettS (ughnz)Labels:
Date Opened:2008-06-01 22:13:30Date Closed:2008-06-02 07:35:09
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Addons/chan_mobile
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I am using chan_mobile for V1.4 from the trixbox team.

I am having several issues which I am not able to pin down to chan_mobile, bluez or asterisk itself.

I have looked for some documentation on chan_mobile in order to try and figure out where the problems are but am not able to find anything.

First issue is my phone will not leave the init state when chan_mobile first connects to the phone. After I have made an outgoing call it will return to free state.
I have tracked this down to my phone not responding to the [AT+CMGF=1] command.
Would it be possible to add an option to not do SMS detection on the phone?

Second issue is the phone seems to drop off the system, for a better way of putting it. When it does the log file shows:
[Jun  1 04:02:53] DEBUG[2870] chan_mobile.c: connect() failed (112).
Sometimes the reason code is 110. I have looked to try and find what these reason codes are but cannot find anything.
Only after I have rebooted the PC or cycled the power on the phone will chan_mobile re-connect.
I do not know if this is related but my phone will send lots of these messages at regular intervals:
[May 31 04:19:41] DEBUG[3385] chan_mobile.c: Device N95 [+CIEV: 4,1]
[May 31 04:19:42] DEBUG[3385] chan_mobile.c: rfcomm_read() (N95) [+CIEV: 4,3]
[May 31 04:19:42] DEBUG[3385] chan_mobile.c: Device N95 [+CIEV: 4,3]
[May 31 04:43:42] DEBUG[3385] chan_mobile.c: rfcomm_read() (N95) [+CIEV: 4,1]
[May 31 04:43:42] DEBUG[3385] chan_mobile.c: Device N95 [+CIEV: 4,1]
[May 31 04:43:44] DEBUG[3385] chan_mobile.c: rfcomm_read() (N95) [+CIEV: 4,2]

Third issue is DISA will not work. Any attempt to use DISA with chan_mobile will result in a deadlock of the DISA app with the phone stuck in busy state.
Only completly downing asterisk and bringing it back up again will kill the deadlocked DISA app and release the phone.

Fourth issue is audio streams. It seems that if no RTP traffic is being sent from a SIP channel while using chan_mobile no audio is being sent from chan_mobile.
This can be re-produced by using a SIP client, such as BOL Sip Phone, and making a call out on the mobile then turn the mic gain on the BOL client right down, effectively muting the mic, and you will hear nothing from the mobile.

Another issue is compatible adapters. I have two USB bluetooth adapters, both which will work OK with windows and audio devices, but only one will work with chan_mobile.
Where do we find information on what features are needed for the adapter to work with chan_mobile?
NOTE I have asked what features are needed for chan_mobile to work as just going by what adapters are supported under bluez is not enough.

I have a phone that does not have any audio at all. chan_mobile will connect to it, make outgoing calls and answer incoming calls but no audio. Trying to find out where to start on fault finding this problem comes to a dead end as there is no information on what codecs etc are needed / used by chan_mobile, assuming it is a codec issue?

Please help us help you make chan_mobile a killer app for asterisk by giving us some useful documentation for cahn_mobile.

Thanks Brett.



****** ADDITIONAL INFORMATION ******

astersik 1.4.20.1
bluez 3.32
Linux CentPBX.local 2.6.18-53.1.21.el5 #1 SMP Tue May 20 09:34:18 EDT 2008 i686 i686 i386 GNU/Linux
chan_mobile rev 454 from the trixbox team.
Comments:By: Joshua C. Colp (jcolp) 2008-06-02 07:35:09

This is a duplicate of the three issues I have associated with this issue. As well we do not support patched systems on this issue tracker, you will need to use Asterisk 1.6 or trunk.