quote who=beonice
Robert, thank you very much for that informative
write-up. Of course, I now have more questions. The
first is really basic. I thought extension meant
something the caller dials _after_ reaching asterisk.
How come incoming DIDs have to be handled as if they
are extensions?
Thanks, Robert. Yes, I _finally_ figured out why I
need multiple extension contexts. I'm now one happy
camper.
Thanks again,
Maya
--- Robert Hajime Lanning
[EMAIL PROTECTED] wrote:
quote who=beonice
Robert, thank you very much for that informative
write-up. Of course, I now have more
quote who=beonice
If I understood the little documentation I found on
's', it's supposed to be a catchall for ALL incoming
calls. That's why I assumed it would catch a DID as
well. If that's not the case, it really should be
updated in some meta-doc somewhere. :)
s is the start extension if
On Thu, Feb 17, 2005 at 06:32:52PM -0800, beonice wrote:
To answer my own question, at least partially, here is
a quote from the Asterisk Configuration chapter in
Paul Mahler's book VoIP Telephony With Asterisk:
Table 1. Reserved Extension Names
beonice wrote:
But we still have the issue of what happens when calls
come in from DIDs in other countries. How are our
colleagues in Europe and Asia handling this? Are you
all creating handlers that special-case your incoming
DID pattern and then map it to the handler for 's' as
Robert
Robert, thank you very much for that informative
write-up. Of course, I now have more questions. The
first is really basic. I thought extension meant
something the caller dials _after_ reaching asterisk.
How come incoming DIDs have to be handled as if they
are extensions?
More questions follow:
--- Martijn van Oosterhout [EMAIL PROTECTED]
wrote:
--- snipped my quote of what 's' is --
I guess it
implies that calls coming from DIDs have digits
associated with them.
Correct. On ISDN lines, E1, T1 and related digital
protocols, details
such as CallerID, Dialled Number, CLI
Andrew, thanks for the explanation ... see more
questions below. :)
--- Andrew Thompson [EMAIL PROTECTED] wrote:
beonice wrote:
--- snipped some ---
I guess the fundamental question is why is a call
coming in from a DID any different? And, of
course,
does a call coming in
Look at an EXTENSIONS RELOAD and make sure the include is being parsed
-- and not throwing file not found errors. I broke my include
functionality last week by reMAKEing and not paying attention to a
known bug in the #INCLUDE function that existed in non-HEAD versions.
/rg
On Feb 16, 2005, at
Robert,
Thanks for the suggestion. I also came to the same
conclusion, but Asterisk wasn't showing any errors.
Then I decided to go back to basics, so I backed up my
extensions.conf and used the sample one provided by
voicepulse voila, it worked.
The culprit? Me. I'd commented out the
beonice wrote:
The culprit? Me. I'd commented out the line:
exten = _NXXNXX,1,Background(welcome) ;
which is apparently a critical one. I was under the
impression that
exten = s,1,Answer
Will s be traveled if a call arrives at it with a DID?
The pattern you have above matches any US did that
On Feb 17, 2005, at 4:32 PM, Andrew Thompson wrote:
beonice wrote:
The culprit? Me. I'd commented out the line:
exten = _NXXNXX,1,Background(welcome) ;
which is apparently a critical one. I was under the
impression that exten = s,1,Answer
Will s be traveled if a call arrives at it with a DID?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robert Goodyear
Sent: Thursday, February 17, 2005 8:36 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Anyone having trouble with
VoicePulse Connect
--- Andrew Thompson [EMAIL PROTECTED] wrote:
beonice wrote:
The culprit? Me. I'd commented out the line:
exten = _NXXNXX,1,Background(welcome) ;
which is apparently a critical one. I was under
the
impression that
exten = s,1,Answer
Will s be traveled if a call arrives at
Robert Webb wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Robert Goodyear
Sent: Thursday, February 17, 2005 8:36 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] Anyone having trouble
-Users] Anyone having
trouble with
VoicePulse Connect?
On Feb 17, 2005, at 4:32 PM, Andrew Thompson
wrote:
beonice wrote:
The culprit? Me. I'd commented out the line:
exten = _NXXNXX,1,Background(welcome) ;
which is apparently a
critical one. I was under the impression
--- beonice [EMAIL PROTECTED] wrote:
... snipped ... this thread is getting long ...
Hmm. I guess that would be one way to do it.
But we still have the issue of what happens when
calls
come in from DIDs in other countries. How are our
colleagues in Europe and Asia handling this?
beonice wrote:
If I understood the little documentation I found on
's', it's supposed to be a catchall for ALL incoming
calls. That's why I assumed it would catch a DID as
well. If that's not the case, it really should be
updated in some meta-doc somewhere. :)
No. 's' is for when Asterisk does
[general]
register = dqo75qMa71:[EMAIL PROTECTED]
Now you should change your password before you find that your phone bill
has drastically increased recently...
Regards,
Adam
--
--
Adam Goryachev
Website Managers
Ph: +61 2 8304 [EMAIL PROTECTED]
Fax: +61 2
I've been using my voicepulse connect number for over
a month now, but today it simply won't connect. My
partner and I each have a number, both are mapped in
my iax.conf and extensions.conf files. This has been
working fine.
Today, either number gives this message:
Feb 16 21:53:14 NOTICE[4330]:
I was doing some testing and it seems to be related to
my extensions.conf.
I have a #include extensions_from_mysql.conf that
was working fine yesterday:
[voicepulse_connect_context2]
exten = s,1,Answer
exten = s,2,NoOp,${CALLERID}
#include extensions_from_mysql.conf
and
21 matches
Mail list logo
