ISDN30 PRI E1. L2 State = TEI_ASSIGNED. United Kingdom.

[oscar cordero]

We are install a PRI in Gibraltar Country with the provider Gib Telecom.

The issue is in the Layer 2 ISDN. The provider had done twice the test ISD30, they connect
some equipment (they disconnect the cable connected to the router card E1 and connect they
equipment) in our side and call to mobile successfull.



////////////////////////////////////////////////


THE STATE JUMP FROM TEI_ASSIGNED TO AWAITING_ESTABLISHMENT

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:
        ACTIVE
    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:  0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 206
    Total Allocated ISDN CCBs = 0



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:
        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:  0xFFFF7FFF
    Number of L2 Discards = 0, L2 Session ID = 206
    Total Allocated ISDN CCBs = 0



///////////////////////////////////////////////

WE NOT SEE INCOMING DATA IN THE COUNTER "packets input"

Interface Serial0/0/0:15 is up, line protocol is up (spoofing)
  Hardware is DSX1
  MTU 1500 bytes, BW 64 Kbit/sec, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation HDLC, crc 16, loopback not set
  Keepalive set (10 sec)
  Last input never, output 00:00:04, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/1/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 48 kilobits/sec
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     5764 packets output, 17292 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 unknown protocol drops
     0 output buffer failures, 0 output buffers swapped out
     1 carrier transitions



/////////////////////////////////////////////


WE NOT SEE RX FOR A LONG TIME.

GW-1-AIR-GIBR-PR#debug isdn q921
*Dec 14 10:03:55.786: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
*Dec 14 10:03:55.786: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Dec 14 10:03:56.786: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Dec 14 10:03:57.786: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
*Dec 14 10:03:58.786: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0



//////////////////////////////////////////////

WE NOT SEE ANY ERROR IN THE CONTROLLER E1

