Darryl Dunkin wrote: > wanpipemon is the way to do it as far as I know. > > For starters, what do your zaptel/zapata configs look like? > > I would first verify that your D-channel is set properly, you can view > that in the console as follows: > asterisk> pri show span 1/0 > Primary D-channel: 24 > Status: Provisioned, Up, Active > Switchtype: National ISDN > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Erik > Anderson > Sent: Monday, August 06, 2007 11:09 > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: [asterisk-users] low-level dump for PRI dchan debugging > > I've been going back and forth with my telco for several days, trying > different configurations to get a new PRI to come up. The bchannels > are all up and the T1 is not in alarm status. The dchannel refuses to > come up however. We've tried ni2, qsig, and now dms100 for the > switchtype. The telco tech I've been working with says that he's been > sending "reset all channels" signals to my system, to which he's > getting an "establish remote" response from my asterisk box. I've > been running a packet dump (wanpipemon -i w1g1 -c trd) of my d-channel > this whole time and have yet to see a single incoming packet. I > believe I *should* be seeing an incoming packet when he sends the > reset, correct? Is there any way to do a completely raw dump of the > d-channel? > > Here are my specs: > linux-2.6.16 > libpri-1.3.5 > zaptel-1.2.19 > asterisk-1.2.21.1 > > The PRI interface is a Sangoma A102...it's running the latest firmware > and I'm running wanpipe-2.3.4-12 for the sangoma drivers. > > Any ideas? > > You should never be the signaling source, you are always a slave to the provider, go with pri_cpe and see if things go better.
Anthony _______________________________________________ --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