asterisk users - Nov 2007 - Two PRI setup questions

I am in the process of implementing a new ISDN pri and have a couple of
questions.  This is a full 24 channels (23 B and 1 D) delivered over a T1
interface.  The interface looks good and is not showing any errors.  Any help
that you can provide would be greatly appreciated.
 
1)  What switchtype should be configured in the zapata.conf file when AT&T
is using CUSTOM?  My understanding is that this equates to the dms100 in
Asterisk, is this right?  The D channel is coming up just fine, but AT&T
tells me that they cannot see the B channels.  When I try to make a call I get a
slow busy and the debug shows an ISDN cause code of 34, no circuit available.
 
2)  Is there a way to see the idle status of a B channel?  When AT&T tells
me they don't see the B channels coming up, is there a way that I can see
this in Asterisk???
 
Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20071101/c81025d8/attachment.htm

Lutgring, Sam wrote:
>
> 1)  What switchtype should be configured in the zapata.conf file when 
> AT&T is using CUSTOM?  My understanding is that this equates to the 
> dms100 in Asterisk, is this right?  The D channel is coming up just 
> fine, but AT&T tells me that they cannot see the B channels.  When I 
> try to make a call I get a slow busy and the debug shows an ISDN cause 
> code of 34, no circuit available.
Most PRI setups in the US that I've delt with are esf.  My setup below:

#
# Zaptel Configuration File

span=1,1,0,esf,b8zs
defaultzone=us
loadzone=us
bchan=1-23
dchan=24


Zapata Configuration file
switchtype=national
context=pri
signalling=pri_cpe
group=1
echocancel=yes
echotraining=yes
echocancelwhenbridged=yes
rxgain=-1.0
txgain=-4.0
busydetect=no
callprogress=no
pridialplan=unknown
usercallerid=yes
callerid=asreceived
channel => 1-23
> 2)  Is there a way to see the idle status of a B channel?  When AT&T 
> tells me they don't see the B channels coming up, is there a way that 
> I can see this in Asterisk???
You'll see the b channels restart when the first come up:

[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/1 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/2 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/3 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/4 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/5 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/6 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/7 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/8 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/9 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/10 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/11 
successfully restarted on span 1
[Oct 23 04:23:53] VERBOSE[17121] logger.c:     -- B-channel 0/12 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/13 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/14 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/15 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/16 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/17 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/18 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/19 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/20 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/21 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/22 
successfully restarted on span 1
[Oct 23 04:23:54] VERBOSE[17121] logger.c:     -- B-channel 0/23 
successfully restarted on span 1



-- 
Ben Franklin quote:

"Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety."

Yep - as Doug mentioned, give esf framing and national switchtype a try.

I have a PRI from AT&T in one of my offices, and use this setup.

-erik

On 11/1/07, Lutgring, Sam <LutgrinS at calhounisd.org>
wrote:
>
>
>
> I am in the process of implementing a new ISDN pri and have a couple of
> questions.  This is a full 24 channels (23 B and 1 D) delivered over a T1
> interface.  The interface looks good and is not showing any errors.  Any
> help that you can provide would be greatly appreciated.
>
> 1)  What switchtype should be configured in the zapata.conf file when
AT&T
> is using CUSTOM?  My understanding is that this equates to the dms100 in
> Asterisk, is this right?  The D channel is coming up just fine, but
AT&T
> tells me that they cannot see the B channels.  When I try to make a call I
> get a slow busy and the debug shows an ISDN cause code of 34, no circuit
> available.
>
> 2)  Is there a way to see the idle status of a B channel?  When AT&T
tells
> me they don't see the B channels coming up, is there a way that I can
see
> this in Asterisk???
>
> Thanks in advance.
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>
> http://lists.digium.com/mailman/listinfo/asterisk-users
>

-- 
Erik Anderson
http://andersonfam.org

On Thursday 01 November 2007 19:31:39 Lutgring, Sam
wrote:
> 2)  Is there a way to see the idle status of a B channel?  When AT&T
tells
> me they don't see the B channels coming up, is there a way that I can
see
> this in Asterisk???
Ask AT&T to turn off "B channel maintenance protocol" on the PRI. 
Asterisk
does not support this mode.

-- 
Tilghman