Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Bronze

PRI-D channel Assitance

Guys,

first time configuring PRI for voice and am having a little issue with the telco. they are asking me to turn up my D channel but have no idea of how this should be done.

My basic config is as follows

controller T1 0/0/0

framing esf

linecode b8zs

pri-group timeslots 1-24

interface Serial0/0/0:23

no ip address

encapsulation ppp

isdn switch-type primary-dms100

isdn incoming-voice voice

no cdp enable

my voice port is created and im thinking that should be all. show isdn status shows the following

Global ISDN Switchtype = primary-dms100

ISDN Serial0/0/0:23 interface

dsl 0, interface ISDN Switchtype = primary-dms100

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = AWAITING_ESTABLISHMENT

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x807FFFFF

Number of L2 Discards = 0, L2 Session ID = 46

Under layer 2 it sometimes shows the state as TEI_ASSIGNED then reverts to awaiting establishment.

finally, a show isdn service shows

PRI Channel Statistics:

ISDN Se0/0/0:23, Channel [1-24]

Configured Isdn Interface (dsl) 0

Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart 5=Maint_Pend)

Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4

State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3

if i show the serial interface i get the line protocol as being down

Serial0/0/0:23 is up, line protocol is down

any assistance would be greatly appreicated.

  • IP Telephony
25 REPLIES
Hall of Fame Super Gold

Re: PRI-D channel Assitance

Hi,

send output of "show controllers T1". Your circuit might be down.

Bronze

Re: PRI-D channel Assitance

here it is, also, can you explain what they meant by turning up my D channel? im assuming the only thing i can do is issue a shut not shut on the Serial 0/0/0:23. interface.. also, ater the initial post, i saw the serial come up and the line protocl showed up (spoofed)

T1 0/0/0 is up.

Applique type is Channelized T1

Cablelength is long gain36 0db

Description: NOTE CHANGED TO CCS

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: 20060707, 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 (128 seconds elapsed):

0 Line Code Violations, 0 Path Code Violations

8 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

8 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 24 hours)

2 Line Code Violations, 6 Path Code Violations,

3498 Slip Secs, 0 Fr Loss Secs, 1 Line Err Secs, 1 Degraded Mins,

3498 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 215 Unavail Secs

Hall of Fame Super Gold

Re: PRI-D channel Assitance

They simply mean, start your device.

You circuit appears fine beside the slips. Please configure "network-clock-participate wic 0" and network-clock-select t1 0/0/0 1".

After that if still trouble please sedn output of "debug isdn q921" when going from shut to no shut under controller T1.

Bronze

Re: PRI-D channel Assitance

did the network clock and select commands and shut down the controller and then brought back up. im seeing awaiting establishment. one last question. this should read multiframe established when its up correct?

043151: Sep 5 08:37:28.095 Caracas: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to up

043152: Sep 5 08:37:28.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043153: Sep 5 08:37:28.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043154: Sep 5 08:37:29.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043155: Sep 5 08:37:30.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043156: Sep 5 08:37:30.095 Caracas: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to up

043157: Sep 5 08:37:31.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043158: Sep 5 08:37:37.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043159: Sep 5 08:37:37.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043160: Sep 5 08:37:38.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043161: Sep 5 08:37:38.355 Caracas: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 11 to priority 1

043162: Sep 5 08:37:39.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043163: Sep 5 08:37:40.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043164: Sep 5 08:37:46.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043165: Sep 5 08:37:46.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043166: Sep 5 08:37:47.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043167: Sep 5 08:37:48.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043168: Sep 5 08:37:49.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043169: Sep 5 08:37:55.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043170: Sep 5 08:37:55.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043171: Sep 5 08:37:56.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043172: Sep 5 08:37:57.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043173: Sep 5 08:37:58.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043174: Sep 5 08:38:04.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043175: Sep 5 08:38:04.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043176: Sep 5 08:38:05.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043177: Sep 5 08:38:06.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043178: Sep 5 08:38:07.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043179: Sep 5 08:38:13.095 Caracas: ISDN Se0/0/0:23 Q921: L2_EstablishDataLink: sending SABME

043180: Sep 5 08:38:13.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043181: Sep 5 08:38:14.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043182: Sep 5 08:38:15.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

043183: Sep 5 08:38:16.095 Caracas: ISDN Se0/0/0:23 Q921: User TX -> SABMEp sapi=0 tei=0

Hall of Fame Super Gold

Re: PRI-D channel Assitance

Hi,

you are not receiving anything. Check with telco thye have activated their side and have no alarms.

Unrelated question: Is your router really in Caracas? I was told repeatedly that ISDN is not available in Venezuela.

Bronze

Re: PRI-D channel Assitance

thanks, have a conference call with the provider so i just wanted to be as prepared as possible. also, is it supposed to say Multiframe established?.

finally, hehe, no its not in caracas, we are in Trinidad near to venezuela and the time zone we normally set is Caracas La Paz. yeah i dont think they have PRI as yet. actually, our provider is now offering PRI (This customer is one of the first to have it) hence my basic questions since we always normally configure CAS.

Unrelated question :) do you do work on this side of the world? (As youre asking about Venezuela)

Hall of Fame Super Gold

Re: PRI-D channel Assitance

I see. Yes the normal status of a PRI is multiframe established.

And yes I "do have" routers in Venezuela as well in Europe, Haiti, Guatemala, Santo Domingo, Argentina soon and others.

Never been to Trinidad but I think I should :)

Bronze

Re: PRI-D channel Assitance

cool, shoot me an email if you wouldnt mind. i think you would like what we are trying to do.

Bronze

Re: PRI-D channel Assitance

- provider says all the channels are up and idle except the D-Channel which is in a locked state. i verified the configurations again but they say that they are not receiving any signalling information from my router. is there anything else i can recommend doing?

just to get something clear as well. the serial 0/0/0:23 is the D channel correct? also do i need to configure nfas_d ?

9298
Views
4
Helpful
25
Replies