Re: (ASCEND) MAX 4002 won't link to PRI

[robert_kim@hotmail.com]

Actually, PRI->T1 is not the hash code option for enabling D-channel
signalling.  That's a Max feature that allows the Max take in a PRI line
in one Wan port (say Wan 1) and reroute channels from the PRI out
another WAN port (say Wan 4) as a T1 (and also in the opposite
direction).  Usually the T1 line is then plugged into a PBX.

If you check the 00-100 screen again, you should check to see if "ISDN
Sig Installed" is set (which I believe it should already be since you
were able to configure your line with "Sig Mode=ISDN").  This is the
option to give you d-channel signalling which allows you to have a PRI
in the Max.  Without it, you can only do inband signalling (plain ol
T1).

If it still fluctuates between RA (red alarm), YA (yellow alarm) and IS
(all one's), then it could be either a cable problem or the telco really
needs to check the physical layer between the demarc and their CO.
Assuming that the cable run from the Max to the demarc is not that long
(say no longer then 10-50 feet), try a different CAT-5 cable.  You can
also try plugging the PRI into another Wan port of the Max.
Otherwise, it's most likely a telco problem.



Well, you're right. I checked the screen (00-100) under the software
version and it says PRI <-> T1 Not Inst.  The 10-100 screen continues
to vascillate between red alarm, yellow alarm and 1S. I have power
cycled
the MAX since manually entering the Hash. What would the next logical
step be?
I have the MAX T-1 WAN port hooked to the extended demarc's RJ-48 with a

known working straight through CAT-5.

At 06:01 PM 4/13/2000 -0700, you wrote:
>I assume the Max took the hash codes fine since you were able to
>configure "Sig Mode=ISDN" and not have it complain that ISDN was not
>available, but you can check to verify this by tabbing over to the "Sys

>Option" window (the same small window that shows your software version)

>and using the down arrow to check if "ISDN Sig Installed".  If so, then

>you should be able to take a PRI and have it come up properly.
>
>What you want to check is the top window (00-100 assuming you have the
>line plugged into Wan 1) and see what the line status is.  If you see
>L1/RA, then you are in "Red Alarm" and your Max doesn't see anything
>coming in.  Check your cabling or try and flip the "framing mode" to
>D4.  If you see something like "L1/DF", then that's D-channel failure.
>This means that telco should see framing at this point (and so should
>you, else you won't be in this state), but no valid D-channel has been
>seen by the Max (at this point, you have to have telco turn up the
>d-channel).  If you see "L1/YA", then the most likely cause is telco
>can't see you, but you can see them (you're actually seeing their red
>alarm).  Either check your cabling or have telco check their cabling
>upstream from you.
>
>This might help you determine what the problem is.
>
>
>
>RE: Connecting a 4002 to a PRI
>
>I've configured roughly 200 Ascend Pipeline
>ISDN routers over the last three years for our
>remote offices, but this is my first experience with a MAX.
>I'm trying to get it to link up
>to a PRI. The telco (USWest) can see the integrated
>CSU, but the framing is bad.
>In order for the 4002 to link to a PRI, you have to
>load the hash code provided by Ascend.
>
>type "esc[esc="
>get the ">" prompt
>load the hash file using the "send Ascii" option in
>CRT, procomm plus or some other com program over serial.
>
>Once this is done, the T-1 WAN port is supposed to be ready to
>recognize ISDN (PRI) signalling.
>
>I noticed the MAX couldn't handle the send ASCII option, as is
evidenced
>by
>the error outputs below. It looks like it couldn't keep up with the
>speed
>of the ASCII send.
>So, I entered all the commands manually and it accepted them.
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>revision 0 1 10 9261303 IdHeMsE~@AT}Qb
>urevision command: command complete.
>p > date 7 1023 4 lVmWhA`MeSqOtP
>uupdate command: command complete.
>p > date 8 65521 0 TAU@P6X:]dI8LG
>pupdate command: command complete.
>t >  35 1 y|x}kugp9deaz
>ERROR:  Command not found
>u > pdate 14
>update command: invalid arg 2!
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>Again, when I entered all the commands manually it accepted them.
>Also, the serial # for the HASH does match the serial # for the router,

>as is required.
>
>The PRI is ESF, B8ZS.
>I put these parameters in the menu:
>
>10-000 Net/T1
>10-100 Line Config
>10-101
>Line 1
>Sig Mode=ISDN
>Switch Type AT&T
>Framing Mode=ESF
>Encoding=B8ZS
>Buildout=7.5db
>Clock Source=yes
>
>All of which was confirmed as matching on USWest's end, but they still
>show
>the framing
>as bad.
>
>Any advise would be appreciated.
>Thanks
>
>++ Ascend Users Mailing List ++
>To unsubscribe:        send unsubscribe to
ascend-users-request@bungi.com
>To get FAQ'd:  <http://www.nealis.net/ascend/faq>

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

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