If you set it as follows it will use the CPND of key 4 which is your primary DN for the set.
key 5 scr xxxx D
D in the CLID table section will search up the keys from 0 until it finds a key which is associated with a CLID table.
Yes, I've been in LD 73 and checked the clocking. We have clocking setup and it was locked to the correct slot. All our PRI's use external clocking so that was checked as well early on during the troubleshooting and was ruled out.
After a lot of troubleshooting and borrowing an ISDN/PRI tester we identified the problem as a hardware issue in our switch. It was one of the following: bad msdl, bad slot on the PRI gateway, or bad port on the back plane. We tested the backplane fine. We permormed after hours maintenance on...
After a lot of troubleshooting and borrowing an ISDN/PRI tester we identified the problem as a hardware issue in our switch. It was one of the following: bad msdl, bad slot on the PRI gateway, or bad port on the back plane. We tested the backplane fine. We permormed after hours maintenance on...
This is not a TMDI card. It is a PRI card residing on a daughter board on the MSDL port 6.
We disconnect the smartjack between the PBX and the T1 (from the lcoal carrier) and we do not get Release Wrong Mode. We get Rls No Response.
I never got the "Release wrong mode" indication. Can you explain the process for doing the loop back that you are referring to? The above loopback test of the MSDL is the only one that I am aware of.
The first part of this is with a loop back plug on the back of the MSDL
DCH000
.stat dch 28
DCH010
.
.
DCH009
stat dch 28
DCH 028 : DSBL RST AUTO
DES : FTS2001
.enl dch 28
.stat dch 28
DCH 028 : DSBL RST AUTO
DES : FTS2001
.stat dch 28...
This is an existing circuit that has been working error free for awhile. We have performed all available hardware tests with no issues noted. I'll double check the local loopback results as that was done last week.
As stated we have a PRI that is down. All hardware on both sides, our switch and far end carrier switch, tests fine. The local provider and the carrier have tested the equipment in between and everything is clean and programmed correctly as ESF/B8ZS the entire way through.
Our PRI span comes up...
We have figured out what the problem is. We have a voice protection system (VPS) that ties into the two affected trunks that is controlled by an outside agency. It appears that either the device has gone bad or changes were made to the configuaration that was messing with the fax calls...
GHTROUT - thanks for the reply. I had already seen that suggestion in other threads and made that change on the 20th. Did several tests without any success. I changed it back to VOD as that is what it has been set to for several years.
Any other ideas?
Here is another update on this issues:
We had a tech come out from the local vendor. He tested some stuff and is pretty sure that it is something internal to our switch. Our long distance and local trunks are on the same shelf and we can't fax through either of them. Our autovon trunk is on a...
Another question - where do I look to see what codec is being used? I've seen references to OTM, but ours crapped out a while ago and the boss decided not to put the time or money into fixing it as we are moving to a new switch soon.
How would I look up the codec being used by CLI and change...
Bumping this back to the top as we are still trying to find a solution for the problem.
I've spent all morning testing different things out. I've also been studying the RDB's for our DSN route and our IAO local route. Faxes work on DSN but not local/long distance.
IN/OUT Local is set as...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.