C40 isdn Bri problem

Hi all
Now my Cisco C40 use two BRI Europe isdn lines to connect the another site's tandbeg system.
The C40 can connected the remote site successful, but the remote site's screen is so small.
is there anyone konw it?

Note: Your question would be better placed in the TelePresence section of the forums where these devices are more actively discussed than in the Conferencing section you've posted in - I'd suggest you move your discussion via the Edit button at the top of the page.
Can you please describe a bit more what you mean by the "screen is so small". The fact that you are using ISDN should have no impact on how the screen displays.
Can you also provide more information on how your C40 is configured - ie, what is the output device, what resolution is it set to on the C40, are you specifying a non-default layout? Is the other end presenting and hence you're seeing a presentation layout?
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Similar Messages

Cisco 1812 ISDN BRI Problem

following is my configuration of 1812.
interface BRI0
no ip address
encapsulation frame-relay IETF
dialer pool-member 1
isdn switch-type basic-net3
isdn point-to-point-setup
interface Dialer0
ip address xx.xx.xx.xx 255.255.255.252
encapsulation frame-relay IETF
dialer pool 1
dialer idle-timeout 0
dialer string XXXXXX
dialer max-call 4095
dialer persistent
frame-relay interface-dlci 16
frame-relay lmi-type q933a
my porblem is this when ever my Line of BRI is fluctuate for any reason my router does not automatically redials. instead i have to restart the router every time.
could any one suggesst me is there any thning wrong in my configuration.
but same configuration works well in 1841 with BRI module installed.
Thanks in advance.
Regards

Although you may manually configure dial peers to work with the MLPP for Analog and BRI Endpoints on Cisco IOS Voice Gateways feature, we recommend that you use Cisco CallManager autoconfiguration. Refer URL
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00804202c9.html#wp1050570

Problem connecting isdn bri voice interface to pstn

