09-15-2008 06:46 AM - edited 03-15-2019 01:16 PM
Have Vwic-wmft-e1. Controller shows down/down with increasing line code violations. Have verified framing /coding/isdn switch type with vendor. Card has AL and CD lights on (yellow and green). shut /no shut does nothing. Site is in India, if that helps. Using no-crc4/hdb3. CM is 6.11
09-15-2008 07:03 AM
Hi,
This is what we have set-up for a E1 in the UK -
sh contr e1
E1 0/0/0 is up.
Applique type is Channelized E1 - balanced
Framing is CRC4, Line Code is HDB3, Clock Source is Line.
From the running-config
!
card type e1 0 0
!
isdn switch-type primary-net5
isdn voice-call-failure 0
!
voice-card 0
no dspfarm
!
controller E1 0/0/0
pri-group timeslots 1-31
!
interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
no cdp enable
!
Your ISDN switch-type will probably be different. If you have a sh run. show isdn stat, sh contr e1 - that would be handy.
James
09-15-2008 07:45 AM
Thanks for your response. Here are the requested files. What troubles me is that when I use a crossover, I get the CD light. Replaces it with a Cat5, CD light goes off, but either way, no status changes on controller
E1 0/0/0 is down.
Applique type is Channelized E1 - balanced
Receiver has loss of frame.
alarm-trigger is not set
Version info Firmware: 20060623, FPGA: 20, spm_count = 0
Framing is NO-CRC4, Line Code is HDB3, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
INDELNRT301#sho isdn stat
Global ISDN Switchtype = primary-net5
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply
ISDN Serial0/0/0:15 interface
dsl 0, interface ISDN Switchtype = primary-net5
L2 Protocol = Q.921 0x0000 L3 Protocol(s) = CCM MANAGER 0x0003
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x00000000
Number of L2 Discards = 0, L2 Session ID = 1
--More--
INDELNRT301#sho run
Building configuration...
Current configuration : 3484 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
!
network-clock-participate wic 0
network-clock-select 1 E1 0/0/0
!
!
ip cef
!
!
no ip domain lookup
!
isdn switch-type primary-net5
!
voice-card 0
dspfarm
dsp services dspfarm
!
!
!
!
!
!
!
!
!
!
!
controller E1 0/0/0
framing NO-CRC4
pri-group timeslots 1-31 service mgcp
!
controller E1 0/0/1
shutdown
framing NO-CRC4
Interface Serial0/0/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
!
Voice Port 0/0/0:15
!
ccm-manager fallback-mgcp
ccm-manager redundant-host 10.5.139.197
ccm-manager mgcp
ccm-manager music-on-hold
ccm-manager config server 10.5.139.196
ccm-manager config
!
mgcp
mgcp call-agent 10.5.139.196 2427 service-type mgcp version 0.1
mgcp dtmf-relay voip codec all mode out-of-band
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp ip qos dscp cs3 signaling
mgcp package-capability rtp-package
no mgcp package-capability res-package
mgcp package-capability sst-package
no mgcp package-capability fxr-package
mgcp package-capability pre-package
no mgcp timer receive-rtcp
mgcp sdp simple
mgcp rtp payload-type g726r16 static
mgcp bind control source-interface Loopback99
mgcp bind media source-interface Loopback99
!
mgcp profile default
!
!
line con 0
line aux 0
line vty 0 4
!
scheduler allocate 20000 1000
!
end
09-15-2008 07:08 AM
Check out this link:
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a00800f99bb.shtml#linecode
Excessive LCV are normally caused by either config or line issues. As James' mentions are you using the correct ISDN switch type. I've configured an E1 in India before and the config is the same as the UK.
09-15-2008 08:19 AM
Hi,
There may be a few commands that may need to be tweaked, nut l would contact your Telco as Layer 1 is showing as de-activated.
Global ISDN Switchtype = primary-net5
ISDN Serial0/0/0:15 interface
dsl 0, interface ISDN Switchtype = primary-net5
Layer 1 Status:
ACTIVE
09-15-2008 09:06 AM
If your E1 controller is in ?down/down" state, most likely you have a physical problem with the link. Confirm with your provider that they have all the same parameters as you configure in term of Framing and Linecode. In the lab, when you have wrong Framing/Linecoding, the controller will be down, but the moment I configure correct parameters, controller comes to up/up state even without "isdn switching" and PRI-DS0 configured.
12-19-2008 10:22 AM
In CUCM, if my provider has the following:
ISDN Switch Type - ETSI
ï¼Line Coding - hdb3
ï¼Framing - crc-4
I do not have these options on the MGCP for the gateway in CUCM. Only B8z3 or AMI.
How does this work in Taiwan then? I cant get my physical layer up
12-29-2008 06:56 AM
The {ISDN Switch Type - ETSI
ï¼Line Coding - hdb3
ï¼Framing - crc-4 ) is an E1 configuration.
Hi tcatlinins,
You may have a card type command set to T1.
Thats why you only see he B8zs which is a T1 config.
You may need to set the card type command
card type e1 slotno.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: