I do not believe that the original poster intended to use backup interface, and I do not believe that backup interface is necessarily needed here. The floating static default route points to the dialer interface:
ip route 0.0.0.0 0.0.0.0 10.100.1.1
ip route 0.0.0.0 0.0.0.0 192.168.99.13 20
and if the primary static default route is withdrawn the router will begin sending traffic to the dialer.
I do note that in the amount of configuration shown I do not see a way to get to 10.100.1.1 and so there may be a problem with the primary static default route. Or it may be that the address is reachable through some interface not shown in the posted config.
I believe that there is a more fundamental problem shown in the original post. One of the lines indicates that layer 1 is not active. If layer 1 is not active then nothing can be sent over this interface. Perhaps we could have posted the output of show isdn status. This would clarify the status of layer 1 and layer 2 for the ISDN.
the 10.100.1.1 can be reach through Eigrp so there is no problem of the primary static route, but when i ping the other peer for the isdn 192.168.99.13 the layer 1, and 2 will be active before that it will be deactive
ar-BRH#sh isdn status
Global ISDN Switchtype = basic-dms100
ISDN BRI0/0/0 interface
dsl 0, interface ISDN Switchtype = basic-net3
Layer 1 Status:
Layer 2 Status:
TEI = 101, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
In almost all part of the world (with the notable exception of North America), the telco switch deactivates L1 and L2 on the S/T bus of ISDN BRI circuits, after few seconds of inactivity. I never got to understand in full why is that, but so it is.
As soon an incoming or outgoing call is attempted, both L1 and L2 are reactivated.
Only recently, ISDN code in IOS has began to address this situation better than before, with the command "isdn tei-negotiation preserve". This way, no time is lost in obtaining a TEI every time the link reactivates.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...