i'm trying to configure my ISDN BRI NT/TE voice interface card (VIC-2BRI-NT/TE) on router 3825 to link to my PSTN provider. This must allow my Cisco IP phones to pass call to the PSTN through my call manager 4.1.
I suscribe to two isdn line. The provider told me that the SWITCH TYPE is VN6 (COTE d'IVOIRE or Ivory Coast).
For my bri configuration, see file "interfaces configuration..."
My problem is that when i pass call from my Ip telephony network, the first call goes well. But after this first call, when i type the command isdn status, i can see that the layer 1 of my isdn interfaces are DEACTIVATED, and after a few minutes, it turn back to ACTIVE. During these minuite, i can't pass any call through my isdn interface.
for outputs of show isdn status command, and isdn debug q931 commands
see file "show isdn status and debug..."
Notice: when the status of the isdn layer is in the deactvated status, i can receive call from the pstn, but i can't passe call to pstn (the state changes to ACTIVE when incomming call from pstn arrive, but still stay DEACTIVATED when outgoing call is initiated)
Please help me

I've entered the "isdn transition-delay 1" interface command and things seem to work well.According to the IOS help on my router,this command clears the ISDN D-CHANNEL after a delay of 1 second.
But i would like to get more information on this command, and also on the isdn layer 2 and 3 timers, and even possible on all the "isdn" interface command option.
THANKS

BRI problems / layer 1 deactivated

Hi there
I could really use some help for this issue. I need to implement a BRI line for voice as backup for a SIP line.
However I cannot make layer 1 come up as active. I know for sure the line is working as attaching a phone to the ISDN2 line makes me able to receive and make calls. So the line is ok from teleprovider side. Must be cable issue, makes a cable according to Cisco doc. "When the ISDN BRI port on the router is configured as an NT port, you must use a "rolled" cable (one with the transmit and receive leads swapped) to connect to a TE interface." But this does not help me still same outcome.
Any help is much appriciated.
Cisco2921 router IOS: 15.0 (1r) with BRI module NT/TE 2gen.
VGW#sh isdn status
Global ISDN Switchtype = basic-net3
ISDN BRI0/0/0 interface
        dsl 0, interface ISDN Switchtype = basic-net3
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        Layer 2 NOT Activated
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask: 0x80000003
ISDN BRI0/0/1 interface
        dsl 1, interface ISDN Switchtype = basic-net3
    Layer 1 Status:
        DEACTIVATED
    Layer 2 Status:
        Layer 2 NOT Activated
    Layer 3 Status:
        0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask: 0x80000003
    Total Allocated ISDN CCBs = 0
VGW#sh controllers bri0/0/0
BRI unit 0:
layer 1 operating in LT-T mode.
Layer 1 is DEACTIVATED. (ISDN L1 State F3)
D Channel Information:
idb at 0x294042F4, driver data structure at 0x2941FF40
Infineon Chip Version 0x1
Infineon Registers:
Int. Status Register [ISTA]=0x00, Aux. Int. [AUXI]=0x00
D-channel: Int. Status Reg: [ISTAD]=0x00, Status. Reg: [STARD]=0x40
Mode Reg: [TR_MODE]=0x01
Transceiver Reg: [TR_CONF0]=0x00
Test mode Reg: [TMD]=0x00
IOM Control Reg: [IOM_CR]=0x08
Status Register [STAR]=0x40, Mode Register [MODED]=0xCA
Serial Data Strobe Control Reg: [SDS1_CR]=0x00, [SDS2_CR]=0x00
RX Buffer Descriptor is at 0x30BF37E4, Buffer size 1524
pak=0x3172EF74 data_ptr=0xE1D5FD4 partial_size=0x0
TX Buffer Descriptor is at 0x2940FEBC
pak=0x0 data_ptr=0x0 partial_size=0x0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns 0 d channel collisions
B1 Channel Information:
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns 0 d channel collisions
B2 Channel Information:
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns 0 d channel collisions
B2 Channel Information:
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns 0 d channel collisions
interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving
isdn point-to-point-setup
isdn incoming-voice voice interface BRI0/0/0
no ip address
isdn switch-type basic-net3
isdn overlap-receiving
isdn point-to-point-setup
isdn incoming-voice voice

I had this problem a few months ago and it took several days of investigation and research to figure it out but I got there in the end. Hopefully this will save someone else a lot of frustration!
In short it was mainly sorted by adding the bearer-cap Speech command to my extra voice-ports.
This command specifies whether the 'call' will initialize for voice or data during the setup and can cause the line to drop/disconnect if it is set incorrectly.
FULL DETAILS
My client was using a UC540W-BRI-K9 with 2 phone lines coming in over a single ISDN device connected to a voice-port. They had purchased a plug-in 2-port voice-board to allow them to utilize another 4 phone lines via an extra 2 ISDN devices, however the company who installed this had failed to configure the system properly so even after I activated the extra lines they would always fail to dial-out as above.
The first step was to tell the plug-in voice-board to use the network-clock and set the ISDN-connected BRIs to use the network-clock:
network-clock-participate wic 1
network-clock-participate wic 2
network-clock-select 1 BRI0/1/0
network-clock-select 2 BRI0/1/1
network-clock-select 3 BRI0/2/0
I spent time investigating the BRI configuration, adding a few bits which I think helped activate the lines, although I still had the outgoing call failures on the new lines:
interface BRI0/1/0
no ip address
isdn switch-type basic-net3 <--- Copied this command to the other BRIs
isdn tei-negotiation first-call   <--- Added this to all the BRIs
isdn point-to-point-setup
isdn incoming-voice voice
isdn sending-complete
isdn static-tei 0 <--- Added this to all the BRIs
trunk-group ALL_BRI 64      <--- Copied this command to the other BRIs
I then found the voice-ports had a separate configuration independent of the BRIs and the newly connected voice-ports required a couple of commands to be copied from the original, working voice-port. The problem was fixed once I applied the bearer-cap Speech command to the extra voice-ports, along with compand-type a-law (for a European system).
voice-port 0/1/0      <--- The original voice-port connected to the primary ISDN
compand-type a-law    <--- Copied to the newly-connected voice-ports
bearer-cap Speech   <--- Copied to the newly-connected voice-ports
voice-port 0/1/1        <--- Connected to 2nd ISDN
compand-type a-law
bearer-cap Speech
voice-port 0/2/0        <--- Connected to 3rd ISDN
compand-type a-law
bearer-cap Speech
voice-port 0/2/1      <--- Unused
The compand-type command is used to convert signals from analog to digital and is normally compand-type u-law for North America systems and compand-type a-law for European systems, as explained here:
http://www.cisco.com/en/US/docs/ios/12_3/vvf_r/vrg_c4_ps1839_TSD_Products_Command_Reference_Chapter.html#compand-type

ISDN BRI connection won't stay up

Hi all,
I'm trying to get the S/T port on 3 routers to connect thru ISDN BRI. Thus far I've only been able to get this to work on a 1601.
My attempts on an 878 and a soho96 are less succesfull.
Both are able to establish a connection, but it won't stick.
Attached is the output of the debug isdn q921. The top shows the succesfull connection on the 1601, the bottom shows the other result. The only discrepancy I can find is the lack of a IS.DN BR0: TX -> INFOc message after the tei exchange is succesfull.
I am in the dark however on whether this is a symptom or the cause of the problem. Searches on the cisco domain don't turn up much on this part of the layer 2 troubleshooting.
Any thoughts are welcome on this subject.
Regards
Wouter

Hello,
there is an earlier thread (see the link below), where the problem was related to the fact that the 878 needs the Advanced Enterprise IOS (and not the Advanced IP Services IOS) for the ISDN interface to function, you might want to check if you are running into the same issue.
http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=WAN%2C%20Routing%20and%20Switching&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1dd96928/10#selected_message
Regards,
GNT

Connecting to an ISDN BRI on a router from a PSTN line from remote site..!!

Friends,
I have a 1812 at HO with WIC1 BS/T Card, connected it to an ISDN BRI line.One of my critical remote location uses Leased circuit to reach my HO Router.But in case if LL goes down,some of the important PC's at the remote site should be able to dial to HO Router BRI Number using PSTN line, get connected and continue, ip address assigned from HO Router and access the application... Is any way available...

Hi Arnab.
You need to configure dial backup through AUX port. You need to connect a normal PSTN line to a modem which in turn is connected to your AUX port. You will have to configure a chat script which you can find in the attachmnet. The attachment is a working example in one of my routers.
You also have to create an ASYNC interface. Check that in the attached file also
--Pls rate if useful---

No dialer command under ISDN BRI interface

Hi all,
I have a 2901 router voice bundle with 4 ISDN BRI ports and would like to have them bundled under Dialer1 interface. Unfortunately it doesn't give me option for Dialer command under BRI interface as expected.
router(config-if)#int bri0/0/0
router(config-if)#dia
router(config-if)#dia
^
% Invalid input detected at '^' marker.
router(config-if)#dialer
^
% Invalid input detected at '^' marker.
router(config-if)#
I assume it's down to the UC license installed on the device but not sure. Does the ISDN BRI interface behave in different way under this license?
Pasting portion of "show ver" as well.
Cisco CISCO2901/K9 (revision 1.0) with 479232K/45056K bytes of memory.
Processor board ID
2 Gigabit Ethernet interfaces
4 ISDN Basic Rate interfaces
1 terminal line
DRAM configuration is 64 bits wide with parity enabled.
255K bytes of non-volatile configuration memory.
250880K bytes of ATA System CompactFlash 0 (Read/Write)
License Info:
License UDI:
Device# PID SN
*0 CISCO2901/K9
Technology Package License Information for Module:'c2900'
Technology Technology-package Technology-package
Current Type Next reboot
ipbase ipbasek9 Permanent ipbasek9
security None None None
uc uck9 Permanent uck9
data None None None
Configuration register is 0x2102

Hi,
Snippet of "sh ver" with IOS version is below:
router#show ver
Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(4)M5, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Fri 13-Sep-13 14:59 by prod_rel_team
ROM: System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1)
router uptime is 2 days, 21 hours, 47 minutes
System returned to ROM by reload at 16:48:03 UTC Mon Aug 18 2014
System restarted at 16:50:01 UTC Mon Aug 18 2014
System image file is "flash0:c2900-universalk9-mz.SPA.152-4.M5.bin"
Last reload type: Normal Reload
Last reload reason: Reload Command
The output of trying to type dialer command is in the initial post, I'm also pasting all available commands under bri0/0/0.
router(config-if)#int bri0/0/0
router(config-if)#?
Interface configuration commands:
aaa Authentication, Authorization and Accounting.
access-expression Build a bridge boolean access expression
arp Set arp type (arpa, probe, snap), timeout, log
options or packet priority
authentication Auth Manager Interface Configuration Commands
autodetect Autodetect Encapsulations on Serial interface
bandwidth Set bandwidth informational parameter
bgp-policy Apply policy propagated by bgp community string
bridge-group Transparent bridging interface parameters
carrier-delay Specify delay for interface transitions
cdp CDP interface subcommands
clns CLNS interface subcommands
clock Configure serial interface clock
cwmp Configure CPE WAN Management Protocol(CWMP) on this
interface
dampening Enable event dampening
default Set a command to its defaults
delay Specify interface throughput delay
description Interface specific description
dot1q dot1q interface configuration commands
dot1x Interface Config Commands for IEEE 802.1X
down-when-looped Force looped serial interface down
encapsulation Set encapsulation type for an interface
ethernet Ethernet interface parameters
exit Exit from interface configuration mode
flow-sampler Attach flow sampler to the interface
full-duplex Configure full-duplex operational mode
h323-gateway Configure H323 Gateway
half-duplex Configure half-duplex and related commands
help Description of the interactive help system
history Interface history histograms - 60 second, 60 minute
and 72 hour
hold-queue Set hold queue depth
ip Interface Internet Protocol config commands
iphc-profile Configure IPHC profile
ipv6 IPv6 interface subcommands
isdn ISDN Interface configuration commands
isis IS-IS commands
iso-igrp ISO-IGRP interface subcommands
keepalive Enable keepalive
line-power Provide power on the line.
llc2 LLC2 Interface Subcommands
load-interval Specify interval for load calculation for an
interface
logging Configure logging for interface
loopback Configure internal loopback on an interface
mab MAC Authentication Bypass Interface Config Commands
mac-address Manually set interface MAC address
macro Command macro
metadata Metadata Application
mop DEC MOP server commands
mtu Set the interface Maximum Transmission Unit (MTU)
netbios Use a defined NETBIOS access list or enable
name-caching
network-clock-priority Configure clock source priority
no Negate a command or set its defaults
ntp Configure NTP
ospfv3 OSPFv3 interface commands
pulse-time Force DTR low during resets
rate-limit Rate Limit
redundancy RG redundancy interface config
routing Per-interface routing configuration
sdllc Configure SDLC to LLC2 translation
serial serial interface commands
service-policy Configure CPL Service Policy
shutdown Shutdown the selected interface
smds Modify SMDS parameters
snapshot Configure snapshot support on the interface
snmp Modify SNMP interface parameters
source Get config from another source
tarp TARP interface subcommands
timeout Define timeout values for this interface
topology Configure routing topology on the interface
transmit-interface Assign a transmit interface to a receive-only
interface
trunk-group Configure interface to be in a trunk group
tx-ring-limit Configure PA level transmit ring limit
vpdn Virtual Private Dialup Network
vrf VPN Routing/Forwarding parameters on the interface
waas WAN Optimization
router(config-if)#

