No audio on T1 calls


#1

I am having an issue with a T1 line. I see the calls coming into the system, but I don’t hear any audio. I set it to put a person on hold forver (just to play moh) and its not working either. In the logs I see the calls, but no audio
Any suggestions?


#2

Is the PBX local to the phones?


#3

what hardware does the T1 terminate on?


#4

Digium t1 Card, Ill get the exact model shortly.
The pbx is local, but I even tested sending to an IVR and I dont hear any audio


#5

from Asterisk

pri set debug on span 1

lots of stuff there, so watch the log file as a call is handled , all “ins” should have a corresponding “out”

You should see the PRI conversation, if the call is well negotiated, chan_dahdi then answering the call and bridging it with another endpoint, be that MOH (local) or any other endpoint.


#6

They are Digium - WCTE23X
The strange thing is that when I do service Dahdi Status, it is showing up as unkown even though I have it configured in the module.
It used to show a PRI now nothing.
I have it configured as:
Framing: ESF/B8ZS
Signalling PRI-CPE
Nation ISDN2
Context From-trunk


#7

Stop asterisk, then try stopping and starting dahdi and look at the status

service asterisk stop (fwconsole stop)

service dahdi stop
service dahdi start
service dahdi status


#8

I am getting the below. As a quick experiment I tried switched it to FXS and then the status shows that instead of unknown
Thank you

Span 1: WCTE2/0/1 “WCTE23X (PCI) Card 0 Span 1” (MASTER) ESF/B8ZS ClockSource

1 unknown Clear
2 unknown Clear
3 unknown Clear
4 unknown Clear
5 unknown Clear
6 unknown Clear
7 unknown Clear


#9

Is your T1 really carrying a PRI or is it just a good old 24 channel RBS? Because a PRI can’t do FXS and if a RBS then likely you should be using e&m


#10

Its a verizon PRI. I had just toggled to FXS to just see if any changes I am making are actually being reflected in the status.
Thank you


#11

For PRI’s to work on top of dahdi you need libpri compiled and working.

Kind of hard to do message by message, perhaps

https://wiki.freepbx.org/pages/viewpage.action?pageId=1048598

and choose your flavor and do the libpri/dahdi bit. . .


#12

Is there a way for me to test to see if it currently is compiled? I have asterisk 13 installed (new install) should I try 16?


#13

If its dahdi/libpri properly compiled against your running kernel then it will automatically load and

pri set debug

will spring into life.


#14

When I run pri set debug on span 1, it does say that it is starting debuging


#15

And when a call is initiated?

What about

service dahdi status


#16

At this stage if there is paid support, I would use it as the system has been down for a while already.

Thank you
[root@freepbx ~]# service dahdi status

Span 1: WCTE2/0/1 “WCTE23X (PCI) Card 0 Span 1” ESF/B8ZS ClockSource

1 unknown Clear (In use) (EC: OSLEC - INACTIVE)
2 unknown Clear (In use) (EC: OSLEC - INACTIVE)
3 unknown Clear (In use) (EC: OSLEC - INACTIVE)
4 unknown Clear (In use) (EC: OSLEC - INACTIVE)
5 unknown Clear (In use) (EC: OSLEC - INACTIVE)
6 unknown Clear (In use) (EC: OSLEC - INACTIVE)
7 unknown Clear (In use) (EC: OSLEC - INACTIVE)
8 unknown Clear (In use) (EC: OSLEC - INACTIVE)
9 unknown Clear (In use) (EC: OSLEC - INACTIVE)
10 unknown Clear (In use) (EC: OSLEC - INACTIVE)
11 unknown Clear (In use) (EC: OSLEC - INACTIVE)
12 unknown Clear (In use) (EC: OSLEC - INACTIVE)
13 unknown Clear (In use) (EC: OSLEC - INACTIVE)
14 unknown Clear (In use) (EC: OSLEC - INACTIVE)
15 unknown Clear (In use) (EC: OSLEC - INACTIVE)
16 unknown Clear (In use) (EC: OSLEC - INACTIVE)
17 unknown Clear (In use) (EC: OSLEC - INACTIVE)
18 unknown Clear (In use) (EC: OSLEC - INACTIVE)
19 unknown Clear (In use) (EC: OSLEC - INACTIVE)
20 unknown Clear (In use) (EC: OSLEC - INACTIVE)
21 unknown Clear (In use) (EC: OSLEC - INACTIVE)
22 unknown Clear (In use) (EC: OSLEC - INACTIVE)
23 unknown Clear (In use) (EC: OSLEC - INACTIVE)
24 unknown HDLCFCS (In use)


#17

Go for the paid solution.there is a link at the top of this page under “support”


(system) closed #18

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.