asterisk users - Nov 2004 - Interfacing T100P with Definity PBX

Hi,
   I have two t100p cards installed. One card connected to the PSTN,
the other card is hooked to the Definity PBX with a T1 cross over
cable. The card connected to the PSTN works fine.
   The problem is with the card hooked up to the PBX. The light behind
the card is green, but when I dial from this card I get an error. Its
says it could start the D-Channel. Could someone help me out with this
problem
   Here are the sections of my configuration files
--------------------------------------------------------------------
;; /etc/zaptel.com
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs
bchan=1-23
dchan=24

;; This is the problematic card
loadzone=us
defaultzone=us
span=2,0,0,esf,b8zs
bchan=25-47
dchan=48
---------------------------------------------------------------------
;; /etc/asterisk/zapata.conf
context = default
switchtype = national
signalling = pri_cpe
group = 1
channel => 1-23

;; The problematic card
context = default
switchtype = national
overlapdial = yes
signalling = pri_net
group = 2
channel => 25-47
------------------------------------------------------------------------

I tried with different options for the switchtype too. The signalling
id definitely pri_net

Would really be grateful for any help in this regard.

Thanks and regards,
 - Ashish

On November 27, 2004 06:46 am, Ashish Shinde wrote:
>    I have two t100p cards installed. One card connected to the PSTN,
> the other card is hooked to the Definity PBX with a T1 cross over
> cable. The card connected to the PSTN works fine.
>    The problem is with the card hooked up to the PBX. The light behind
> the card is green, but when I dial from this card I get an error. Its
> says it could start the D-Channel. Could someone help me out with this
> problem
> span=1,0,0,esf,b8zs
If span 1 is the telco you want sync to be '1' not 0 -- you want the
span to
take clock from the PSTN.  span 2 with sync '0' is right 99% of the time
--
most PBXes and KSUs don't have an option to be the sync source so
they'll be
trying to sync from *, which should have it span sync set to '0' to
achieve
this.
> ;; The problematic card
> context = default
> switchtype = national
> overlapdial = yes
> signalling = pri_net
> group = 2
> channel => 25-47
Just out of curiosity, does your PBX allow overlap dial?  I'd try setting it
to 'no' and trying.

Other than that, it appears that this setup is identical to mine with my 
Norstar MICS.  Since you are getting errors about the D channel not being up 
I would imagine you have a configuration error on your PBX side, as this end 
certainly looks fine.  Does * say that span 1's D channel is up?

-A.