From the "hate it when this happens" dept, or, "start using something
and find it's not all there". I know I had this working but my
cvs-committed version doesn't work and I don't know what changed.
I actually live in that vast majority of Canada in which DSL is not
available at any price (of course this is the majority in terms of area,
not population). So please don't suggest this as a way out :-)
I have a GrandStream 488 ATA attached for FXO to a POTS line
(since I'm running * on an Arm box which doesn't have a PCI slot). Set
up pretty much like this: http://astrecipes.net/index.php?n=338.
Asterisk version is 1.4.13. I'm recompiling 1.4.18 as this goes out,
just to be sure there's not a relevant bugfix, but this seems pretty
basic. 488's Firmware is up to date:
Program: 1.0.3.96 Bootloader: 1.1.0.1 HTML: 1.0.3.96 VOC: 1.0.0.13
I can make local 10-digit calls just fine, using this:
[macro-dial-outbound-local]
exten => s,1,Dial(SIP/33/${MACRO_EXTEN},20)
(where SIP/33 connects to the ATA's FXO port).
What's not working is dial out using a long-distance service. The
service works manually from an analog phone. I dial a 10-digit number
and it says "Please enter the number at the dial tone" or similar, then
a dialtone. Calling manually with an analog phone you can start dialing
as soon as the service answers; they listen during their recording. But
trying to automate this seems harder.
[macro-dial-outbound-worldline]
exten => s,1,Dial(SIP/33/${WORLDLINE_ACCESS},20,D(${MACRO_EXTEN}))
This is the part that doesn't work. The problem seems to be that the
DTMF is sent too quickly, before the other end is ready to receive it.
Called 33/416xxxxxxx
-- SIP/33-4dfda000 is ringing
-- SIP/33-4dfda000 answered USTM/[EMAIL PROTECTED]
-- Sending DTMF '613xxxxxxx' to the called party.
The last line appears almost before I can get my hand off the call
button; * is thinking the call is "answered" because it got through to
the SIP ATA, not that it's actually given the ATA a chance to call.
Any ideas how to proceed, or what is the best strategy to pursue?
What's even a good set of google keywords for this?
Thanks!
Ian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
