Thanks Eric.
That is exactly what the problem was. I actually added a D(1) instead of
the w, but either would work I'm sure. Its odd that you couldn't get a
better error than that. I mean, asterisk should be able to tell what was
actually sent and received by the other end. I shouldn't say it
"sho
John Novack wrote:
Not option w
add a "w" in the DIAL STRING
Guess you didn't search the archives?
Sometime in 1.2 this feature was fixed to work with pulse dial as well.
If he had searched the archives, he never would have posted the message
in the first place.
_
OPTIONS to the Dial line (at the end) are different the special digits
in the number string.
Rob Schall wrote:
Also, in the dial command the "w" says its for the *1 recording. Not
waiting. Is the documentation wrong? What is the correct way to wait in
the dial command?
Rob
John Novack w
You want Asterisk to dial 1-630-XXX-XXX, but the telco only got
630-XXX-, which the provider will see "630-" and assume your
current area code of 312.
Rob Schall wrote:
But if this was the case, then why would the message playback (from the
provider) read back the digits from the sta
What happens if you connect the fxo to the fxs and try several attempts
at completing a call? This should at least tell you if the issue is
outdialed digit issues or telco receipt issues.
Dave
On Mon, 2007-06-04 at 10:30 -0500, Rob Schall wrote:
> But if this was the case, then why would the mess
Asterisk does NOT wait for dialtone when going offhook on an FXO port.
Asterisk is sending digits to the telco too quickly.
Add a "w" (.5 second wait) before the extension to be dialed. Example:
exten => _91NXXNXX,n,Dial(${TRUNK}/w${EXTEN:${TRUNKMSD}},,wW)
Rob Schall wrote:
Here's a poss
Not option w
add a "w" in the DIAL STRING
Guess you didn't search the archives?
Sometime in 1.2 this feature was fixed to work with pulse dial as well.
example:
exten => s,1,Dial(ZAP/g4/w(${ARG1:3:4}),360,Tt)
John Novack
Rob Schall wrote:
Also, in the dial command the "w" says its fo
Also, in the dial command the "w" says its for the *1 recording. Not
waiting. Is the documentation wrong? What is the correct way to wait in
the dial command?
Rob
John Novack wrote:
>
>
> Rob Schall wrote:
>> Here's a possible bug, or more likely, I'm just missing something.
>>
>> We have a
Don't overthink this
Error messages from providers are frequently misleading and inaccurate
Some only use one recording for anything they think they can't process.
Add at least one "w" to the dial string and see if all the misdials
don't go away.
Also check the list archives for MANY such compla
But if this was the case, then why would the message playback (from the
provider) read back the digits from the start. I mean, I dialed
630-XXX-XXX and it reads back 312 (my local area code)-630-XXX-X
I would think if it wasn't waiting, then it would do like a 312-30X-XX-XX
Rob
John Novack wrot
Rob Schall wrote:
Here's a possible bug, or more likely, I'm just missing something.
We have a pots card in one of our asterisk boxes. Its a simple asterisk setup with one FXO/FXS card and basic static extensions file, etc. When we dial out over the pots line, 4 out of 5 times, it will work. H
Here's a possible bug, or more likely, I'm just missing something.
We have a pots card in one of our asterisk boxes. Its a simple asterisk
setup with one FXO/FXS card and basic static extensions file, etc. When
we dial out over the pots line, 4 out of 5 times, it will work. However,
every 4 or 5 t
12 matches
Mail list logo
