Hi guys, I've had a sporadic problem recently with one of my users on our POTS line. About 1/3 of the time he dials a number (usually from a speeddial on his phone, I think), he'll get some phone company message (from the outside) about how the call could not be completed as dialed or something like that. However, the logs (and the console) always show the correct dialed digits. Anyone have a similar symptom? I theorize that perhaps Asterisk picks up the line and starts dialing too quickly for our service occasionally. Is there a way that I could stick a delay before the digits are sent down the wire to test this theory? I checked out the wiki but didn't see much pertaining to this. I figure maybe you can put some control characters on the beginning of a dial string to have it pause, but it doesn't seem to be ',' or 'p'. Thanks, jl
On Fri, 2004-01-09 at 11:42, john lawler wrote:> Hi guys, > > I've had a sporadic problem recently with one of my users on our POTS > line. About 1/3 of the time he dials a number (usually from a speeddial > on his phone, I think), he'll get some phone company message (from the > outside) about how the call could not be completed as dialed or > something like that. > > However, the logs (and the console) always show the correct dialed digits. > > Anyone have a similar symptom? I theorize that perhaps Asterisk picks > up the line and starts dialing too quickly for our service > occasionally. Is there a way that I could stick a delay before the > digits are sent down the wire to test this theory? I checked out the > wiki but didn't see much pertaining to this. I figure maybe you can put > some control characters on the beginning of a dial string to have it > pause, but it doesn't seem to be ',' or 'p'.p could be pulse, the character you are looking for is w. show application dial Also, asterisk will have to have received every digit before it dials the pots line. So you may wish to look at what asterisk thought it was dialing to determine if it is a DTMF detection error at asterisk or at the remote end. You should be able to watch the console, or track back the CDR logs to see what was dialed out by your user. -- Steven Critchfield <critch@basesys.com>
On Fri, 9 Jan 2004, john lawler wrote:> I've had a sporadic problem recently with one of my users on our POTS > line. About 1/3 of the time he dials a number (usually from a speeddial > on his phone, I think), he'll get some phone company message (from the > outside) about how the call could not be completed as dialed or > something like that.I had a similar problem with a client. I hooked up a butt set to the line and listened and only heard 4-5 digits being sent. The problem ended up being high loop current on the line. It should be around 20-25 milliamps, but this one was 45. High loop current can cause a variety of strange problems. There is more information on it at www.sandman.com if you want to look. The easiest way to fix it is to put a 500 or 1k ohm 1 watt resistor in series with both tip and ring. dave -- Dave Weis "I believe there are more instances of the abridgment djweis@sjdjweis.com of the freedom of the people by gradual and silent encroachments of those in power than by violent and sudden usurpations."- James Madison