Re: Cisco 2821 with E1

Faheem Ansari · ‎12-29-2010

hello,

I just configured E1 on my router to connect with local telco switch by configuring following parameters;

controller E1 0/0/1

pri-group timeslots 1-30

description FMX_HUB

!

interface Serial0/0/1:15

description FMX_HUB

no ip address

encapsulation hdlc

isdn switch-type primary-qsig

isdn timer T310 120000

isdn overlap-receiving

isdn protocol-emulate network

isdn incoming-voice voice

no cdp enable

!

And after applying above mentioned configuration I got following status on E1 Controller

E1 0/0/1 is up.

Applique type is Channelized E1 - balanced

Cablelength is Unknown

Description: FMX_HUB

No alarms detected.

alarm-trigger is not set

Version info Firmware: 20100222, FPGA: 13, spm_count = 0

Framing is CRC4, Line Code is HDB3, Clock Source is Line.

but i am unable to make any call to PSTN dial-peers are properly configured and up and running for other E1s. debug output is

HUB-CORE#debug isdn q921

*Dec 29 09:35:54.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:35:55.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:01.987: ISDN Se0/0/1:15 Q921: L2_EstablishDataLink: sending SABME

*Dec 29 09:36:01.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:02.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:03.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:04.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:10.987: ISDN Se0/0/1:15 Q921: L2_EstablishDataLink: sending SABME

*Dec 29 09:36:10.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:11.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:12.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:13.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:19.987: ISDN Se0/0/1:15 Q921: L2_EstablishDataLink: sending SABME

*Dec 29 09:36:19.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:20.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:21.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

*Dec 29 09:36:22.987: ISDN Se0/0/1:15 Q921: User TX -> SABMEp sapi=0 tei=0

HUB-CORE#debug isdn q931

debug isdn q931 is ON.

*Dec 29 09:36:50.987: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Dec 29 09:36:59.987: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Dec 29 09:37:08.987: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Dec 29 09:37:17.987: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Dec 29 09:37:26.987: ISDN Se0/0/1:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Dec 29 10:22:40.019: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for Controller E1 0/0/1

now help me to find the problem.

Haitham Hasan Abdel Mohde · ‎12-29-2010

Hi Faheem,

hope everything is well.

why you configur encapsulation under the serial interface?

B.R./Haitham

If this helps, Please Rate

paolo bevilacqua · ‎12-29-2010

habdelmo wrote:

why you configur encapsulation under the serial interface?

Please note: Whatever encapsulation is configured, or not configured, under a voice serial interface, will not make any difference.

The OP problem is caused by the fact that telco has not completed the provisioning, or the circuit is faulty. Nothing related to the router.

Logan Gaffney · ‎12-29-2010

I would also check to see if you should indeed be emulating the network (unde the serial interface). Usually if you are going directly to the Telco switch, they are network. Regardless, we should be Tx and Rx SAMBE messages, i.e.:

*Dec 29 19:39:05.841: ISDN Se0/1/0:15 Q921: Net TX -> RRp sapi=0 tei=0 nr=60

*Dec 29 19:39:05.841: ISDN Se0/1/0:15 Q921: Net RX <- RRp sapi=0 tei=0 nr=66

*Dec 29 19:39:05.841: ISDN Se0/1/0:15 Q921: Net TX -> RRf sapi=0 tei=0 nr=60

*Dec 29 19:39:05.845: ISDN Se0/1/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=66

paolo bevilacqua · ‎12-29-2010

lgaffney wrote:

Usually if you are going directly to the Telco switch, they are network.

May I nitpick again? Not usually, but always.

Faheem Ansari · ‎12-30-2010

when i tried to initiate call i got follwoing messages on debug

