BRI Leased-Line service is only available in Japan and Germany, and operates
like a serial point-to-point leased line. However, the service has to be
requested. Also, I understand that channel aggregation at 128K is only
available in Japan. Can you confirm that this service has been setup for
you, and that Germany now supports 128k channel aggregation. Do you have a
properly configured device at the other end of the leased-line?

CM

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]
> Sent: 09 July 2001 01:25
> To: [EMAIL PROTECTED]
> Subject: RE: My BRI interface will not respond! [7:11045]
> 
> 
> Well, your current config doesn't look like it will do much - there's
> nothing to tell it where to dial.  I suspect that is the cause of your
> error message.
> How are you trying to get it to dial?  Traffic to 192.168.8.0 will be
> directed to BRI1/0, but BRI1/0 has no dialer string or dialer map to
> associate a number to dial.
> 
> If you've tried other configs that do have the association, 
> have you spoken
> to your telco to find out whether they actually think the 
> ISDN service is
> working?
> 
> JMcL
> 
> ---------------------- Forwarded by Jenny Mcleod/NSO/CSDA on 
> 09/07/2001
> 10:03 am ---------------------------
> 
> 
> "Uche Ishionwu" @groupstudy.com on 06/07/2001
> 05:05:59 pm
> 
> Please respond to "Uche Ishionwu" 
> 
> Sent by:  [EMAIL PROTECTED]
> 
> 
> 
> To:   [EMAIL PROTECTED]
> cc:
> 
> 
> Subject:  RE: My BRI interface will not respond! [7:11045]
> 
> 
> Hello Jenny,
> 
>  currently the lights are blinking, but there seems to be no 
> data-traffic.
>  you might want to take a look at my current config.
> 
>   -Uche.
> 
>  ps: this is the only message i keep on receiving upon 
> implementing debug
> isdn q921/9931 !---->
> 
>   00:36:15: No dialer db, manual isdn call can't dial out
> 
> ....what does this mean please???
> 
> config------>
> 
> 
> oks>en
> Password:
> oks#sh conf
> Using 1662 out of 29688 bytes
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname oks
> !
> no logging console
> no logging monitor
> enable secret 5 $1$DjGs$cxj/.CpMxoel/kKvi.Wqn1
> !
> !
> !
> !
> !
> memory-size iomem 15
> ip subnet-zero
> !
> isdn switch-type basic-net3
> isdn voice-call-failure 0
> isdn tei-negotiation first-call
> isdn leased-line BRI1/0 128
> !
> !
> !
> interface FastEthernet0/0
>  ip address 192.168.0.2 255.255.255.0
>  no ip directed-broadcast
>  duplex auto
>  speed auto
> !
> interface BRI0/0
>  description This is my
> domain!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!
>  no ip address
>  no ip directed-broadcast
>  shutdown
>  isdn switch-type basic-net3
> !
> interface BRI1/0
>  description l
>  ip address 192.168.8.2 255.255.255.0
>  no ip directed-broadcast
>  fair-queue 64 16 0
> !
> interface BRI1/1
>  no ip address
>  no ip directed-broadcast
>  shutdown
>  isdn switch-type basic-net3
> !
> interface BRI1/2
>  no ip address
>  no ip directed-broadcast
>  shutdown
>  isdn switch-type basic-net3
> !
> interface BRI1/3
>  no ip address
>  no ip directed-broadcast
>  shutdown
>  isdn switch-type basic-net3
> !
> interface Dialer0
>  no ip address
>  no ip directed-broadcast
>  dialer in-band
>  no cdp enable
> !
> interface Dialer1
>  ip address negotiated
>  ip directed-broadcast
>  dialer in-band
>  dialer map ip 192.168.9.5 name ELSATEST 02710755
>  no cdp enable
> !
> ip classless
> ip route 192.168.0.0 255.255.255.0 FastEthernet0/0
> ip route 192.168.8.0 255.255.255.0 BRI1/0
> no ip http server
> !
> !
> map-class dialer xxxxxxxx
> !
> map-class dialer oks_cisco1
> dialer-list 1 protocol ip permit
> !
> line con 0
>  password ucheoma
>  transport input none
> line aux 0
> line vty 0 4
>  login
> !
> end




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=11419&t=11045
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to