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

["Peter Copeland" <Tharen@i-t-c.com>]

USWest insists AT&T is the switch type to be used. Channels 1-23 are switched 
slot 0, Prt/Grp 0 and 24 is the D channel. We tested it again this morning
- it continues
to vascillate between red alarm, yellow alarm and 1S.


At 05:03 PM 4/13/2000 -0400, you wrote:
>My switch type is set for NTI with Ameritech; Buildout is 0. Are channels
>1-23 set to switched, slot 0, Prt/Grp 0 and channel 24 set for D-Channel?
>
>---------------------------------------------
>Stephen D. Goff
>Network Administrator
>NetWorld Online: An A1 Internet Company
>http://www.nwonline.net (419) 334-9042
>
>
>-----Original Message-----
>From: owner-ascend-users@max.bungi.com
>[mailto:owner-ascend-users@max.bungi.com]On Behalf Of Peter Copeland
>Sent: Thursday, April 13, 2000 1:45 PM
>To: ascend-users@max.bungi.com
>Subject: (ASCEND) MAX 4002 won't link to PRI
>
>
>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>