RE: BRI [7:70059]

2003-06-04 Thread Dom
Show isdn status then use debug isdn q921 for more detailed information.


Best regards,

Dom Stocqueler
CTO - SysDom Technologies

 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 03 June 2003 10:33
To: [EMAIL PROTECTED]
Subject: Re: BRI [7:70059]


Hi ppl,

i'm encountering some issues on the 2nd channel, it takes quite a while
for it to come up despite the 1st channel hits the threshold, is there
any command that i can issue to monitor on the 2nd channel?

thanks

regards,

jef




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70062t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: BRI [7:70059]

2003-06-04 Thread Devrim Yener KUCUK
debug isdn q921 is for the layer 2 activity ( for the signalling between the
router and the swith, like TEI, SAPI...)

you can be using:
debug dialer
debug isdn q931 to watch what is going layer 3.

you can check
sh isdn stat -- and see the number of channels occupied

or

sh int bri 0 -- for the D channel
sh int bri 0:1- for the first B channel
sh int bri 0:2 for the second be channel


Regards

De
- Original Message -
From: Dom 
To: 
Sent: Tuesday, June 03, 2003 1:39 PM
Subject: RE: BRI [7:70059]


 Show isdn status then use debug isdn q921 for more detailed information.


 Best regards,

 Dom Stocqueler
 CTO - SysDom Technologies



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 03 June 2003 10:33
 To: [EMAIL PROTECTED]
 Subject: Re: BRI [7:70059]


 Hi ppl,

 i'm encountering some issues on the 2nd channel, it takes quite a while
 for it to come up despite the 1st channel hits the threshold, is there
 any command that i can issue to monitor on the 2nd channel?

 thanks

 regards,

 jef




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70067t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


RE: BRI [7:70059]

2003-06-04 Thread Andrew Larkins
as well as debu ppp multilink

