Page 1 of 1

Disconnected Number status

PostPosted: Wed May 28, 2008 4:50 pm
by TroyD
Quick question, I am using TE120P by Digium for our dialer, currently i have no DC status appearing, instead it is dispositioned as a B (busy). the only way I have found to try and seperate real busys from actual disconnected numbers is to look at the call legnth and if its more than a few seconds I determine that it is a disconnected number due to the busy signal after the recording. This is my zapata.conf:

[channels]
group=0
signalling=pri_cpe
switchtype=dms100
context=default
echocancel=yes
usedistinctiveringdetection=yes
callerid=asreceived
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
rxgain=0.0
txgain=0.0
resetinterval=never
;callprogress=yes
busydetect=yes
busycount=4
channel => 1-23

any ideas as to why there is no signaling to indicate a disconnected number? might I have the zapata.conf set up incorrectly? Does anyone have a sample of their config that I can try with mine?

thanks..

PostPosted: Wed May 28, 2008 11:33 pm
by mflorell
What kind of circuit are you connected to?

D4/AMI or B8ZS/ESF?

RBS or PRI?

If PRI, what signalling protocol?

What country is the circuit located in?

PostPosted: Thu Jun 05, 2008 3:30 pm
by TroyD
From What I can Tell it is

B8ZF :Line Coding
ESF :Framing
DS1

Believe it is a PRI

and the Switch Type is DMS

D Channel is on 24

US Circuit Located in Florida

PostPosted: Fri Jun 06, 2008 7:20 am
by mflorell
I have quite a bit of experience with PRI T1s in Florida :)

Who is the carrier?

There are a lot of issues with PRI signalling here in the US because of the lack of standards in signalling.

It is strange that the disconnects are showing up as BUSYs, usually they wil just show as a type 16 normal clearing(which is still wrong).

one other possibility is that these calls are busy congestion on the carrier side, meaning that your carrier can't handle your calling volume. I have seen this happen before.

PostPosted: Mon Jun 09, 2008 11:12 am
by TroyD
Airespring is the provider (the underlying T1 is Quest)

I dont have more than 6 calls at once being made, so it should not be using more trunks than available..I have been watching that due to the drops showing up on occasion and fiddling with Adaptive dialing VS Ratio.

PostPosted: Mon Jun 09, 2008 7:56 pm
by mflorell
Would you have some Asterisk CLI output of these calls?

Re: Disconnected Number status

PostPosted: Thu Jan 24, 2013 11:59 am
by omarrodriguezt