[Asterisk-Users] Problems dialing out - possible settings changes
Rich Adamson
radamson at routers.com
Sat Mar 5 08:45:25 MST 2005
> Thought I had this fixed, but it turns out it is not. I've been
> wracking my brain. Here is what I have done:
> - Tried 3 different Qwest PSTN lines (just in case it was a line issue)
> - Tried calling same number from an analog phone plugged directly into
> the Qwest line - NO PROBLEMS.
> - Because of this, I think it is an issue with my * implementation.
> - I have looked at the Dial plan and have made some modifications,
> cleaning up some extra stuff that was not needed.
>
> What is still happening:
> - I am calling a single number for testing purposes. The same number
> each time (yes, I have tried other numbers with the exact same results
> so I decided to stick with one number)
>
> - About 1 out of every 3 or 4 times my call is actually successful. The
> rest of the time I receive the phone company's "the number you called is
> not in service, please check the number and call again"
>
> - I look at the CLI readout that appears using asterisk -vvvvvvvvvvvvcg
> to start and it shows ZAP/g1/<the correct number>
>
> Evidently something is happening in translating the dtmf codes, but I am
> at a loss. More explanation is in my original post below.
>
> Any help would be appreciated as we are going to use this as a
> production box on a small construction job site.
Just a guess here... try inserting a "w" in the beginning of your dial
string to delay the sending of dtmf, etc. In some Qwest cases, their
equipment is not ready to receive dtmf immediately after going off hook
on a call, and effectively drops the first one or two digits.
More information about the asterisk-users
mailing list