RE: Dialer watch questions

From: Lupi, Guy (Guy.Lupi@xxxxxxxxxxxxx)
Date: Fri Apr 19 2002 - 11:43:04 GMT-3


   
12.1(12) is what I am using.

~-----Original Message-----
~From: Sean C. [mailto:Upp_and_Upp@hotmail.com]
~Sent: Friday, April 19, 2002 12:48 AM
~To: Lupi, Guy; ccielab@groupstudy.com
~Subject: Re: Dialer watch questions
~
~
~ok, next question - what's the IOS? Dialer watch isn't stable
~to 12.1(7)
~
~http://www.cisco.com/warp/public/471/backup_cookbook.html#ts_watch
~----- Original Message -----
~From: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>
~To: "'Sean C.'" <Upp_and_Upp@hotmail.com>; "ying chang"
~<ying_c@hotmail.com>; <ccielab@groupstudy.com>
~Sent: Thursday, April 18, 2002 6:28 PM
~Subject: RE: Dialer watch questions
~
~
~Thank you for the suggestion, but I had it on there already.
~It really has
~to be something having to do with dialer watch, I had the exact same
~callback configs working with snapshot and OSPF demand
~circuits. I also
~tried the dialer redial interval, no luck.
~
~~-----Original Message-----
~~From: Sean C. [mailto:Upp_and_Upp@hotmail.com]
~~Sent: Friday, April 19, 2002 12:31 AM
~~To: ying chang; Lupi, Guy; ccielab@groupstudy.com
~~Subject: Re: Dialer watch questions
~~
~~
~~Hi Guy and Chang,
~~
~~Sorry, I'm walking into this post wayyyy too late (it's not
~~nice when FedEx
~~ships 3 routers to the wrong city and now I have 2 hours
~~rather than 2 days
~~to get up some microwave T1 circuits) but I'm wondering if
~~you're looking
~~for these commands for using callback:
~~
~~on the callback server:
~~Dialer enable-timout 5
~~
~~on the callback client:
~~dialer wait-for-carrier-time 10
~~
~~From CCO: When an incoming call arrives and the router finds
~~a best match
~~configured for callback, the router uses the value configured
~~by the dialer
~~enable-timeout command to determine the length of time to wait
~~before making
~~the callback.
~~
~~The minimum value of the timer is 1 second; the default value
~~of the timer
~~is 15 seconds. The interval set for this feature on this
~~router must be much
~~less than that set for DDR fast call rerouting for ISDN (that
~~interval is
~~set by the dialer wait-for-carrier command) on the calling
~~(remote) side. We
~~recommend setting the dialer wait-for-carrier timer on the
~~calling side to
~~twice the length of the dialer enable-timeout timer on the
~~callback side.
~~
~~Again, sorry if I'm walking into something that has already
~~been suggested
~~but I didn't see any configs so I don't know if these have
~~been applied.
~~HTH,
~~Sean
~~
~~
~~
~~
~~----- Original Message -----
~~From: "ying chang" <ying_c@hotmail.com>
~~To: <Guy.Lupi@eurekaggn.com>; <ccielab@groupstudy.com>
~~Sent: Thursday, April 18, 2002 5:58 PM
~~Subject: Re: Dialer watch questions
~~
~~
~~Hi Guy,
~~
~~I've experienced the samething about two weeks ago. The problem is the
~~called party have to drop the line to callback. I do not think
~~there's any
~~hook for us to tell the dialer-watch don't make another call
~~even the line
~~is dropped, I also could not find anything to adjust how often
~~dialer-watch
~~can make calls. Since dialer-watch has responsibility to
~~reestablish the
~~link, as soon as the called party drop the line, it would make
~~another call,
~~and the result is the calling and the called party are in the race
~~condition. If you constantly get connected, that's good. In my case,
~~sometimes it made the connection to bri:0, sometimes it made
~~to bri:1, but
~~most of the time it just failed.
~~
~~Chang
~~
~~
~~>From: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>
~~>Reply-To: "Lupi, Guy" <Guy.Lupi@eurekaggn.com>
~~>To: "'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
~~>Subject: Dialer watch questions
~~>Date: Thu, 18 Apr 2002 15:37:46 -0400
~~>
~~>I have a working dialer watch config with ppp callback, but
~~the watching
~~>router attempts to call the other router about 10 times
~~before finally the
~~>other router calls back and the line comes up. Has anyone seen this
~~>before?
~~>I have the same callback configuration working fine with OSPF demand
~~>circuits and snapshot routing, only when I use dialer watch
~~do I see this
~~>come up. Below is a show isdn history from the router that
~~is requestion
~~>callback:
~~>
~~>r2#sh isdn hist
~~>--------------------------------------------------------------
~~-------------
~~-
~~>----
~~> ISDN CALL HISTORY
~~>--------------------------------------------------------------
~~-------------
~~-
~~>----
~~>Call History contains all active calls, and a maximum of 100 inactive
~~>calls.
~~>Inactive call data will be retained for a maximum of 15 minutes.
~~>--------------------------------------------------------------
~~-------------
~~-
~~>----
~~>Call Calling Called Remote Seconds Seconds
~~Seconds Charges
~~>Type Number Number Name Used Left Idle
~~>Units/Currency
~~>--------------------------------------------------------------
~~-------------
~~-
~~>----
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>In 1111 2222 r8 18 - -
~~>
~~>Out 1111 r8 0
~~ 0
~~>
~~>In 1111 2222 r8 12 - -
~~>
~~>--------------------------------------------------------------
~~-------------
~~-
~~>----
~~>
~~>r2#



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:13 GMT-3