2509 Access Server and ISDN BRI connection

Hi yall..
I'm a newbe to CISCO havin just completed my CCNA.I would like to know how should i configure a 2509's async to communicate with a windows PC on the other end via ISDN.I have 2 TA's 1(extenal and internal )modems and 2 ISDN BRI line connections with me.plz help..
regards
Pranny..:)

Hi,
Please see the config examples.
http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a00800943ad.shtml
http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/products_configuration_guide_chapter09186a008008722c.html
HTH,
-amit singh

ISDN BRI INTERFACE

Isdn bri interface is used as backup by serial interface
backup delay 10 60
under bri interface following command is also configured
dialer idle-timeout 900
what will be idle timeout of bri interface if serial interface comes back and functional.

Hello Jabbar,
this looks like a cisco BCRAN question, here it goes:
the backup delay 10 60 , means that it will take 10 seconds before the secondary link comes up, after the primary goes down, and it will take 60 seconds after the primary goes back up, before the secondary goes down.
dialer idle-timeout 900:
this command indicates how long the call can stay idle before it is disconnected.
from cisco:
"This command is used on lines for which there is no contention. When contention occurs, the dialer fast-idle command is activated. For example, when a busy line is requested to send another packet to a different destination than it is currently connected to, line contention occurs and the dialer fast-idle command is activated.
By default, this command applies to inbound and outbound calls. For example, if a receiving system needs to make outgoing calls, you might configure it with a short idle timeout.
Only packets that match the dialer group reset the idle timer."
So, I guess it would be 900s
HTH,
please rate this post if it does,
Vlad

