[cisco-voip] Troubleshooting ISDN PRI alternating between TEI_ASSIGNED and AWAITING_ESTABLISHMENT

Fedorov, Konstantin kfedor at amt.ru
Tue Nov 21 12:18:40 EST 2006


Hi?

This L2 problem.

Call to provider and ask why L2 not established.
May be you must change protocol-emulate on d channel.



-----------------------
Sincerely Yours,
Konstantin Fedorov

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Robert
Kulagowski
Sent: Tuesday, November 21, 2006 7:45 PM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Troubleshooting ISDN PRI alternating between
TEI_ASSIGNED and AWAITING_ESTABLISHMENT

Jonathan Charles wrote:
> I would start by checking the t1 controller for errors, is it up, etc.

T1 0/2/0 is up.
   Applique type is Channelized T1
   Cablelength is long gain36 0db
   No alarms detected.
   alarm-trigger is not set
   Soaking time: 3, Clearance time: 10
   AIS State:Clear  LOS State:Clear  LOF State:Clear
   Version info Firmware: 20060711, FPGA: 13, spm_count = 0
   Framing is ESF, Line Code is B8ZS, Clock Source is Line.
   CRC Threshold is 320. Reported from firmware  is 320.
   Data in current interval (208 seconds elapsed):
      0 Line Code Violations, 0 Path Code Violations
      0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
      0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail
Secs
   Total Data (last 24 hours)
      0 Line Code Violations, 0 Path Code Violations,
      0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
      0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail
Secs

Currently configuring SIP, so no H.323 or MGCP.

deb isdn standard is showing essentially the same thing as I pasted in 
my first email.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip





More information about the cisco-voip mailing list