[asterisk-bugs] [Asterisk 0011368]: chan_mobile does not recognize dtmf together with Authenticate or DISA
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat May 2 18:11:34 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11368
======================================================================
Reported By: bt047265
Assigned To: mnicholson
======================================================================
Project: Asterisk
Issue ID: 11368
Category: Addons/chan_mobile
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 89454
Request Review:
======================================================================
Date Submitted: 2007-11-25 08:42 CST
Last Modified: 2009-05-02 18:11 CDT
======================================================================
Summary: chan_mobile does not recognize dtmf together with
Authenticate or DISA
Description:
Hello,
chan_mobile is configured according to the documentation. Incoming and
outgoing calls are working via the new channel "Mobile".
Mobile.conf:
[adapter]
id=stick1
address=00:08:F4:16:3A:E2
[SGH-F200]
;address=00:1D:25:73:0E:76
address=00:1B:59:14:77:38
port=4
context=incoming_mobile
adapter=stick1
dtmfskip=50
This dialplan was added to the extensions.conf:
[incoming_mobile]
exten => _!,1,Answer()
exten => _!,n,Wait(1)
exten => _!,n,Verbose(${EXTEN})
exten => _!,n,Verbose(${CALLERID})
exten => _!,n,Authenticate(1234)
exten => _!,n,Background(vm-enter-num-to-call)
exten => _!,n,DISA(no-password,phones,"sipgate" <7001>)
No DTMF tones are regocnized by the Authenticate function. If the same
context is assigned to the SIP channel Authenticate and DISA is working.
Attached the output of /var/log/asterisk/full for:
- incoming mobile authenticate
- icoming mobile to SIP extension
- incoming SIP authenticate
If the incoming call from the mobile is directly routed to an SIP
extension, DTMF is sended to the SIP extension.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0011801 mobile to asterisk audio stability stro...
has duplicate 0012768 Multipile issues with chan_mobile
has duplicate 0011556 "No audio" on incoming blueto...
related to 0012567 Big latency (up to 3 sec) when call wai...
======================================================================
----------------------------------------------------------------------
(0104064) ughnz (reporter) - 2009-05-02 18:11
http://bugs.digium.com/view.php?id=11368#c104064
----------------------------------------------------------------------
I agree with alexz, there must be some difference in setup somewhere.
Here is my setup:
- VIA PC-1 system. 1.5GHz CPU with 1G RAM.
- Centos 5.3
- Bluez 3.36
- CSR chipset dongle
- Vodafone 715 mobile
- Asterisk 1.6.1.0 Release
- DAHDI 2.1.0.4
mobile.conf:
;
; mobile.conf
; configuration file for chan_mobile
;
[general]
interval=30 ; Number of seconds between trying to connect to devices.
; The following is a list of adapters we use.
; id must be unique and address is the bdaddr of the adapter from
hciconfig.
; Each adapter may only have one device (headset or phone) connected at a
time.
; Add an [adapter] entry for each adapter you have.
[adapter]
id=blue
address=xx:xx:xx:xx:xx:xx
;forcemaster=yes
alignmentdetection=yes
;nocallsetup=yes
;[adapter]
;id=blue1
;address=xx:xx:xx:xx:xx:xx
;alignmentdetection=yes
; The following is a list of the devices we deal with.
; Every device listed below will be available for calls in and out of
Asterisk.
; Each device needs an adapter=xxxx entry which determines which bluetooth
adapter is used.
; Use the CLI command 'mobile search' to discover devices.
; Use the CLI command 'mobile show devices' to see device status.
;
; To place a call out through a mobile phone use
Dial(Mobile/[device]/NNN.....) in your dialplan.
; To call a headset use Dial(Mobile/[device]).
[TRUNK]
address=xx:xx:xx:xx:xx:xx ; the address of the phone
port=4 ; the rfcomm port number (from mobile search)
context=from-pstn ; dialplan context for incoming calls
adapter=blue ; adapter to use
dtmfskip=100
;[n95]
;address=xx:xx:xx:xx:xx:xx
;port=3
;context=from-pstn
;adapter=blue1
;dtmfskip=50
hcid.conf:
#
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "1234";
}
# Default settings for HCI devices
device xx:xx:xx:xx:xx:xx {
# Local device name
# %d - device id
# %h - host name
name "trixbox";
# Local device class
class 0x200408;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
#lp rswitch,hold,sniff,park;
}
device xx:xx:xx:xx:xx:xx {
name "trixbox1";
class 0x200408;
iscan enable; pscan enable;
lm accept;
}
hciconfig -a output:
hci0: Type: USB
BD Address: xx:xx:xx:xx:xx:xx ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:384753 acl:376 sco:7232 events:487 errors:0
TX bytes:180438 acl:225 sco:3426 commands:112 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'trixbox'
Class: 0x080408
Service Classes: Capturing
Device Class: Audio/Video, Hands-free
HCI Ver: 2.0 (0x3) HCI Rev: 0xc5c LMP Ver: 2.0 (0x3) LMP Subver:
0xc5c
Manufacturer: Cambridge Silicon Radio (10)
sdptool browse output:
Service Name: Voice Gateway
Service RecHandle: 0x10000
Service Class ID List:
"Handsfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: A2DP Source
Service RecHandle: 0x10002
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0100
Service Name: AVRCP Target
Service RecHandle: 0x10003
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x100
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0100
Service Name: Serial Port
Service RecHandle: 0x10004
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 16
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Serial Port" (0x1101)
Version: 0x0100
Service Name: Information Synchronization
Service RecHandle: 0x10005
Service Class ID List:
"IrMC Sync" (0x1104)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 17
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"IrMC Sync" (0x1104)
Version: 0x0100
Service Name: Object Push
Service RecHandle: 0x10006
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 18
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
Service Name: File Transfer
Service RecHandle: 0x10007
Service Class ID List:
"OBEX File Transfer" (0x1106)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 19
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"OBEX File Transfer" (0x1106)
Version: 0x0100
Issue History
Date Modified Username Field Change
======================================================================
2009-05-02 18:11 ughnz Note Added: 0104064
======================================================================
More information about the asterisk-bugs
mailing list