ISDN BRI U

Hi All,
I recently purchased Cisco 2811 with ISDN BRI U HWIC for ISDN connectivity. Unfortunately, when I connect the card to my ISDN NT box, the light on the ISDN NT box keeps flashing signifying no connectivity, while there are no signs of light behind the HWIC card either. When I swapped this out with a normal ISDN BRI S/T card, I can see a steady light on the NT box and also light behind the HWIC on the router meaning there is connectivity between the router and the ISDN NT box.
A quick check on Cisco website shows that these type of cards require RJ-49C connector (see site below)
http://www.cisco.com/en/US/prod/collateral/modules/ps5949/data_sheet_c78_439537.html
Can someone be kind enough to let me know if/why normal RJ-45 cables cannot be used? Also, I am struggling to get information online on these RJ-49C connectors.
Thanks
Austin

ISDN needs proper cabling, not Ethernet cabling.
The pinour is in the product manual.

Cisco 4-Port ISDN-BRI Network Module

Cisco 4-Port ISDN-BRI Network Module
what does the BRI mean?
I have this module in a 2600 series router. Can it be used for basic LAN connection (like a hub)?

First, to answer your question: No, you cannot.
ISDN is a Telco technology and protocol suite.
"BRI" stands for "Basic Rate Interface," also described as "2B+D" for two Bearer channels and a "D" channel, which is used for control signaling in some configurations, and additional bandwidth in others.
Max throughput is either 128K (2 X 56K or 64Kbps per channel) or 144Kbps (2B+16K that may be available in the D channel depending on your config.
ISDN requires an intermediate telco-style switch between the clients and can't be used back-to-back directly.
Good Luck
Scott

ISDN BRI layer 1 & layer 2 do not sustain "active" statuses

Hi Expert,
I have some routers which can not sustain the ISDN layer 1 & layer 2 statuses correctly. Whenever, the ISDN line is manually activated or the ISDN BRI ports are manually reset, the layer 1 & layer 2 statuses become active but they become deactivated after a while. I have changed the ISDN module and the same symptom is observed. Would you advise what is the cause and resolution. Your advice in this matter is greatly appreciated.
Thanks and Regards,
Jason Peh

Hi Rick,
Below is the show interface for BRI1/0,
router_2#sh isdn status
Global ISDN Switchtype = basic-net3
ISDN BRI1/0 interface
dsl 8, interface ISDN Switchtype = basic-net3
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
TEI = 66, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
Layer 3 Status:
0 Active Layer 3 Call(s)
Activated dsl 8 CCBs = 0
The Free Channel Mask: 0x80000003
router_2#sh int BRI1/0
BRI1/0 is up (spoofing), line protocol is up (spoofing)
Hardware is BRI
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Last input 00:04:39, output 00:04:39, output hang never
Last clearing of "show interface" counters 24w4d
Input queue: 0/75/0 (size/max/drops); 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)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
27807 packets input, 207167 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
27921 packets output, 209138 bytes, 0 underruns
0 output errors, 0 collisions, 551 interface resets
0 output buffer failures, 0 output buffers swapped out
1680 carrier transitions
router_2#sh int BRI1/0:1
BRI1/0:1 is down, line protocol is down
Hardware is BRI
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Closed, multilink Closed
Last input 04:59:17, output 04:59:17, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 108 drops; input queue 0/75, 1 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
7434 packets input, 1689890 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
2 input errors, 0 CRC, 1 frame, 1 overrun, 0 ignored, 1 abort
10743 packets output, 782350 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
4682 carrier transitions
router_2#sh int BRI1/0:2
BRI1/0:2 is down, line protocol is down
Hardware is BRI
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Closed, multilink Closed
Last input 04:59:22, output 04:59:22, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 3 drops; input queue 0/75, 3 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
6902 packets input, 1530090 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
3 input errors, 0 CRC, 3 frame, 0 overrun, 0 ignored, 3 abort
7527 packets output, 594592 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
25 carrier transitions
I have another router with the same configuration and the statuses are able to sustain correctly. Thus, I doubt that the backup interface command has any effect on the layer 1 & layer 2 statuses.
Best Regards,
Jason Peh

