Lance Grover
2005-Jul-06 13:53 UTC
[Asterisk-Users] NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1
I am getting: NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1 on my asterisk box and it seems to be causing a poping sound in the phones, I am wondering if anyone can shed some light on this. I have scanned the archives and get possibilities ranging form motherboards, to pri, to loaded module problems. Can someone tell me the best way to start tracking this down? -- Thanks, Lance Grover
Lance Grover
2005-Jul-07 12:11 UTC
[Asterisk-Users] NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1
Does anyone have comment on this? I am getting: NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1 on my asterisk box and it seems to be causing a poping sound in the phones, I am wondering if anyone can shed some light on this. I have scanned the archives and get possibilities ranging form motherboards, to pri, to loaded module problems. Can someone tell me the best way to start tracking this down? -- Thanks, Lance Grover
Lance Grover
2005-Sep-29 22:30 UTC
[Asterisk-Users] Re: NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1
On 7/6/05, Lance Grover <lance.grover@gmail.com> wrote:> > I am getting: > NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on > Primary D-channel of span 1 > > on my asterisk box and it seems to be causing a poping sound in the > phones, I am wondering if anyone can shed some light on this. I have > scanned the archives and get possibilities ranging form motherboards, > to pri, to loaded module problems. Can someone tell me the best way > to start tracking this down?Well I finally got this working properly so I just wanted to thank all those that sent me suggestions. It seems that this error can come because of to many modules, or IRQ issues, or whatever but for me it boiled down to the fact that in my /etc/zaptel.conf I was not using my PRI as the primary time source, I had it as the secondary and I only had one PRI attached. I hate it when it is something little and easy to fix, especially when it is your fault. After changing the config file so that it used the PRI as the primary time source the error went away and I have not seen it since, it is nice. Just for those that don't know what I am talking about this is what the offending line said in my zaptel.conf file: span=1,2,0,esf,b8zs This is what I changed it to so that now it works: span=1,1,0,esf,b8zs it was just that easy. -- Thanks, Lance Grover -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050930/03ed9301/attachment.htm
Seemingly Similar Threads
- chan_zap.c:8050 pri_dchannel: Ring requested on unconfigured channel 255/255 span 2
- chan_zap.c:8534 pri_dchannel: PRI Error
- Getting: Can't fix up channel from 5 to 7 because 7 is already in use, and pri_dchannel: Answer requested on channel 0/7 not in use on span 1
- PRI got event: HDLC Abort (6) on Primary D-channel of span 1
- B410P: DAHDI BRI PTMP HDLC Abort (6) on Primary D-channel of span 1 (TEI Errors)