09-04-2007 04:27 PM - edited 03-14-2019 11:22 PM
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.
09-05-2007 01:56 AM
Hi,
send output of "show controllers T1". Your circuit might be down.
09-05-2007 03:44 AM
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
09-05-2007 03:48 AM
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.
09-05-2007 04:39 AM
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
09-05-2007 05:02 AM
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.
09-05-2007 05:10 AM
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)
09-05-2007 12:55 PM
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 :)
09-05-2007 05:35 PM
cool, shoot me an email if you wouldnt mind. i think you would like what we are trying to do.
09-06-2007 05:55 AM
- 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 ?
09-06-2007 06:09 AM
Your config is fine. But you are not receiving anything neither they do. Please recheck all layer 1, circuit, cabling to NTU, all these things. Ask here if you aren't sure about something.
Ask them if they seen any alarm at E1 level. Last resort, prepare a rj-45 loop in form of a female socket and connect it in place of the the router, this will definitely lift the burden of proof from you. The pinout is on the manual page for the card, however it's always the same.
My email is in my profile. Good luck!
09-06-2007 06:17 AM
Fixed an issue like this last week ... try changing the encapsulation on the D channel from PPP to HDLC, then reload the router. Use the command 'encapsulation hdlc ' under the D channel config.
At the moment, the telco is likely having trouble understanding the D channel messages when they are framed as PPP :-)
09-06-2007 09:49 AM
Hi, you know like I do that in fact encapsulation on an ISDN interface only changes the encapsulation for B-channels when used for data. Encapsulation on D-channel is only and always LAPD, that is the layer 2 of ISDN.
This said I can totally believe that restoring the encapsulation to default and a reboot is beneficial, also considering that ISR routers only recently gained data capability on the VWICx moduled.
09-06-2007 10:13 AM
well, i think ive tried everything. just off the phone after a marathon 3 hours with the provider with no success. they say their D channel is locked out and they turned on a trunk and got a D channel out of service. they are re-checking the cross connects but it doesnt look good.
09-06-2007 10:39 AM
Let them work and things will eventually work.
It is very, very hard to find a cisco router is culpable. (ok, sometime it is, but not to the point of locking a telco's interface).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide