cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4977
Views
15
Helpful
23
Replies

Setting up BRI

Dear friend.

I have some problem when setting up BRI Interface (2B+D) in Vietnam.

This is my configuration:

Configuration:


interface BRI0/1/0

no ip address

no ip route-cache

isdn switch-type basic-net3

isdn twait-disable

isdn tei-negotiation preserve

isdn point-to-point-setup

isdn incoming-voice voice

isdn static-tei 0

end

Show ISDN Status:


ISDN BRI0/1/0 interface

        dsl 4, interface ISDN Switchtype = basic-net3

    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 4 CCBs = 0

    The Free Channel Mask:  0x80000003


Debug ISDN Q921:

debug isdn q921

debug isdn q921 is              ON.

Jan 31 04:38:23.695: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME

Jan 31 04:38:23.695: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 31 04:38:24.695: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 31 04:38:25.695: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Jan 31 04:38:26.291: ISDN BR0/1/0 Q921: User RX <- IDCKRQ ri=0 ai=127

Jan 31 04:38:26.291: ISDN BR0/1/0 Q921: User TX -> IDCKRP ri=18285 ai=0

Jan 31 04:38:26.695: ISDN BR0/1/0 Q921: User TX -> SABMEp sapi=0 tei=0

Debug ISDN Q931:

Jan 31 04:47:39.707: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Jan 31 04:47:45.707: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Jan 31 04:47:51.707: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2


Debug ISDN error interface BRI 0/1/0

Jan 31 04:52:26.607: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x3

Jan 31 04:52:26.611: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x650

Jan 31 04:52:27.631: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x3

Jan 31 04:52:27.631: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x650

Jan 31 04:52:27.707: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x  

Jan 31 04:52:33.707: ISDN BR0/1/0 SERROR: L2_Go: at bailout DLCB is NULL

        L2: sapi 63 tei 127 ces 0 ev 0x650

Jan 31 04:52:33.895: ISDN BR0/1/0 SERROR: service_queue_from_physical_layer: got ISDN_PH_ACT_IND on an active interface?


Please help me to solve this problem.

I can't make call to PSTN.

Thanks all my friends.

VinhPLT

1 Accepted Solution

Accepted Solutions

Are you trying to call 427 from Cisco to PBX ?

If so that is not the right configuration.

View solution in original post

23 Replies 23

ronpatel
Level 8
Level 8

Hi

The status of ISDN is not correct. it should be

MULTIPLE_FRAME_ESTABLISHED and not AWAITING_ESTABLISHMENT.

Check with your service provider and see what is the issue with D channel.

Regards

Ronak Patel

Rate Helpful post.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

Dear Ronak Patel.

Thanks for your help?

So which command should be chaged? switch-type of ISDN?

Regards

VinhPLT

Hi

I believe the switch type is correct. The  problem is with serivce provider. Please check with service provider.

Also send us the full router configuration.

regards

Ronak Patel

Rate Helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

Hi.

I send full router configuration.

how run

Building configuration...

Current configuration : 8254 bytes

!

! Last configuration change at 05:35:46 UTC Thu Jan 31 2013 by cisco

version 15.1

service timestamps debug datetime msec

service timestamps log datetime msec

no service password-encryption

!

hostname FCV-VG

!

boot-start-marker

boot-end-marker

!

!

card type e1 0 0

logging buffered 51200 warnings

!

no aaa new-model

network-clock-participate wic 0

network-clock-participate wic 1

!

no ipv6 cef

ip source-route

ip cef

!

!

!

!

!

ip domain name yourdomain.com

multilink bundle-name authenticated

!

!

!

!

isdn switch-type primary-net5

!

crypto pki token default removal timeout 0

!

crypto pki trustpoint TP-self-signed-2109617910

enrollment selfsigned

subject-name cn=IOS-Self-Signed-Certificate-2109617910

revocation-check none

rsakeypair TP-self-signed-2109617910

voice-card 0

!

!

!

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

h323

sip

!

voice class h323 1

  h225 timeout tcp establish 1

!

!

!

!

!

license udi pid CISCO2911/K9 sn FGL1650115F

hw-module pvdm 0/0

--More--                           !

!

!

username cisco privilege 15 secret 4 tnhtc92DXBhelxjYk8LWJrPV36S2i4ntXrpb4RFmfqY

!

redundancy

!

!

controller E1 0/0/0

pri-group timeslots 1-31

!

controller E1 0/0/1

pri-group timeslots 1-2,16

!

!

!

!

!

interface Embedded-Service-Engine0/0

no ip address

shutdown

!

interface GigabitEthernet0/0

description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$

ip address 172.28.90.60 255.255.255.0

ip virtual-reassembly in

duplex auto

speed auto

!

interface GigabitEthernet0/1

ip address 10.232.72.39 255.255.255.0

ip virtual-reassembly in

duplex auto

speed auto

h323-gateway voip interface

h323-gateway voip bind srcaddr 10.232.72.39

interface Serial0/0/0:15

no ip address

--More--                            ip flow ingress

ip flow egress

encapsulation hdlc

isdn switch-type primary-net5

isdn overlap-receiving

isdn incoming-voice voice

isdn send-alerting

isdn bchan-number-order ascending

isdn sending-complete

no cdp enable

!

interface Serial0/0/1:15

no ip address

ip flow ingress

ip flow egress

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

isdn send-alerting

isdn sending-complete

no cdp enable

!

interface BRI0/1/0

no ip address

no ip route-cache

shutdown

isdn switch-type basic-net3

isdn twait-disable

isdn point-to-point-setup

isdn incoming-voice voice

isdn static-tei 0

!

interface BRI0/1/1

no ip address

isdn switch-type basic-qsig

isdn overlap-receiving

isdn point-to-point-setup

isdn incoming-voice voice

isdn skipsend-idverify

!

ip forward-protocol nd

!

ip http server

ip http access-class 23

ip http authentication local

ip http secure-server

ip http timeout-policy idle 60 life 86400 requests 10000

!

ip route 0.0.0.0 0.0.0.0 10.232.72.254

!

access-list 23 permit any

!

!

!

control-plane

!

!

voice-port 0/0/0:15

!

voice-port 0/1/0

compand-type a-law

connection plar 713

!

voice-port 0/1/1

!

voice-port 0/0/1:15

!

!

!

mgcp profile default

!

!

dial-peer voice 700 voip

description *****Dial-peer to CRM*****

destination-pattern 7..

session target ipv4:10.232.72.31

dtmf-relay h245-alphanumeric

no vad

!

dial-peer voice 1 pots

destination-pattern 01.........

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 2 pots

destination-pattern 09........

--More--                            progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 0/1/0

!

dial-peer voice 3 pots

destination-pattern [2-7].......

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 4 pots

destination-pattern 0[2-7]........

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 5 pots

destination-pattern 0[2-7].........

progress_ind setup enable 3

progress_ind alert enable 8

progress_ind progress enable 8

progress_ind connect enable 8

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 300 pots

destination-pattern 3..

direct-inward-dial

port 0/0/0:15

!

dial-peer voice 600 pots

destination-pattern 6..

direct-inward-dial

port 0/0/1:15

forward-digits all

!

--More--                           !

!

!

gatekeeper

shutdown

!

!

!

line con 0

login local

line aux 0

line 2

no activation-character

no exec

transport preferred none

transport input all

transport output pad telnet rlogin lapb-ta mop udptn v120 ssh

stopbits 1

line vty 0 4

access-class 23 in

privilege level 15

login local

transport input telnet ssh

line vty 5 15

access-class 23 in

privilege level 15

login local

transport input telnet ssh

!

scheduler allocate 20000 1000

end

Thanks for your support!

Regards,

VinhPLT

HI

Why is your BRI0/1/0 interface is shutdown.  Do following

1) Un Shut the interface.

Try and remove below lin kcommand form the BRI0/1/0

2)  no isdn point-to-point-setup

3) isdn static-tei 0

Do clear counters and send out ut of router# show interfaces bri0/1/0 after doing one ISDN test call command.

regards

Ronak Patel

Rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

Hi.

Interface was shutdown when I change switch-type. I forgot to up it

I send you show int bri 0/1/0 output after doing your command.

FCV-VG#show int bri 0/1/0

BRI0/1/0 is up, line protocol is up (spoofing)

  Hardware is Voice NT or TE BRI

  MTU 1500 bytes, BW 64 Kbit/sec, DLY 20000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation VOICE, loopback not set

  Keepalive set (10 sec)

  Last input 00:00:08, output never, output hang never

  Last clearing of "show interface" counters 00:01:18

  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/16 (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

     14 packets input, 112 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

     78 packets output, 364 bytes, 0 underruns

     0 output errors, 0 collisions, 0 interface resets

     0 unknown protocol drops

     0 output buffer failures, 0 output buffers swapped out

     0 carrier transitions

Hi.

For more information, I notice that BRI channel from PSTN have two port RJ-45 output through NT1.

When I connect a digital phone directly into NT1 output port, then the phone has signal (tone & display LCD up).

So can I use that port to connect to BRI interface? Is it different type between line use to connect phone and line to connect to BRI interface. This port is using to connect to SMTD3 card on Siemens HiPath 3800 and now I want to move it to Cisco 2921.

Best Regards.

VinhPLT

Hi

what cable you are using to connect your BRI port with NT box.

Regards

Ronak Patel

Rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

Hi.

I use pin 3-6 to transmit and pin 4-5 to receive.

Regards,

VinhPLT

paolo bevilacqua
Hall of Fame
Hall of Fame

try

interface BRI0/1/0

no isdn static-tei

Dear Paolo.

When I used command no isdn static-tei, Layer 2 status is Inactive.

Regards,

VinhPLT

Then static tei 0 is fine, now you try incoming and outgoing calls.

Note, unless you';re are familiar with CME already, the best approach is that you give the task to a reputable consultant, to avoid much loss of time and frustration.

Dear Paolo.

I have configure at least 3 CME with FXO, E&M and E1 Interface. And this is used as a H.323 VG, not CME.

And this is the 1st time I try to use BRI Interface for 2B+D.

I connect it to PSTN through NT1.

But something maybe wrong. When I connect both of output RJ (one to Cisco and one to Siemens), you can see the result abow. When we unplugged Siemens port to NT1, BRI Interface was down. I don't know what happen with it.

Regards.

VinhPLT

With point-to-point BRI circuits (static-tei 0), you cannot have multiple devices connected to the NT1.

So you can only have the Cisco, or the PBX connected at one time. You can power off the NT1 to have it reset and recognize the new device connected.