From: Andrea Zanetti (AZanetti@thrupoint.net)
Date: Thu Mar 10 2005 - 07:18:20 GMT-3
Thanks Brian, thanks JC.
Brian, your response to question A enlightened me.
On the contrary, there is still something that I don't understand about
"one or two" numbers using BRI interfaces.
As JC says, there may be some issues when using only one number, for
example when callback feature is on.
I am not at all an ISDN expert, but I think that the following
configurations are correct, in order to have R2 callback R1. Here two
numbers are used to avoid, I think, the busy number problem when R2
calls.
But I cannot see the need of using two numbers when using PPP multilink
feature with dialer load-threshold.
As far as I know, ISDN should be capable to signal to the other end
(actually one end ask the network the resource for a second B channel)
the need of using another B channel for the active call.
And the second B channel is bundled dynamically.
So, why should I use two ISDN numbers with two dialer map commands, when
using ppp multilink and dialer threshold features?
Thanks a lot
Bye
Andrea
--Calling party: R1
interface BRI0/0
ip address 1.42.12.1 255.255.255.0
encapsulation ppp
ip ospf demand-circuit
dialer map ip 1.42.12.2 name R2 broadcast 8358662
dialer map ip 1.42.12.2 name R2 broadcast 8358664
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866101 8358661
isdn spid2 0835866301 8358663
no peer neighbor-route
ppp callback request
ppp authentication chap
dialer-list 1 protocol ip permit
---Called Party: R2
interface BRI0/0
ip address 135.42.12.2 255.255.255.0
encapsulation ppp
dialer map ip 1.42.12.1 name R1 class callr1 broadcast 8358661
dialer map ip 1.42.12.1 name R1 class callr1 broadcast 8358663
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866201 8358662
isdn spid2 0835866401 8358664
no peer neighbor-route
ppp callback accept
ppp authentication chap
dialer-list 1 protocol ip permit
map-class dialer callr1
dialer callback-server username
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: 09 March 2005 18:19
To: Andrea Zanetti; Group Study
Subject: RE: Dialer interface question x 2
Question A Answer:
By default, a dialer interface is treated as a point-to-point link.
This is similar to a point-to-point subinterface with Frame Relay where
you only need to apply the layer 2 address (frame-relay interface-dlci
<dlci>) to the sub interface and all layer 3 addresses map to the single
layer 2 address. With a dialer interface all layer 3 addresses map to
the single layer 2 address (dialer string).
Question B Answer:
This will depend on your ISDN switch configuration. You can normally
tell if you need one or two numbers by the information given. You can
also test this by using the ISDN test call command and see what is
required to connect both B channels.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Andrea Zanetti
Sent: Tuesday, March 08, 2005 11:40 PM
To: 'Group Study'
Subject: Dialer interface question x 2
Hi group,
I cannot understand how dialer interfaces map to broadcasts, and what is
the difference in having one or two numbers on BRI interfaces or dialer
interfaces.
-Question A
When dialer map statements are configured under bri interfaces, the
broadcast keyword tells the machine to send (pseudo)broadcast on the
dial up connection.
On the contrary, when using dialer interfaces with dial string only (one
or two numbers), I cannot see anything that tells the machine whether or
not to send broadcasts on the connection.
-Question B
Sometimes in BRI configuration with multilink PPP only one telephone
number is used.
Sometimes two, one for each B channel. Why? How can I tell if I have to
use one or two?
I know these are very basic questions, but I would appreciate your
comments.
Thanks to everybody
Andrea
Note:The information contained in this message may be privileged and
confidential and protected from disclosure . If the reader of this
message is not the
intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please
notify us
immediately by replying to the message and deleting it from your
computer. Thankyou. ThruPoint Ltd.
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:44 GMT-3