-Original Message-
From: Dom [mailto:[EMAIL PROTECTED]
Sent: 03 June 2003 13:39
To: [EMAIL PROTECTED]
Subject: RE: BRI [7:70059]


Show isdn status then use debug isdn q921 for more detailed information.


Best regards,

Dom Stocqueler
CTO - SysDom Technologies

 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: 03 June 2003 10:33
To: [EMAIL PROTECTED]
Subject: Re: BRI [7:70059]


Hi ppl,

i'm encountering some issues on the 2nd channel, it takes quite a while
for it to come up despite the 1st channel hits the threshold, is there
any command that i can issue to monitor on the 2nd channel?

thanks

regards,

jef




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70068t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: BRI [7:70059]

2003-06-04 Thread Devrim Yener KUCUK
debug isdn q921 is for the layer 2 activity ( for the signalling between the
router and the swith, like TEI, SAPI...)

you can be using:
debug dialer
debug isdn q931 to watch what is going layer 3.

you can check
sh isdn stat -- and see the number of channels occupied

or

sh int bri 0 -- for the D channel
sh int bri 0:1- for the first B channel
sh int bri 0:2 for the second be channel


Regards

De

- Original Message -
From: Dom 
To: 
Sent: Tuesday, June 03, 2003 1:39 PM
Subject: RE: BRI [7:70059]


 Show isdn status then use debug isdn q921 for more detailed information.


 Best regards,

 Dom Stocqueler
 CTO - SysDom Technologies



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 03 June 2003 10:33
 To: [EMAIL PROTECTED]
 Subject: Re: BRI [7:70059]


 Hi ppl,

 i'm encountering some issues on the 2nd channel, it takes quite a while
 for it to come up despite the 1st channel hits the threshold, is there
 any command that i can issue to monitor on the 2nd channel?

 thanks

 regards,

 jef




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70069t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


RE: BRI [7:70059]

2003-06-04 Thread Dom
Sorry De.
Debug q931 is what is needed. It has been about 5 years since I last
touched ISDN thank God!

Best regards,

Dom Stocqueler
 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Devrim Yener KUCUK
Sent: 03 June 2003 14:17
To: [EMAIL PROTECTED]
Subject: Re: BRI [7:70059]


debug isdn q921 is for the layer 2 activity ( for the signalling between
the router and the swith, like TEI, SAPI...)

you can be using:
debug dialer
debug isdn q931 to watch what is going layer 3.

you can check
sh isdn stat -- and see the number of channels occupied

or

sh int bri 0 -- for the D channel
sh int bri 0:1- for the first B channel
sh int bri 0:2 for the second be channel


Regards

De
- Original Message -
From: Dom 
To: 
Sent: Tuesday, June 03, 2003 1:39 PM
Subject: RE: BRI [7:70059]


 Show isdn status then use debug isdn q921 for more detailed 
 information.


 Best regards,

 Dom Stocqueler
 CTO - SysDom Technologies



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 03 June 2003 10:33
 To: [EMAIL PROTECTED]
 Subject: Re: BRI [7:70059]


 Hi ppl,

 i'm encountering some issues on the 2nd channel, it takes quite a 
 while for it to come up despite the 1st channel hits the threshold, is

 there any command that i can issue to monitor on the 2nd channel?

 thanks

 regards,

 jef




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70074t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: BRI [7:70059]

2003-06-04 Thread MADMAN
Actually a debug isdn q931 would be more pertinent, 921 is your 
conection to the switch whereas 931 is call setup.  A debug dialer could 
also be useful.

   Dave

Andrew Larkins wrote:
 as well as debu ppp multilink
 
 -Original Message-
 From: Dom [mailto:[EMAIL PROTECTED]
 Sent: 03 June 2003 13:39
 To: [EMAIL PROTECTED]
 Subject: RE: BRI [7:70059]
 
 
 Show isdn status then use debug isdn q921 for more detailed information.
 
 
 Best regards,
 
 Dom Stocqueler
 CTO - SysDom Technologies
 
  
 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: 03 June 2003 10:33
 To: [EMAIL PROTECTED]
 Subject: Re: BRI [7:70059]
 
 
 Hi ppl,
 
 i'm encountering some issues on the 2nd channel, it takes quite a while
 for it to come up despite the 1st channel hits the threshold, is there
 any command that i can issue to monitor on the 2nd channel?
 
 thanks
 
 regards,
 
 jef
-- 
David Madland
CCIE# 2016
Sr. Network Engineer
Qwest Communications
612-664-3367

Government can do something for the people only in proportion as it
can do something to the people. -- Thomas Jefferson




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70075t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: BRI [7:70059]

2003-06-04 Thread nakul malik
I suggest u debug ISDN in its entirety.
use: debug isdn ? to see all options for debugging ISDN.
It seems your call setup is taking too long. so monitor the d channel as
well.
See how long it takes for call setup on initial establishment (1st channel). 
Then check the time it takes to setup the call for the second channel. 
Some providers, atleast a while back, used the D channel to carry
performance
data. It may be the case with ur provider as well which is why it is taking
long
to setup the second channel.
If this doesnt work, try sniffing the line.
HTH
-N


Date: Tue, 3 Jun 2003 14:05:13 GMT
 Devrim Yener KUCUK  [EMAIL PROTECTED] Re: BRI [7:70059]Reply-To:
Devrim
Yener KUCUK 

debug isdn q921 is for the layer 2 activity ( for the signalling between the
router and the swith, like TEI, SAPI...)

you can be using:
debug dialer
debug isdn q931 to watch what is going layer 3.

you can check
sh isdn stat -- and see the number of channels occupied

or

sh int bri 0 -- for the D channel
sh int bri 0:1- for the first B channel
sh int bri 0:2 for the second be channel


Regards

De

- Original Message -
From: Dom 
To: 
Sent: Tuesday, June 03, 2003 1:39 PM
Subject: RE: BRI [7:70059]


 Show isdn status then use debug isdn q921 for more detailed information.


 Best regards,

 Dom Stocqueler
 CTO - SysDom Technologies



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: 03 June 2003 10:33
 To: [EMAIL PROTECTED]
 Subject: Re: BRI [7:70059]


 Hi ppl,

 i'm encountering some issues on the 2nd channel, it takes quite a while
 for it to come up despite the 1st channel hits the threshold, is there
 any command that i can issue to monitor on the 2nd channel?

 thanks

 regards,

 jef
NAKUL MALIK

H-342
New Rajendra Nagar
New Delhi-110060
India

Ph: +91-11-582-3488
Cell: +91-9811424477
Fax: +91-11-575-7334

Mail-on-cell: [EMAIL PROTECTED]


-
Express yourself with a super cool email address from BigMailBox.com.
Hundreds of choices. It's free!
http://www.bigmailbox.com
-




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70085t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: BRI [7:70059]

2003-06-03 Thread koh jef
Hi ppl,

i'm encountering some issues on the 2nd channel, it takes quite a while for
it to come up despite the 1st channel hits the threshold, is there any
command that i can issue to monitor on the 2nd channel?

thanks

regards,

jef 


Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=70059t=70059
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]