thr3ads.net - asterisk users - [asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems [Sep 2012]

If this information is useful, please help other people find it:
Share via:

Raj Mathur (राज माथुर)

2012-Sep-14 03:26 UTC

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

Hi,

Continuing with the saga of Digium vs MTNL Mumbai, looking for
suggestions on handling incoming Caller-ID issues.  The card manages to
grab a couple of (random) digits of the incoming CID, but they're more
or less useless.  Is there any way to fix this?

Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL Mumbai.
Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)

chan_dahdi.conf contains:
usecallerid = yes
cidsignalling=dtmf
cidstart=polarity_in

Signalling is fxsks.

Log (calling number is 9811066XXX):
[Sep 14 08:21:11] DEBUG[9337]: chan_dahdi.c:11895 do_monitor: Monitor doohicky 
got event Ring Begin on channel 1
[Sep 14 08:21:11] DEBUG[9337]: sig_analog.c:3621 analog_handle_init_event: 
channel (1) - signaling (5) - event (ANALOG_EVENT_RINGBEGIN)
[Sep 14 08:21:11] DEBUG[9337]: chan_dahdi.c:11895 do_monitor: Monitor doohicky 
got event Ring/Answered on channel 1
[Sep 14 08:21:11] DEBUG[9337]: sig_analog.c:3621 analog_handle_init_event: 
channel (1) - signaling (5) - event (ANALOG_EVENT_RINGOFFHOOK)
[Sep 14 08:21:11] DEBUG[9337]: dsp.c:471 ast_tone_detect_init: Setup tone 1100 
Hz, 500 ms, block_size=160, hits_required=21
[Sep 14 08:21:11] DEBUG[9337]: dsp.c:471 ast_tone_detect_init: Setup tone 2100 
Hz, 2600 ms, block_size=160, hits_required=116
[Sep 14 08:21:11] DEBUG[9337]: dsp.c:1576 ast_dsp_set_busy_pattern: dsp busy 
pattern set to 0,0
[Sep 14 08:21:11] DEBUG[9315]: devicestate.c:340 _ast_device_state: No provider 
found, checking channel drivers for DAHDI - 1
[Sep 14 08:21:11] DEBUG[9315]: devicestate.c:458 do_state_change: Changing state
for DAHDI/1 - state 2 (In use)
[Sep 14 08:21:11] DEBUG[9315]: devicestate.c:438 devstate_event: device
'DAHDI/1'
state '2'
[Sep 14 08:21:11] DEBUG[11186]: sig_analog.c:1769 __analog_ss_thread: 
__analog_ss_thread 1
    -- Starting simple switch on 'DAHDI/1-1'
