Sangoma A200 T1/PRI Card

From: Dave Brockman 
------------------------------------------------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anyone on list have recent experience with Sangoma A200 T1 cards and
PIAF-2, or recent experience with same hardware and have a solid
understanding of Asterisk (1.8) components (because I don't) that can
spare an hour tomorrow (lunch is my treat!)?  I've run into a bit of a
brick wall and am under a bit of a time-crunch to get this up and
running...

Outside of Asterisk, everything seems DAHDI-licious (dahdi

=============================================================== From: Aaron Welch ------------------------------------------------------ So are the channels not showing up at all? How are you getting D-Channel si= gnaling? The channels will not show up without a connection. -AW

=============================================================== From: Dave Brockman ------------------------------------------------------ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Outside of Asterisk, (dahdi

=============================================================== From: Joe Freeman ------------------------------------------------------ Can you do a pri debug? Sounds like signalling issues. If so they should become apparent with a high enough pri debug level. Alternatively, you can look at the pipe with wanpipemon, I think, with the Sangoma cards.

=============================================================== From: Dave Brockman ------------------------------------------------------ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I should also mention this PRI works with another PBX, and I am led to believe I am using the identical configuration in regards to # of channels/National 2/encoding/etc. I'm literally unplugging a live working PRI and plugging it into my pbx and card. (source is different hardware and software, unfortunately comparing the two hasn't helped much as of yet). Aside from the dahdi show xxx commands, is there another way inside of *CLI to "see" the hardware? Regards, dtb -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+QuhYACgkQABP1RO+tr2RitgCePdnXjsHdc7Vwh8ubuBrF7bvk ibEAoIxprPayJpSD6tcgNPrBs6LC7zU5 =kmfF -----END PGP SIGNATURE-----

=============================================================== From: Joe Freeman ------------------------------------------------------ the debug pri from the asterisk cli should show you d channel signalling. the wanpipemon output should show you everything happening on the circuit.

=============================================================== From: Dave Brockman ------------------------------------------------------ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for that... I found more info on the debug pri commands and have them bookmarked for tomorrow. Will search out wanpipemon now :) Regards, dtb -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Q1H8ACgkQABP1RO+tr2Sq1wCfV+QLCwYFeJmiUl5ufdabs13/ c9UAn0tgwz6Ia5G89gpzp5JSrUrwzt2d =36ih -----END PGP SIGNATURE-----

=============================================================== From: Dave Brockman ------------------------------------------------------ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Follow-Up: Due to other issues with latest PIAF2 (most importantly a bug in the md-raid subsystem that doesn't version correctly on the mirror), I went with a different distro, but did need to disable Wanpipe HW DCHAN option, that was part of the problem on PIAF, but there was something else wrong as well. /shrug This week has taught me why Cisco keeps TDM termination in their routers, I agree with their logic. Regards, dtb - -- "Some things in life can never be fully appreciated nor understood unless experienced firsthand. Some things in networking can never be fully understood by someone who neither builds commercial networking equipment nor runs an operational network." RFC 1925 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+TPW0ACgkQABP1RO+tr2QlWACffr57fTdVfcv56ONpk0oHwy9b F+wAoICJg1jck54dZUUL8bNXZxxLdzPL =2P7u -----END PGP SIGNATURE-----