GW-1-AIR-GIBR-PR#show controller e1
E1 0/0/0 is up.
  Applique type is Channelized E1 - balanced
  No alarms detected.
  alarm-trigger is not set
  Version info FPGA Rev: 08121917, FPGA Type: PRK4
  Framing is CRC4, Line Code is HDB3, Clock Source is Line.
  International Bit: 1, National Bits: 11111
  Data in current interval (567 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



//////////////////////////////////////////////

Our CUCM is configures with MGCP with this parameters:

Global ISDN Switch Type     = EURO
Switchback Timing = Gracefull

-----
Product =     Cisco MGCP E1 Port
Gateway =     GW-1-AIR-GIBR-PR
Device Protocol =      PRI de acceso digital
Registration =     Registered with Cisco Unified Communications Manager 10.0.16.11
IP Address =     10.0.16.14
Device is trusted Device is not trusted
End-Point Name =      S0/SU0/DS1-0@GW-1-AIR-GIBR-PR 
NetworkLocale = United Kingdom

-----
PRI Protocol Type = PRI EURO
Protocol Side = User
Channel Selection Order = Bottom UP
Channel IE Type = User Number When 1B
PCM Type = A-law

-----
Line Coding =     HDB3
Framing     = CRC4
Clock = EXTERNAL
EURO
HDB3


-----

Cisco Unified CM Administration

System version: 8.5.1.12900-7

-----

 

[acampbell]

Hi,

I see you are set to use CRC4 for framing.

Not sure what the correct setting for Gibroltar is.

Try making it NO CRC4 on both the router & CUCM.

Regards

Alex

[paolo bevilacqua]

CRC setting is fine, otherwise controller would not be error free.

And, CRC settings are on router only, not on CUCM.

[paolo bevilacqua]

When they did the testing using their equipment, you were present and have seen that personally ?

[oscar cordero]

Unfortunately I was not there, Im the enginneer and Im work remotely, but our techinicial level 1 (remote hand) was there.

in the CUCM there a re option for line codig and CRC when you configure MGCP.

[acampbell]

Oscar,

What is the config of your interface S0/0/0:15

Regards

Alex

[oscar cordero]

In my gateway I have:

!

network-clock-participate wic 0

network-clock-select 1 E1 0/0/0

!

isdn switch-type primary-net5

!

controller E1 0/0/0

pri-group timeslots 1-31 service mgcp

!

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

echo-cancel coverage 64

cptone GB

!        

ccm-manager redundant-host 10.0.16.10

ccm-manager mgcp

no ccm-manager fax protocol cisco

ccm-manager music-on-hold

ccm-manager config server 10.0.16.11 10.0.16.10

ccm-manager config

!

mgcp

mgcp call-agent 10.0.16.11 2427 service-type mgcp version 0.1

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

mgcp bind control source-interface GigabitEthernet0/1

mgcp bind media source-interface GigabitEthernet0/1

!

mgcp profile default

!

[acampbell]

Hi,

This all looks good.

There seem be a few issues and old bugs re this.

Can you try :-

!

no mgcp

!

int s0/0/0:15

shut

!

! wait 10 seconds

!

no shut

!

mgcp

!

See if this helps

Alex

[paolo bevilacqua]

Ask telco to come back onsite and repeat tests.

No packets received by router = circuit not active.

[oscar cordero]

We did the no mgcp and not help.

Im asking the Telco repeat the test.

Cisco Enginner also delete config of the MGCP and config with H323 but still not up the L2 ISDN (Q921). Cisco ENginner found that we not receive RX just TX.

debug isdn q921 and got:

ec 19 17:25:55.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:25:56.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:02.450: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 19 17:26:02.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:03.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:04.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:05.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:11.450: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 19 17:26:11.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Dec 19 17:26:12.450: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

NEW Config with H323 (With out MGCP):

network-clock-participate wic 0

network-clock-select 1 E1 0/0/0

!

isdn switch-type primary-net5

!

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

!

!

voice-port 0/0/0:15

!        

ccm-manager redundant-host 10.0.16.10

ccm-manager mgcp

no ccm-manager fax protocol cisco

ccm-manager music-on-hold

ccm-manager config server 10.0.16.11 10.0.16.10

ccm-manager config

!

mgcp

mgcp call-agent 10.0.16.11 2427 service-type mgcp version 0.1

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

mgcp bind control source-interface GigabitEthernet0/1

mgcp bind media source-interface GigabitEthernet0/1

!

mgcp profile default

!

[oscar cordero]

I change from “user” to “network” in MGCP and now for first time I have receive data from the switch isdn. what is mean BAD FRAME?. How can I solved?.

Dec 21 10:06:47.700: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:06:47.700: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:48.700: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:49.700: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:50.700: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:57.412: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:06:57.716: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:06:57.716: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:58.408: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:06:58.716: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:06:59.412: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:06:59.716: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:00.416: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:07:00.716: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:07.731: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:07:07.731: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:08.731: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:09.731: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:10.731: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:17.743: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:07:17.743: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:18.743: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:19.743: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:20.743: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:07:27.495: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to down (RAI detected)

Dec 21 10:07:27.671: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller E1 0/0/0

Dec 21 10:07:29.495: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to down

Dec 21 10:07:37.923: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller E1 0/0/0

Dec 21 10:07:37.923: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10

Dec 21 10:08:29.495: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up

Dec 21 10:08:29.523: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:08:29.523: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:30.523: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:31.495: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed state to up

Dec 21 10:08:31.523: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:32.523: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:39.535: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:08:39.535: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:39.923: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1

Dec 21 10:08:40.535: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:41.535: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:42.535: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:49.547: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:08:49.547: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:50.546: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:51.546: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:52.546: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:08:59.562: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

Dec 21 10:08:59.562: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:09:00.562: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:09:01.562: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:09:02.562: ISDN Se0/0/0:15 Q921: Net TX -> SABMEp sapi=0 tei=0

Dec 21 10:09:04.738: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:09:05.730: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:09:06.734: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:09:07.738: ISDN Se0/0/0:15 Q921: Net RX <- BAD FRAME(0x02017F)

Dec 21 10:09:09.574: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

[paolo bevilacqua · Accepted solution]

Bad frame means you are network and are receiving a network frame.

You should be user always and work with H.323, as MGCP is unreliable.

[oscar cordero]

We are working with new generation routers and PRI cards, for the router "2900 series" and card PRI "VWIC3". This newest equipment have not reported till now any BUG about compatibility with Switchs ISDN providers.

Today We upgrade the IOS from c2900-universalk9-mz.SPA.151-3.T1.bin to  c2900-universalk9-mz.SPA.152-2.T.bin and this solve this issue.

So  in conclution from the beginner the configuration in boths sides  (provider Gib Telecom and Our Cisco router- CUCM) was ok. The issue was  the firmware router!!!.

cisco is reporting this new BUG.