*Dec 30 12:54:41.507: ISDN Se0/0/0:15 Q921: Net TX -> RRp sapi=0 tei=0 nr=37
*Dec 30 12:54:41.519: ISDN Se0/0/0:15 Q921: Net RX <- RRp sapi=0 tei=0 nr=37
*Dec 30 12:54:41.519: ISDN Se0/0/0:15 Q921: Net TX -> RRf sapi=0 tei=0 nr=37
*Dec 30 12:54:41.583: ISDN Se0/0/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=37
*Dec 30 12:54:48.011: ISDN Se0/0/0:15 Q921: Net RX <- INFO sapi=0 tei=0, ns=37 nr=37
*Dec 30 12:54:48.011: ISDN Se0/0/0:15 Q921: Net TX -> RR sapi=0 tei=0 nr=38
*Dec 30 12:54:48.011: ISDN Se0/0/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 6, call id 0x1E, call ref 0x8002, event 0x7B
*Dec 30 12:54:48.015: ISDN Se0/0/0:15 Q921: Net TX -> INFO sapi=0 tei=0, ns=37 nr=38
*Dec 30 12:54:48.043: ISDN Se0/0/0:15 Q921: Net RX <- INFO sapi=0 tei=0, ns=38 nr=37
*Dec 30 12:54:48.043: ISDN Se0/0/0:15 Q921: Net TX -> RR sapi=0 tei=0 nr=39
*Dec 30 12:54:48.047: ISDN Se0/0/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 6, call id 0x1E, call ref 0x8002, event 0x7B
*Dec 30 12:54:48.047: ISDN Se0/0/0:15 Q921: Net TX -> INFO sapi=0 tei=0, ns=38 nr=39
*Dec 30 12:54:48.075: ISDN Se0/0/0:15 Q921: Net RX <- INFO sapi=0 tei=0, ns=39 nr=37
*Dec 30 12:54:48.075: ISDN Se0/0/0:15 Q921: Net TX -> RR sapi=0 tei=0 nr=40
*Dec 30 12:54:48.075: ISDN Se0/0/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 6, call id 0x1E, call ref 0x8002, event 0x7B
*Dec 30 12:54:48.079: ISDN Se0/0/0:15 Q921: Net TX -> INFO sapi=0 tei=0, ns=39 nr=40
*Dec 30 12:54:48.211: ISDN Se0/0/0:15 Q921: Net RX <- RR sapi=0 tei=0 nr=38
*Dec 30 12:54:48.363: ISDN Se0/0/0:15 Q921: Net RX <- RR sapi=0 tei=0 nr=39
*Dec 30 12:54:48.511: ISDN Se0/0/0:15 Q921: Net RX <- RR sapi=0 tei=0 nr=40
*Dec 30 12:54:51.527: ISDN Se0/0/0:15 Q921: Net RX <- RRp sapi=0 tei=0 nr=40
*Dec 30 12:54:51.531: ISDN Se0/0/0:15 Q921: Net TX -> RRf sapi=0 tei=0 nr=40
*Dec 30 12:55:01.527: ISDN Se0/0/0:15 Q921: Net TX -> RRp sapi=0 tei=0 nr=40
*Dec 30 12:55:01.539: ISDN Se0/0/0:15 Q921: Net RX <- RRp sapi=0 tei=0 nr=40
*Dec 30 12:55:01.539: ISDN Se0/0/0:15 Q921: Net TX -> RRf sapi=0 tei=0 nr=40
*Dec 30 12:55:01.607: ISDN Se0/0/0:15 Q921: Net RX <- RRf sapi=0 tei=0 nr=40
*Dec 30 12:55:11.547: ISDN Se0/0/0:15 Q921: Net RX <- RRp sapi=0 tei=0 nr=40
*Dec 30 12:55:11.547: ISDN Se0/0/0:15 Q921: Net TX -> RRf sapi=0 tei=0 nr=40

and no call in the end

paolo bevilacqua · ‎12-30-2010

Now you have to look at "show isdn status", should be multiframe established.

Then, you disable debug isdn q921, and enable q931 instead.

Faheem Ansari · ‎01-01-2011

Problems has been resolved now, but i have to wait for some time after dialing a number to establish a call.. every this is fine with E1, no errors on L2 or L3 but when i enable Debug ISDN Q931 following logs display on my screen...

Router_HUB#
*Jan 1 14:50:52.535: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8 callref = 0x0359
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98399
                Exclusive, Channel 25
        Calling Party Number i = 0x0181, '202786'
                Plan:ISDN, Type:Unknown
        High Layer Compat i = 0x9181
*Jan 1 14:50:52.539: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_INCOMING
*Jan 1 14:50:52.539: ISDN Se0/0/0:15 EVENT: call_incoming: call_id 0x0011, Guid = 5D3FF4988016
*Jan 1 14:50:52.543: ISDN Se0/0/0:15 Q931: TX -> SETUP_ACK pd = 8 callref = 0x8359
        Channel ID i = 0xA98399
                Exclusive, Channel 25
        Progress Ind i = 0x8188 - In-band info or appropriate now available
*Jan 1 14:50:52.571: ISDN Se0/0/0:15 Q931: RX <- STATUS pd = 8 callref = 0x0359
        Cause i = 0x81E31E - Information element not implemented
        Call State i = 0x02
*Jan 1 14:50:53.531: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0359
        Called Party Number i = 0x81, '2'
                Plan:ISDN, Type:Unknown
*Jan 1 14:50:53.531: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_INFO
*Jan 1 14:50:54.231: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0359
        Called Party Number i = 0x81, '0'
                Plan:ISDN, Type:Unknown
*Jan 1 14:50:54.231: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_INFO
*Jan 1 14:50:54.419: ISDN Se0/0/0:15 Q931: RX <- INFORMATION pd = 8 callref = 0x0359
        Called Party Number i = 0x81, '0'
                Plan:ISDN, Type:Unknown
*Jan 1 14:50:54.419: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_INFO
*Jan 1 14:51:08.447: ISDN Se0/0/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x0359
        Cause i = 0x8190 - Normal call clearing
*Jan 1 14:51:08.447: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_DISC
*Jan 1 14:51:08.451: ISDN Se0/0/0:15 Q931: TX -> RELEASE pd = 8 callref = 0x8359
*Jan 1 14:51:08.475: ISDN Se0/0/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x0359
        Cause i = 0x8190 - Normal call clearing
*Jan 1 14:51:08.475: ISDN Se0/0/0:15 EVENT: process_rxstate: ces/callid 1/0x11 calltype 2 CALL_CLEARED