Very frustrating issue, even more so considering my tech-ID has been terminated. Switched from t1 to PRI. Calls inbound are OK (may be dropping randomly) but if not all, most outbound calls get dead air. I had them call me, the call came through but once answered just silence on the line. Assigned priority clocking to that blade did a save and back up, even reset the blade but still no luck.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SV8300 PRI Dead Air
- Thread starter CallMeLB
- Start date
OzzieGeorge
Programmer
Don't have much experience with the 8300 but down here (Oz) we switched from Australian ISDN to ETSI and one of the symptoms we foud of the wrong type being set was the type of conditions you are describing. Off the top of my head (don't hold me to it as I don't have a manual to hand) Cmd AA
belevedere
Instructor
Look at There is a PRI cheat sheet there. Follow it step by step. I think you may have missed the CIC code assignemnt. CMD 3007.
- Thread starter
- #4
In command AA I have data mode set to "based on AT&T specs" instead of none and ISDN protocol set to NI-2 which it should be.
I did find and use the cheat sheet. All of my channels have a CIC number assigned. Channels 1-24 are trunks d001-d024 and have CIC codes assigned 000-022 for channels 1-23.
After making changes I did a back up, save and disconnect, even reset the board through PCPro, still no change.
I did find and use the cheat sheet. All of my channels have a CIC number assigned. Channels 1-24 are trunks d001-d024 and have CIC codes assigned 000-022 for channels 1-23.
After making changes I did a back up, save and disconnect, even reset the board through PCPro, still no change.
belevedere
Instructor
Unfortunately you are at the point where you need a PRI tester to determine where the problem is. If you switched and reprogrammed from an existing T-1 and used the same trunk route then I would suggest you delete it and set it up again using previously unused trunk routes higher than route 10. Those routes have no defaults to get in the way. After deleting reset the blade. After reprogramming, reset the blade. If it still has issues, then you might have to get hold of a PRI tester. Or, at lest get telco to come in and test from the smart jack to their CO.
- Status
Similar threads
