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

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

On Friday 14 Sep 2012, Richard Mudgett wrote:
> > 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):

> 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.

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
-- 
Raj Mathur  || r...@kandalaya.org   || GPG:
http://otheronepercent.blogspot.com || http://kandalaya.org || CC68
It is the mind that moves   || http://schizoid.in   || D17F

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

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

On Friday 14 Sep 2012, Richard Mudgett wrote:
> > 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):

> 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.

Thanks, will test that on the weekend then.

Regards,

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

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

[A J Stiles]

On Friday 14 September 2012, Mitul Limbani wrote:
> 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.

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?

-- 
AJS

Answers come *after* questions.

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

[Richard Mudgett]

> 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

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

[Mitul Limbani]

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: mi...@enterux.in
DID: +91-22-71967121
Cell: +91-9820332422




On Fri, Sep 14, 2012 at 7:49 PM, Warren Selby  wrote:

> On Fri, Sep 14, 2012 at 9:02 AM, Raj Mathur (राज माथुर) <
> r...@linux-delhi.org> wrote:
>
>> 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.
>>
>>
> 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...
>
>
> --
> Thanks,
> --Warren Selby, dCAP
> http://www.SelbyTech.com 
>
>
> --
> _
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

[Warren Selby]

On Fri, Sep 14, 2012 at 9:02 AM, Raj Mathur (राज माथुर) <
r...@linux-delhi.org> wrote:

> 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.
>
>
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...


-- 
Thanks,
--Warren Selby, dCAP
http://www.SelbyTech.com 
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

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

On Friday 14 Sep 2012, Patrick Lists wrote:
> 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.

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  || r...@kandalaya.org   || GPG:
http://otheronepercent.blogspot.com || http://kandalaya.org || CC68
It is the mind that moves   || http://schizoid.in   || D17F

--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
   http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

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

[Patrick Lists]

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


--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
  http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users

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

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

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_

[asterisk-users] Digium AEX410

[Matt Watson]

Poking around the zaptel SVN earlier today i see support was added for an 
AEX410 card recently...

I'm going to go out on a limb and assume this is the PCI-Express version of the 
TDM410?

Any hints on a general availability date?

--
Matt

___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users