On Wednesday August 08 2007 8:28 am, Tim Johnson wrote:
> Hi Drew. Thanks for the tips. My Line 1 works as I'd like it to, and I
> could be wrong, but I don't think changing the dialplan there will help. I
> really just want to be able to dial local phone calls (7 digits) and have
> it go out the S
on-Commercial Discussion
Sent: Tuesday, August 07, 2007 5:55 PM
Subject: Re: [asterisk-users] Outbound dialing
Tim,
If the Asterisk stuff below doesn't fix it, try the docs at
http://www.jmgtechnology.com.au/spa_3000_guide.pdf
Ensure you enable VoIP to PSTN gateway mode and
Tim,
If the Asterisk stuff below doesn't fix it, try the docs at
http://www.jmgtechnology.com.au/spa_3000_guide.pdf
Ensure you enable VoIP to PSTN gateway mode and that "PSTN Line" is
registered with Asterisk. This is probably OK as you appear to get
dialtone back from the SPA. If you are ca
Tim Johnson wrote:
> Hello all. I am just getting back into Asterisk and I am setting up my
> Linksys SPA3102. I have incoming calls working fine, as is the phone
> plugged into the unit. My problem is I cannot get the SPA3102 to dial
> a phone number automatically. I can call the extention o
Not specific to the SPA3102, but just normal outbound dialing is as follows:
exten => _1NXXNXX,1,Dial(//${EXTEN})
or if you want to require people to dial 9, then:
exten => _91NXXNXX,1,Dial(//${EXTEN})
or if you're like me and you're used to a cell phone and don't like dialing
the 1:
e
Hello all. I am just getting back into Asterisk and I am setting up my
Linksys SPA3102. I have incoming calls working fine, as is the phone
plugged into the unit. My problem is I cannot get the SPA3102 to dial
a phone number automatically. I can call the extention of the PSTN and
I get a se
On May 20, 2005 07:21 am, Phill Wolf wrote:
> I wish the card (or Asterisk) waited for the dialtone before dialing.
> Sometimes the phone company gives a dialtone within 1 second; other times
> it takes 2 seconds and occasionally 3 seconds or longer. Crufting a large
> number of w's into the dialpl
> However, outbound calls are hit or miss. Sometimes they work fine and
> other times we get a
"you must first dial a 1 or 0" message back from telco when dialing out
standard POTS lines.
>
>
> >>>Did you get this working yet?
> >>>
> >>>
> >>>
> >>>
> >>Yes, it d
> >In very very general terms, the delay is only seen when interfacing
> >with analog pstn lines. (Newer central office switches that support
> >isdn typically are not designed/engineered with this one-to-many
> >dtmf receiver arrangement.)
> >
> >
> This makes perfect sense now as the systems we
John Novack wrote:
...along with detection of stutter dial tone on analog lines.
This would be somewhat useful. When there is stutter for whatever
reason, outbound dialing must be delayed a couple seconds. Some times
my PSTN line would roll-over to the telco voicemail before * would
answer, so
Rich Adamson wrote:
However, outbound calls are hit or miss. Sometimes they work fine and
other times we get a "you must first dial a 1 or 0" message back from
telco when dialing out standard POTS lines.
Did you get this working yet?
Yes, it does seem to be working fine now by add
Rich Adamson wrote:
However, outbound calls are hit or miss. Sometimes they work fine and other times we get a "you must first dial a 1 or 0" message back from telco when dialing out standard POTS lines.
Did you get this working yet?
Yes, it does seem to be working fine now by addin
> >> However, outbound calls are hit or miss. Sometimes they work fine and
> >> other times we get a "you must first dial a 1 or 0" message back from
> >> telco when dialing out standard POTS lines.
> >
> >
> > Did you get this working yet?
> >
> >
> Yes, it does seem to be working fine now by ad
I wish the card (or Asterisk) waited for the dialtone before
dialing. Sometimes the phone company gives a dialtone within 1
second; other times it takes 2 seconds and occasionally 3 seconds or
longer. Crufting a large number of w's into the dialplan makes
Asterisk seem pokey, but less cruft means
Johnathan Corgan wrote:
Mike Clark wrote:
However, outbound calls are hit or miss. Sometimes they work fine and
other times we get a "you must first dial a 1 or 0" message back from
telco when dialing out standard POTS lines.
Did you get this working yet?
Yes, it does seem to be working fine no
Mike Clark wrote:
However, outbound calls are hit or miss. Sometimes they work fine and
other times we get a "you must first dial a 1 or 0" message back from
telco when dialing out standard POTS lines.
Did you get this working yet?
-Johnathan
___
Asteri
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Mike Clark
> Sent: Wednesday, May 18, 2005 4:53 PM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: [Asterisk-Users] Outbound dialing issue with FXO
&g
Mike Clark wrote:
We are installing a number of systems with 2 TDM04B cards. Have done all
the isolation to unique IRQs, etc. All inbound calls seem to work fine.
However, outbound calls are hit or miss. Sometimes they work fine and
other times we get a "you must first dial a 1 or 0" message bac
We are installing a number of systems with 2 TDM04B cards. Have done all
the isolation to unique IRQs, etc. All inbound calls seem to work fine.
However, outbound calls are hit or miss. Sometimes they work fine and
other times we get a "you must first dial a 1 or 0" message back from
telco when
I am new to asterisk and am hoping someone can point me in the right
direction, I have been working on this problem for some time with no
success. I have a TE410P connected to our PBX using a single T1 interface.
The PBX sends calls to * using the featd format, passing both ANI and DNIS
(works pe
hi there. i've got a question about outbound dialing.
here's my scenario:
1. i build a list of phone numbers from a database
2. when a call comes in, i begin dialing from the list
3. when an outbound call is answered, i connect the caller to that line.
so far, i'm able to do this with an agi scri
21 matches
Mail list logo
