Don't forget that not only do the two end switches need to support
clear channel signaling (64K), as opposed to in-band signaling (56K),
but all of the switches used between. The Telco also has it's own
internal internetwork that your data must traverse and if any of those
switches don't support clear channel signaling you will need to back
your data flows down to 56K.
HTH,
AQ
At 06:00 PM 7/5/2000, Taylor, Don wrote:
>The type (brand) of switch used shouldn't really matter, but as mentioned
>before, both of them have to support clear-channel 64K. It's possible that
>the one at the remote side doesn't accept that. If you have someone handy at
>the remote end to console into the router, you can use "debug isdn events"
>(I believe that's the right command) to watch the call coming in. If you see
>a bearer channel capacity error (again, I believe that's the right syntax;
>it's been over a year since I worked heavily with ISDN), you know that
>something on the remote end is expecting 56K. It could also be that the
>router itself is set to respond to 56K only, rather than the fault lying
>with the switch.
>
>- Don
>
>-----Original Message-----
>From: John Neiberger [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, July 05, 2000 2:03 PM
>To: [EMAIL PROTECTED]
>Subject: RE: 56k ISDN??
>
>
>Thanks, that info helps as well. The switch on our side is basic-ni, on the
>remote side it is supposedly dms100. And, we are in different exchanges, so
>that might be part of the problem. USWest ran traces on my calls to that
>site and said the calls were making it there, but the other site was not
>responding. The guy at the remote site can see the call arrive, but then
>the line drops. Odd. Oh well, adventures in troubleshooting, as usual!
>
>Thanks,
>John
>
> > In my experience with ISDN when I worked for Pacific Bell, the only times
>we
> > ever used 56K was when there were legacy switches involved that could
>only
> > handle 56K (in-band signaling, instead of clear-channel). My advice is to
> > try 64K and only move to 56K if you find it's required.
> >
> > Your exchange is the first 3 digits of your phone number AFTER the area
>code
> > (e.g. in the number 123-456-7890, 123 is the area code and 456 is the
> > exchange).
> >
> > Hope this helps. =)
> >
> > - Don
> >
> > -----Original Message-----
> > From: John Neiberger [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, July 05, 2000 1:14 PM
> > To: [EMAIL PROTECTED]
> > Subject: 56k ISDN??
> >
> >
> > I noticed on CCO that when configuring ISDN it suggests settings the
>speed
> > to 56k for calls outside of the local exchange. What types of situations
> > are they actually referring to, and why would we use 56k instead of 64k?
> >
> > Another dumb question: how do we know if a called number is in our local
> > exchange or not? Would this be something I'd have to verify with my
>local
> > provider?
> >
> > TIA for any help, I'm pretty new to the wonderful world of ISDN.
> >
> > John
> >
> >
> >
> >
> >
> > _______________________________________________________
> > Say Bye to Slow Internet!
> > http://www.home.com/xinbox/signup.html
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>****************************************************************************
>*
> > The information in this email is confidential and may be legally
>privileged.
> > It is intended solely for the addressee. Access to this email by anyone
>else
> > is unauthorized.
> >
> > If you are not the intended recipient, any disclosure, copying,
>distribution
> > or any action taken or omitted to be taken in reliance on it, is
>prohibited
> > and may be unlawful. When addressed to our clients any opinions or advice
> > contained in this email are subject to the terms and conditions expressed
>in
> > the governing KPMG client engagement letter.
> >
>****************************************************************************
>*
>
>
>
>
>
>_______________________________________________________
>Say Bye to Slow Internet!
>http://www.home.com/xinbox/signup.html
>
>___________________________________
>UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
>FAQ, list archives, and subscription info: http://www.groupstudy.com
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>*****************************************************************************
>The information in this email is confidential and may be legally privileged.
>It is intended solely for the addressee. Access to this email by anyone else
>is unauthorized.
>
>If you are not the intended recipient, any disclosure, copying, distribution
>or any action taken or omitted to be taken in reliance on it, is prohibited
>and may be unlawful. When addressed to our clients any opinions or advice
>contained in this email are subject to the terms and conditions expressed in
>the governing KPMG client engagement letter.
>*****************************************************************************
>
>___________________________________
>UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
>FAQ, list archives, and subscription info: http://www.groupstudy.com
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
*******************************
Adam Quiggle
Sr. Network Engineer
BP-Amoco/MCI Worldcom
CCNA, MCNE, MCSE
Author of McGraw Hill's BCRAN
[EMAIL PROTECTED]
********************************
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
