~ You have the topology right and have confirmed my suspicion. The modem ~ capping would only be done on remote modems dialing in because the ~ possibility still exists that a remote modem with a clearer circuit ~ path might be able to negotation a higher data rate. I just wanted to ~ make sure that capping the remote modem did not in some way change how ~ the central router needed to be configured to train up.
~ We are trying to troubleshoot unclean or degraded circuit paths but ~ the telcos are not being incredibly helpful. So while we plug away at ~ them I am trying to have other solutions on-hand. ~ ~ I appreciate your infinite patience in terms of helping em out with ~ this and some other issues I have raised here on comp.dcom.sys.cisco ~ in the past, now I have one additional question :) ~ ~ We also have a 3745 and we are hanging an external modem off the aux ~ port for dialin out-of-band management. I have everything set up and I ~ can dial into just fine. I don't have login set on the aux port so ~ when I dial in I go to directly to router> prompt, the issue that when ~ I do so it appears that the modem has responded back to the connection ~ before I see it on my screen, for example I might seen something like ~ this: ~ ~ router>
~ router>RING ~ router>
~ router>CONNECT ~ router>
~ ~ I can still access the router fine, just wondering why I am getting ~ what looks like modem responses back on the display like that. ~ Occasionally I'll even get something like ~ ~ router>
~ router>NO CARRIER ~ router>
~ ~ even though the call connected and I am getting access to the router. ~ What might cause this. I tried turning command echo off on the modem ~ (ATE0) and that didn't work, I though perhaps a chat script was the ~ culprit (we have one on the aux port for dialout on that same modem) ~ but removing it did not help. If I enable 'login' on the aux port when ~ I dialin I get '%Bad Passwords' and I suspect this might be the cause ~ ~ Any thoughts? ~ ~ Thanks again, ~ Robert
Do you have "modem inout" or "modem dialin" and "flush-at-activation" configured on the aux port? If so, then when DCD (which we call "DSR") comes up on the modem, the line's input buffer should be flushed of any "NO CARRIER" "RING", "CONNECT" result code stuff, then the router prompt should be displayed.
To add suspenders to your belt, maybe you can configure your modem not display result codes when answering. (This would be set via Q2 on many modems.)