Re: [asterisk-users] Two PRI setup questions
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 ATT tells me they don't see the B channels coming up, is there a way that I can see this in Asterisk??? Ask ATT to turn off B channel maintenance protocol on the PRI. Asterisk does not support this mode. -- Tilghman ___ --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
Re: [asterisk-users] Two PRI setup questions
Tilghman Lesher wrote: 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 ATT tells me they don't see the B channels coming up, is there a way that I can see this in Asterisk??? Ask ATT to turn off B channel maintenance protocol on the PRI. Asterisk does not support this mode. It may work with either the 4E or 5E switchtypes. There is some code that (I didn't write it) I think unbusies the channels that is executed for one or the other switchtypes. -- Matthew Fredrickson Software/Firmware Engineer Digium, Inc. ___ --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
[asterisk-users] 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 ATT 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 ATT 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 ATT 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
Re: [asterisk-users] Two PRI setup questions
Lutgring, Sam wrote: 1) What switchtype should be configured in the zapata.conf file when ATT 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 ATT 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 ATT 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. ___ --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
Re: [asterisk-users] Two PRI setup questions
Yep - as Doug mentioned, give esf framing and national switchtype a try. I have a PRI from ATT in one of my offices, and use this setup. -erik On 11/1/07, Lutgring, Sam [EMAIL PROTECTED] 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 ATT 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 ATT 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 ATT 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 ___ --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
