Thanks, I had some extra settings under [trunkgroups] in /etc/asterisk/chan_dahdi.conf which were causing the issues. I removed them and the PRI works OK now.
Thanks, Liviu On Wed, Apr 28, 2010 at 3:45 PM, Dave Donovan <[email protected]> wrote: > On Wed, Apr 28, 2010 at 2:57 PM, Liviu Toma <[email protected]> wrote: > >> Hello, >> >> Does anyone have a sample DAHDI configuration for a Digium TE110P card >> ? I need both the /etc/dahdi/system.conf and >> /etc/asterisk/chan_dahdi.conf >> I have mine half working, as in the PRI is up, the D channel comes up, >> when I make an inbound call Asterisk answers it, but as soon as it >> starts playing a message, it hangs up with >> >> -- Channel 1/23, span 1 got hangup, cause 100 >> == Spawn extension (default, s, 4) exited non-zero on 'DAHDI/23-1' >> -- Hungup 'DAHDI/23-1' >> >> Thanks, >> Liviu >> > > Liviu, > > I'm running FreePBX but I made the PRI settings myself. > > /etc/dahdi/system.conf: > # comments from default file skipped > ## Configuration for Bell PRI > span=1,1,0,esf,b8zs > echocanceller=oslec,1-23 > bchan=1-23 > dchan=24 > > > > /etc/asterisk/chan_dahdi.conf > > [trunkgroups] > > [channels] > context=from-pstn > signalling=fxs_ks > rxwink=300 ; Atlas seems to use long (250ms) winks > usecallerid=yes > hidecallerid=no > callwaiting=yes > usecallingpres=yes > callwaitingcallerid=yes > threewaycalling=yes > transfer=yes > canpark=yes > cancallforward=yes > callreturn=yes > echocancel=yes > echocancelwhenbridged=no > faxdetect=incoming > echotraining=800 > rxgain=0.0 > txgain=0.0 > callgroup=1 > pickupgroup=1 > > > ;Uncomment these lines if you have problems with the disconection of your > analog > lines > ;busydetect=yes > ;busycount=3 > > > immediate=no > > ;; Config for Trunk Side PRI to Bell Canada > context=from-pstn > switchtype=dms100 > ;nsf=none > pridialplan=national > ;resetinterval=never > ;inbanddisconnect= > ;priindication=outofband > ;priexclusive=yes > facilityenable=yes > signalling=pri_cpe > ;rxwink=300 ; Atlas seems to use long (250ms) winks > usecallerid=yes > hidecalleridname=no > ;cidsignalling=bell > ;hidecallerid=yes > usecallingpres=yes > ;transfer=yes > echocancel=yes > echocancelwhenbridged=no > ;echotraining=400 > faxdetect=incoming > ;relaxdtmf=yes > ;rxgain=2.0 > ;txgain=3.0 > group=0 > ;callgroup=1 > ;pickupgroup=1 > ;immediate=yes > ;transfertobusy=no > callerid=asreceived > ;accountcode=AAA000 > ;busydetect=yes > ;busycount=6 > ;callprogress=yes > ;progzone=us > channel=>1-23 > > #include dahdi-channels.conf > #include chan_dahdi_additional.conf > #include chan_dahdi_custom.conf > > > In addition, the google turned up > http://networking.ringofsaturn.com/RemoteAccess/isdncausecodes.php which > said this: > > *"Cause No. 100 - Invalid information element contents.* > This cause indicates that the equipment sending this cause has received and > information element which it has implemented; however, one or more of the > fields in the information element are coded in such a way which has not been > implemented by the equipment sending this cause. > What it means: > Like cause 1 and cause 88, this usually indicates that the ISDN number being > dialed is in a format that is not understood by the equipment processing the > call. SPIDs will sometimes fail to initialize with a Cause 100, or a call > will fail with this cause." > > My 2 cents: You might try looking at your facilityenable and pridialplan > settings first. > > I hope this helps. Good luck, > Dave > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
