[asterisk-bugs] [Asterisk 0011556]: "No audio" on incoming bluetooth call to voicemail, call dropped
noreply at bugs.digium.com
noreply at bugs.digium.com
Sat May 3 14:29:19 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11556
======================================================================
Reported By: non-poster
Assigned To: dbowerman
======================================================================
Project: Asterisk
Issue ID: 11556
Category: Addons/chan_mobile
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 92526
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 12-14-2007 14:55 CST
Last Modified: 05-03-2008 14:29 CDT
======================================================================
Summary: "No audio" on incoming bluetooth call to voicemail,
call dropped
Description:
I have "context=incoming-mobile" in mobile.conf for my bluetooth phone. It
connects, and Asterisk indicates that "Usable" for voice = "Yes", "Type" =
"Phone".
The incoming-mobile context directs the call to voicemail:
context incoming-mobile {
_. => {
VoiceMail(9999,b);
Hangup();
};
}
When I call the bluetooth phone, I hear the outgoing voicemail message
"...9999 is busy... leave message...beep", then the call is dropped. The
logs contain:
channel.c:2992 in set_format: Set channel Mobile/SCP2500-f304 to write
format slin
-- Recording the message
app.c:603 in __ast_play_and_record: Recording Formats: sfmts=sln
rtp.c:1089 in ast_rtcp_read: Got RTCP report of 104 bytes
app.c:657 in __ast_play_and_record: One waitfor failed, trying another
app.c:661 in __ast_play_and_record: No audio available on
Mobile/SCP2500-f304??
channel.c:1465 in ast_hangup: Hanging up channel 'Mobile/SCP2500-f304'
chan_mobile.c:667 in mbl_hangup: Hanging up device SCP2500.
The chan_mobile messages:
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [+CIEV:
3,1]
chan_mobile.c:1418 in do_monitor_phone: Device SCP2500 [+CIEV: 3,1]
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [RING]
chan_mobile.c:1418 in do_monitor_phone: Device SCP2500 [RING]
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [+CLIP:
"206xxxyyyy",129]
chan_mobile.c:1002 in rfcomm_write: rfcomm_write() (SCP2500) [ATA ]
chan_mobile.c:869 in mbl_devicestate: Checking device state for device
SCP2500
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [OK]
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [+CIEV:
2,1]
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [+CIEV:
3,0]
chan_mobile.c:1831 in do_sco_listen: accept()ed socket.
chan_mobile.c:1836 in do_sco_listen: Incoming Audio Connection from device
00:00:A0:2E:XX:XX MTU is 64
chan_mobile.c:1828 in do_sco_listen: About to accept() socket.
chan_mobile.c:943 in do_alignment_detection: Alignment Detection result is
[0 0 0 0]
chan_mobile.c:667 in mbl_hangup: Hanging up device SCP2500.
chan_mobile.c:1002 in rfcomm_write: rfcomm_write() (SCP2500) [AT+CHUP ]
chan_mobile.c:869 in mbl_devicestate: Checking device state for device
SCP2500
chan_mobile.c:869 in mbl_devicestate: Checking device state for device
SCP2500
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [OK]
chan_mobile.c:1326 in do_monitor_phone: rfcomm_read() (SCP2500) [+CIEV:
2,0]
chan_mobile.c:1418 in do_monitor_phone: Device SCP2500 [+CIEV: 2,0]
======================================================================
----------------------------------------------------------------------
jmls - 05-03-08 14:29
----------------------------------------------------------------------
qwell - any further thoughts ?
Issue History
Date Modified Username Field Change
======================================================================
05-03-08 14:29 jmls Note Added: 0086369
======================================================================
More information about the asterisk-bugs
mailing list