Thanks for the reply!
Generally that's what I do, script local area codes and prefixes so that
dialing 1 is necessary only for long distance calls. The problem here is
that there are over 1500 area codes and prefixes (DC area) that are required
by the carrier to not be dialed with a 1 (ie, local
1500 prefixes is not a big number. You can use a little script for it (less
than 50 lines).
With a script connecting to a DB server and looking for the prefix, is a
good solution. This way you don't need to force the user to dial the the
leading 1 (or not to do it), you just look on the DB server
On Thu, Oct 30, 2008 at 1:40 PM, Juan Rodríguez [EMAIL PROTECTED] wrote:
With a script connecting to a DB server and looking for the prefix, is a
good solution. This way you don't need to force the user to dial the the
leading 1 (or not to do it), you just look on the DB server and if it does
Thanks for the reply!
I've played around with R to solve this (probably should have mentioned
that), however I wasn't able to make it work. The message is still played
(this message is from the provider). It will move to the next line in the
dialplan, but as soon as users hear the message they
From zapata.conf.sample:
; PRI Out of band indications.
; Enable this to report Busy and Congestion on a PRI using out-of-band
; notification. Inband indication, as used by Asterisk doesn't seem to work
; with all telcos.
;
; outofband: Signal Busy/Congestion out of band with
I left something out on that last message, sorry.
With r, not R, it will mask the message with ringing. I could then fail it
over to another dial out, however from testing I've found that my users
expect something to happen within 30 seconds (voicemail, pickup, etc.) The
worse-case scenario would
Arka:
I thought you would reroute the call with (or without) the leading one, so,
just Dial again.
This will work and your users wont notice a BIG difference if the call is
answered. The problem is if the call is not answer, because if you have a
busy number, then your users will get something
Hi,
I've ran into an issue with a PRI provider in a major metropolitan area that
I haven't needed to deal with before and I was hoping someone might have
some insight on how to handle this within the Asterisk dialplan.
At this location users can't always tell if a number is long distance or not
Some additional information.
I played with ${DIALEDSTATUS} in place of ${HANGUPCAUSE} and got an unusual
result:
[Oct 28 16:50:54] WARNING[17503]: chan_sip.c:1950 retrans_pkt: Maximum
retries exceeded on transmission
NzJlOWI0NjI5NTMwMmEwZTExYzZiZTM5YWY4MDk0MzA. for seqno 2 (Critical Response)
Try using a R or r on the Dial command, the R option is better for you in my
opinion.
i.e Dial(Zap/G2/1${EXTEN},30,R) or Dial(Zap/G2/1${EXTEN}|30|R)
The R option is going to generate a ring tone when the callee indicates
ringing and is going wait for an Answer. As Progress is just for early
10 matches
Mail list logo