ISDN BRI backup - Disconnect after 1 sec

There is a ISDN BRI backup to Serial IF on a router.BRI seems to be able to cennect with opossite site, but after 1 sec comes Disconnect(see attachment).I tried Floating static routes and Dialer watch as well, with the same result. Can anybode help me? Thanks

There is no aaa new-model statment on both side.I`ve rewrite user/psw and added ppp chap hostname ... command.
output of isdn status follows:
cpp-poprad#
Sep 20 14:52:00.647: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di0
Sep 20 14:52:00.651: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
Sep 20 14:52:00.651: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 0524684841 N/A
Sep 20 14:52:01.655: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 0524684841 cpp-poprad
Sep 20 14:52:01.655: %ISDN-6-DISCONNECT: Interface BRI0/1/0:1 disconnected from 0524684841 cpp-poprad, call lasted 1 seconds
Sep 20 14:52:01.659: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
Sep 20 14:52:01.659: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di0sh isdn statu
Global ISDN Switchtype = basic-net3
ISDN BRI0/1/0 interface
dsl 2, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 71, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 2 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
cpp-poprad#sh isdn act
ISDN ACTIVE CALLS
Call Calling Called Remote Seconds Seconds Seconds Charges
Type Number Number Name Used Left Idle Units/Currency
cpp-poprad#
Sep 20 14:52:18.295: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to up
Sep 20 14:52:18.295: %DIALER-6-BIND: Interface BR0/1/0:1 bound to profile Di0
Sep 20 14:52:18.299: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 05246848411 N/A
Sep 20 14:52:18.351: %ISDN-6-CONNECT: Interface BRI0/1/0:1 is now connected to 05246848411 cpp-poprad
Sep 20 14:52:18.531: %LINK-3-UPDOWN: Interface BRI0/1/0:1, changed state to down
Sep 20 14:52:18.531: %DIALER-6-UNBIND: Interface BR0/1/0:1 unbound from profile Di0sh isdn act

Dialup for isdn bri

how do i configure the authentication for isdn bri as a dialup in cisco routers without radius server?
can i cofigure all the authentication in cisc router?

Check the links:
ISDN Configuration Example - IP :
http://cisco.com/en/US/tech/tk801/tk379/technologies_configuration_example09186a0080094091
.shtml
Sample Configuration: Basic ISDN Configuration :
http://cisco.com/en/US/tech/tk801/tk379/technologies_configuration_example09186a0080094abd
.shtml
You can configure pap, chap for example.
Is that what you are looking for?

Isdn bri dialup

sir,
i configured isdn bri as a dialup in cisco router for remote side clients.
how do i authenticate the clients in cisco router without seperate radius sever.
i tried the following commands only in cisco router.
aaa new-model
username cisco privilege 15 password cisco123
aaa authentication login default local
but authentication is not happening.

You can configure a username/password using CHAP on the dialermap statement.
or
create a local username and configure:-
aaa new-model
aaa authentication login default local
aaa authentication login NO_AUTHEN none
aaa authentication ppp default local
As long as the encapsulation you are using on your BRI interface is PPP !!!!
HTH>

C40 isdn Bri problem

Similar Messages

Maybe you are looking for