Digium AEX410, MTNL Mumbai Caller-ID Problems

Home » Asterisk Users » Digium AEX410, MTNL Mumbai Caller-ID Problems
Asterisk Users 8 Comments

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_size0, hits_required!
[Sep 14 08:21:11] DEBUG[9337]: dsp.c:471 ast_tone_detect_init: Setup tone 2100
Hz, 2600 ms, block_size0, hits_required6
[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@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@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@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

8 thoughts on - Digium AEX410, MTNL Mumbai Caller-ID Problems

  • [snip]

    Your DAHDI and Asterisk versions are old so for starters I would update everything to the latest releases. See asterisk.org.

    Regards, Patrick

  • I could compile the latest from source for the sake of testing, but will eventually have to move back to a packaged Asterisk for production.
    Since the Digium Debian Asterisk packages don’t have a maintainer any more, that means production will eventually return back to 1.8.13.

    So if there’s a good chance that the latest Asterisk and Dahdi packages will give better results in testing or might actually solve the problem, I’ll be glad to compile from source. If not, then perhaps it’s not worth polluting a production box with locally-compiled packages.

    Regards,

    — Raj

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

  • Try adding a Wait(2) between your NoOp and your Verbose lines. I don’t know about your telco, but sometimes the CID is not sent with the first ring, and you have to add a Wait(2) to grab it.

    You may even want to call your upper level support at your telco and ask them how and when they send your callerid information…

  • Operator sends callerId after 1st small ring (actually this is not audible since its very small duration ring) post which all the data flows.

    However, sometimes due to line distrubance this first small ring is missed.

    Regards, Mitul Limbani, Chief Architech & Founder, Enterux Solutions Pvt. Ltd.
    110 Reena Complex, Opp. Nathani Steel, Vidyavihar (W), Mumbai – 400 086. India http://www.enterux.com/
    http://www.entvoice.com/
    email: mitul@enterux.in DID: +91-22-71967121
    Cell: +91-9820332422

  • Are you sure caller ID in India is not done as it is in the UK, with a reversal of the line polarity before the first ring and the ident sent after the reversal?

  • Outstanding! Just tried with 1.8.17.0-rc1 and the old Dahdi (2.5.0.1)
    and it delivered at least two CIDs just fine. Many thanks.

    Now to sort out the Asterisk packaged for Debian issue. Worst case, will package it myself 🙁

    Regards,

    — Raj