Interestingly, after I made that post I was reading something else
related to ISDN and saw that if you're in the UK it had to be
basic-net3. :-) So, you're right, it's probably not a switch
configuration issue, but it's acting exactly like the situation I had
when it was a switch issue.
The switch type was configured correctly on my side but the remote side
had the wrong setting. They would see my incoming config requests but
then the call would immediately be dropped. We worked on that for a
*long* time before I called Qwest back and asked to speak to a different
engineer who was clueful.
Where is the location you are dialing, is it also in the UK? Given
those debug results it's fairly clear that your side is speaking to the
ISDN switch, it's your end-to-end connection that is hosed. Are you
calling out of your local exchange? I'm not sure how those switches
operate but over here we have to hard-set the speed of the call to 56k
for inter-exchange calls.
Do those switches require SPIDs? If so, are your SPIDs valid?
Good luck,
John
>>> "Row Adel" 4/10/01 5:13:22 AM >>>
Hey,
I will need to get hold of the debug and status output (not in the
office at
present). But I remember that "sh isdn status" tells me that layer 1
is
active and layer 2 has multiple_frame_established. Also, I am in the UK
and
so it is definitely basic net 3.
As for the debug output on the connection, the LCP shows status listen
and
"0" (zero) indicating outgoing requests but no "I" to show incoming
data.
This occurs several times until timeout.
There is remarkably little info out there on dealing with a failure at
this
stage! I may have to redo the configuration using legacy DDR instead
of
dialer profiles to see if it is my setup causing this, or perhaps even
a
hardware problem in one of the routers.
As soon as I can get some debug I will post.
Thanks a lot,
Row.
""John Neiberger"" wrote in message
sad1e88f.065@fsutil01">news:sad1e88f.065@fsutil01...
> I have seen behavior like this that was caused by having the wrong
> switch type configured. However, we had the wrong one configured
> because we actually trusted Qwest! They told us we had a 5ESS
> switch which was partially true. In reality it was a 5ESS switch
> running National ISDN software. In that situation you need to
configure
> a basic-ni1 switch type.
>
> I don't know what the specific problem might be in your case, but it
> might be something along those lines. If you don't know *for
certain*
> it might be worthwhile to check with your provider and verify the
switch
> type.
>
> BTW, could we see the debug output as well as the output from "show
> isdn status"?
>
> Good luck,
> John
>
> >>> "Row Adel" 4/9/01 4:22:04 PM >>>
> Hello,
>
> I am configuring Cisco 801 ISDN routers to link two offices together
> via
> dial-on-demand. The connection fails to even get to the CHAP
> authentication
> stage (tried PAP also). On debugging the connection attempts (debug
> PPP
> negotiation), it is clear that the failure is occuring at the LCP
> stage.
> Neither router is sending LCP configuration details. Whichever side
> initiates the connection, there is no incoming request received in
> response
> to the outgoing conFREQ's and so the connection times-out after 24
> seconds.
> IOS version is 12 and ISDN connectivity is proven (basic net 3).
> Can anyone help with where to look for the problem?
> Thanks in advance.
> Row.
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=58&t=44
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
