(ASCEND) 5.0Ap36 on MAX1800 probs

[Todd Romero <toddr@user2.mnsinc.com>]

I upgrade the software in a max1800 to: 5.0Ap36 because I was lead to 
believe that Ascend had fixed a bri bug. Here's were it gets worse. 

We loaded some customer onto the 1800 and all was fine for about 12hrs. Then 
one og the D-channels reports an "X" which means it cant see the isdn line. 
I did a power-on reset, and nothin, I did a power-off reset and nothin. I 
took that line and switched ports, nothin. I took the line and tried it in a 
P50, and walla, the line itself is fine. (I also tried new rj45 ends on the 
cable)

What gives? has anyone else seen a prob like this. I thought maybe the port 
on the max was bad, but.. i tried it in different ports, etc. Additionally I 
added a new line and it detected it fine. 


ill guess ill try downgrading

anyone see anything similar to this?
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

Follow-Ups:

• Re: (ASCEND) 5.0Ap36 on MAX1800 probs
• From: Jason Nealis <nealis@babylon.erols.com>

---

• Prev by Date: (ASCEND) Problems with Pipeline 50 connecting to Max 2024
• Next by Date: Re: (ASCEND) K56 and X2
• Prev by thread: RE: (ASCEND) Fatal Error Index:2001
• Next by thread: Re: (ASCEND) 5.0Ap36 on MAX1800 probs
• Index(es):
  • Main
  • Thread