Ok something interesting - when I change the /etc/zaptel.conf to e&m and the signaling to em I get this in my zttool:
aaaaaaa Digium Wildcard TE110P T1/E1 Card 0 aaaaaaaaaaaaa
a a
a a
a Current Alarms: Yellow Alarm a
a Sync Source: Internally clocked a
a IRQ Misses: 0 a
a Bipolar Viol: 0 a
a Tx/Rx Levels:0/ 0 a
a Total/Conf/Act: 24/ 24/ 23 a
a 111111111122222 aaaaaaaa a
a 123456789012345678901234 a Back a a
a TxA 00000000000000000000000- aaaaaaaa a
a TxB 00000000000000000000000- a
a TxC 00000000000000000000000- a
a TxD 00000000000000000000000- a
a aaaaaaaa a
a RxA 11111111111111111111111- a Loop a a
a RxB 11111111111111111111111- aaaaaaaa a
a RxC 11111111111111111111111- a
a RxD 11111111111111111111111- a
a a
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Notice tx - all 0s and recieve all 1s - there has never been anything in those spots before:
But here is what my old zapata.conf was:
[channels]
context = incomming
switchtype = dms100
overlapdial = yes
usecallerid = yes
echocancel = yes
echocancelwhenbridged = yes
;add the is option if you are problems with DTMF detection
relaxdtmf = yes
rxgain = 0.0
txgain = 0.0
signalling = pri_cpe
group = 1
channel => 1-14
well we should be 14b+1d - so I made the zaptel.conf 1-14 dchan 15
I am restarting the system - to see what happens -
here is the results
Jul 25 07:06:25 ERROR[4819] chan_zap.c: Unable to open D-channel 24 (No such device or address)
Jul 25 07:06:25 ERROR[4819] chan_zap.c: Unable to start D-channel on span 1
Jul 25 07:06:25 WARNING[4819] loader.c: chan_zap.so: load_module failed, returning -1
Jul 25 07:06:25 WARNING[4819] loader.c: Loading module chan_zap.so failed!
I have read that even though we are only using 14b channels we still need all 23 listed in zaptel.conf - and then we only use 1-14 in the zapata.conf
should I get SBC on the phone agian and see if anythings changed?
The biggest thing that confuses me is that they kept telling me the protocol is National 2 what the heck is that - I can not find anyplace to make that change - its on the ordernumber i posted above (National / FAS)
your configs look right - what is the problem? can you not make calls?
if your ztcfg -vvv returns no errors, and asterisk starts cleanly, you SHOULD be able to make and receive calls…as far as i can tell, you are good to go at this point.
you could also check zttool if you’d like, but i’d try placing a call and seeing what happens.
ok…i’m not sure if SBC would be set up similarly across the country, but here in Overland Park, our PRI is using switchtype=national and signalling=pri_cpe in zapata.conf
EDIT: protocol=NI2 is probably the signalling setting, and both pri_cpe and pri_net support the following, according to digium’s docs:
Voice Modes
PRI CPE & PRI NET
* NI1
* NI2
* EuroISDN
* 4ESS (AT&T)
* 5ESS (Lucent)
* DMS100
from the looks of your ztcfg, your zaptel.conf is good to go.
are you currently running switchtype=national? if not, set it - it’s pretty much the only supported switchtype.
are you running signalling=pri_cpe? if not, please try that. make sure you restart asterisk, the just try to make a call - i don’t care what SBC says, just try to make a call.
if signalling is pri_cpe and you can’t call out, you MIGHT try setting it to pri_net.
there aren’t very many options for PRI, so one of the two above signalling types SHOULD be right…
switchtype: Sets the type of PRI switch being used. Default: national. Acceptable values are:
national: National ISDN type2 (common in the US)
ni1: National ISDN type 1
dms100: Nortel DMS100
4ess: AT&T 4ESS
5ess: Lucent 5ESS
euroisdn: EuroISDN
qsig: Minimalistic protocol to build a “network” with two or more PBX of different vendors!
Have you tried making a loopback plug and see if the card will green up?
[quote=“rusty”]switchtype: Sets the type of PRI switch being used. Default: national. Acceptable values are:
national: National ISDN type2 (common in the US)
ni1: National ISDN type 1
dms100: Nortel DMS100
4ess: AT&T 4ESS
5ess: Lucent 5ESS
euroisdn: EuroISDN
qsig: Minimalistic protocol to build a “network” with two or more PBX of different vendors!
Have you tried making a loopback plug and see if the card will green up?[/quote]
rusty brought up a good point - do you have a loopback cable you could plug in to test the card with?
also, when you are making these changes, are you completely killing asterisk and starting it back up? you don’t need to reboot the machine, just make sure the asterisk process has been restarted…
should be able to find some diagrams on google but basically you want to tye pins 1 and 4 together and pin 2 nd 5 together
Im not for sure been a whole since I tried but I believe the card should green up without asterisk running just do the modprobe and ztcfg after changes and I believe it goes green before starting asterisk