[Sep 14 08:21:11] DEBUG[11186]: sig_analog.c:2392 __analog_ss_thread: Receiving 
DTMF cid on channel DAHDI/1-1
[Sep 14 08:21:11] DEBUG[9350]: app_queue.c:1487 handle_statechange: Device 
'DAHDI/1' changed to state '2' (In use) but we don't care
because they're not a
member of any queue.
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf: Begin DTMF
digit: 0x31 '1' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x31 '1' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: dsp.c:1424 ast_dsp_process: DTMF Detected -
Reset
busydetector
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf: End DTMF 
digit: 0x31 '1' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF
digit:
0x31 '1' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:2426 __analog_ss_thread: CID got 
digit '1'
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf: Begin DTMF
digit: 0x36 '6' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: Begin DTMF 
digit: 0x36 '6' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: dsp.c:1424 ast_dsp_process: DTMF Detected -
Reset
busydetector
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf: End DTMF 
digit: 0x36 '6' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: End DTMF
digit:
0x36 '6' on DAHDI/1-1
[Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:2426 __analog_ss_thread: CID got 
digit '6'
[Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:3509 analog_exception: 
analog_exception 1
[Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:3603 analog_exception: Exception on
16, channel 1
[Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:2660 __analog_handle_event: 
__analog_handle_event 1
[Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:2687 __analog_handle_event: Got 
event ANALOG_EVENT_RINGBEGIN(12) on channel 1 (index 0)
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3509 analog_exception: 
analog_exception 1
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3603 analog_exception: Exception on
16, channel 1
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2660 __analog_handle_event: 
__analog_handle_event 1
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2687 __analog_handle_event: Got 
event ANALOG_EVENT_RINGOFFHOOK(2) on channel 1 (index 0)
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3043 __analog_handle_event: Ring 
detected
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2441 __analog_ss_thread: CID got 
string '16'
[Sep 14 08:21:14] WARNING[11186]: callerid.c:243 callerid_get_dtmf: Couldn't
detect start-character. CID parsing might be unreliable
[Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2443 __analog_ss_thread: CID is 
'16', flags 0
[Sep 14 08:21:14] DEBUG[9315]: devicestate.c:340 _ast_device_state: No provider 
found, checking channel drivers for DAHDI - 1
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:3239 ast_str_retrieve_variable: Result of 
'EXTEN' is 's'
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper: Launching
'NoOp'
[Sep 14 08:21:14] DEBUG[9315]: devicestate.c:458 do_state_change: Changing state
for DAHDI/1 - state 2 (In use)
[Sep 14 08:21:14] DEBUG[9315]: devicestate.c:438 devstate_event: device
'DAHDI/1'
state '2'
    -- Executing [s at incoming:1] NoOp("DAHDI/1-1", "Incoming
s") in new stack
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:4058 pbx_substitute_variables_helper_full:
Function result is '16'
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper: Launching 
'Verbose'
    -- Executing [s at incoming:2] Verbose("DAHDI/1-1", "CID
16") in new stack
CID 16
[Sep 14 08:21:14] DEBUG[9350]: app_queue.c:1487 handle_statechange: Device 
'DAHDI/1' changed to state '2' (In use) but we don't care
because they're not a
member of any queue.
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper: Launching
'Set'
    -- Executing [s at incoming:3] Set("DAHDI/1-1",
"SPYGROUP=queue-01") in new
stack
[Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper: Launching 
'Answer'

More information available on request.

Incidentally, are we entitled to Digium support for these issues on
this card?

Regards,

-- Raj
-- 
Raj Mathur                          || raju at kandalaya.org   || GPG:
http://otheronepercent.blogspot.com || http://kandalaya.org || CC68
It is the mind that moves           || http://schizoid.in   || D17F

Patrick Lists

2012-Sep-14 07:34 UTC

head link

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

On 09/14/2012 05:26 AM, Raj Mathur (??? ?????) wrote:
[snip]> Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL Mumbai.
> Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)
Your DAHDI and Asterisk versions are old so for starters I would update 
everything to the latest releases. See asterisk.org.

Regards,
Patrick

Richard Mudgett

2012-Sep-14 15:22 UTC

head link

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

> Continuing with the saga of Digium vs MTNL Mumbai, looking for
> suggestions on handling incoming Caller-ID issues.  The card manages
> to
> grab a couple of (random) digits of the incoming CID, but they're
> more
> or less useless.  Is there any way to fix this?
> 
> Asterisk 1.8.13, Dahdi 2.5.0.1 on Debian Testing (Wheezy), MTNL
> Mumbai.
> Digium, Inc. Wildcard AEX410 4-port analog card (PCI-Express)
> 
> chan_dahdi.conf contains:
> usecallerid = yes
> cidsignalling=dtmf
> cidstart=polarity_in
> 
> Signalling is fxsks.
> 
> Log (calling number is 9811066XXX):
> [Sep 14 08:21:11] DEBUG[9337]: chan_dahdi.c:11895 do_monitor: Monitor
> doohicky
> got event Ring Begin on channel 1
> [Sep 14 08:21:11] DEBUG[9337]: sig_analog.c:3621
> analog_handle_init_event:
> channel (1) - signaling (5) - event (ANALOG_EVENT_RINGBEGIN)
> [Sep 14 08:21:11] DEBUG[9337]: chan_dahdi.c:11895 do_monitor: Monitor
> doohicky
> got event Ring/Answered on channel 1
> [Sep 14 08:21:11] DEBUG[9337]: sig_analog.c:3621
> analog_handle_init_event:
> channel (1) - signaling (5) - event (ANALOG_EVENT_RINGOFFHOOK)
> [Sep 14 08:21:11] DEBUG[9337]: dsp.c:471 ast_tone_detect_init: Setup
> tone 1100
> Hz, 500 ms, block_size=160, hits_required=21
> [Sep 14 08:21:11] DEBUG[9337]: dsp.c:471 ast_tone_detect_init: Setup
> tone 2100
> Hz, 2600 ms, block_size=160, hits_required=116
> [Sep 14 08:21:11] DEBUG[9337]: dsp.c:1576 ast_dsp_set_busy_pattern:
> dsp busy
> pattern set to 0,0
> [Sep 14 08:21:11] DEBUG[9315]: devicestate.c:340 _ast_device_state:
> No provider
> found, checking channel drivers for DAHDI - 1
> [Sep 14 08:21:11] DEBUG[9315]: devicestate.c:458 do_state_change:
> Changing state
> for DAHDI/1 - state 2 (In use)
> [Sep 14 08:21:11] DEBUG[9315]: devicestate.c:438 devstate_event:
> device 'DAHDI/1'
> state '2'
> [Sep 14 08:21:11] DEBUG[11186]: sig_analog.c:1769 __analog_ss_thread:
> __analog_ss_thread 1
>     -- Starting simple switch on 'DAHDI/1-1'
> [Sep 14 08:21:11] DEBUG[11186]: sig_analog.c:2392 __analog_ss_thread:
> Receiving
> DTMF cid on channel DAHDI/1-1
> [Sep 14 08:21:11] DEBUG[9350]: app_queue.c:1487 handle_statechange:
> Device
> 'DAHDI/1' changed to state '2' (In use) but we don't
care because
> they're not a
> member of any queue.
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf:
> Begin DTMF
> digit: 0x31 '1' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf:
> Begin DTMF
> digit: 0x31 '1' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: dsp.c:1424 ast_dsp_process: DTMF
> Detected - Reset
> busydetector
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf:
> End DTMF
> digit: 0x31 '1' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: End
> DTMF digit:
> 0x31 '1' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:2426 __analog_ss_thread:
> CID got
> digit '1'
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf:
> Begin DTMF
> digit: 0x36 '6' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf:
> Begin DTMF
> digit: 0x36 '6' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: dsp.c:1424 ast_dsp_process: DTMF
> Detected - Reset
> busydetector
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:1602 analog_handle_dtmf:
> End DTMF
> digit: 0x36 '6' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: chan_dahdi.c:2026 my_handle_dtmf: End
> DTMF digit:
> 0x36 '6' on DAHDI/1-1
> [Sep 14 08:21:12] DEBUG[11186]: sig_analog.c:2426 __analog_ss_thread:
> CID got
> digit '6'
> [Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:3509 analog_exception:
> analog_exception 1
> [Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:3603 analog_exception:
> Exception on
> 16, channel 1
> [Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:2660
> __analog_handle_event:
> __analog_handle_event 1
> [Sep 14 08:21:13] DEBUG[11186]: sig_analog.c:2687
> __analog_handle_event: Got
> event ANALOG_EVENT_RINGBEGIN(12) on channel 1 (index 0)
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3509 analog_exception:
> analog_exception 1
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3603 analog_exception:
> Exception on
> 16, channel 1
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2660
> __analog_handle_event:
> __analog_handle_event 1
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2687
> __analog_handle_event: Got
> event ANALOG_EVENT_RINGOFFHOOK(2) on channel 1 (index 0)
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:3043
> __analog_handle_event: Ring
> detected
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2441 __analog_ss_thread:
> CID got
> string '16'
> [Sep 14 08:21:14] WARNING[11186]: callerid.c:243 callerid_get_dtmf:
> Couldn't
> detect start-character. CID parsing might be unreliable
> [Sep 14 08:21:14] DEBUG[11186]: sig_analog.c:2443 __analog_ss_thread:
> CID is
> '16', flags 0
> [Sep 14 08:21:14] DEBUG[9315]: devicestate.c:340 _ast_device_state:
> No provider
> found, checking channel drivers for DAHDI - 1
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:3239 ast_str_retrieve_variable:
> Result of
> 'EXTEN' is 's'
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper:
> Launching 'NoOp'
> [Sep 14 08:21:14] DEBUG[9315]: devicestate.c:458 do_state_change:
> Changing state
> for DAHDI/1 - state 2 (In use)
> [Sep 14 08:21:14] DEBUG[9315]: devicestate.c:438 devstate_event:
> device 'DAHDI/1'
> state '2'
>     -- Executing [s at incoming:1] NoOp("DAHDI/1-1",
"Incoming s") in
>     new stack
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:4058
> pbx_substitute_variables_helper_full:
> Function result is '16'
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper:
> Launching
> 'Verbose'
>     -- Executing [s at incoming:2] Verbose("DAHDI/1-1", "CID
16") in new
>     stack
> CID 16
> [Sep 14 08:21:14] DEBUG[9350]: app_queue.c:1487 handle_statechange:
> Device
> 'DAHDI/1' changed to state '2' (In use) but we don't
care because
> they're not a
> member of any queue.
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper:
> Launching 'Set'
>     -- Executing [s at incoming:3] Set("DAHDI/1-1",
"SPYGROUP=queue-01")
>     in new
> stack
> [Sep 14 08:21:14] DEBUG[11186]: pbx.c:4230 pbx_extension_helper:
> Launching
> 'Answer'
You appear to be suffering form
https://issues.asterisk.org/jira/browse/ASTERISK-19610

It is fixed in the just released v1.8.17.0-rc1.

Richard

Reasonably Related Threads

Search for more possibly parallel threads

asterisk users - Sep 2012 - Digium AEX410, MTNL Mumbai Caller-ID problems

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

[asterisk-users] Digium AEX410, MTNL Mumbai Caller-ID problems

Reasonably Related Threads