asterisk users - Jun 2005 - AMP/A@H (asterisk at home) custom incoming routing

Folks,

First off, this is messy, and I hope someone will be kind enough to  
help me clean this up (the part added to extensions_additional.conf).  
You've been warned!

For those of your using AMP or A@H, there has been a lot of talk  
about how to route incoming calls to different places based on which  
trunk is ringing. The standard answer is that you can only do this by  
using DIDs, which is all fine and good, unless you are using a plain  
old copper line that doesn't support DID. Anyhow, I have figured out  
how to make a call that comes in on a specific ZAP channel ring at a  
specific extension (not that it was brain surgery). I'm not certain  
if it would be better to use the file extensions_custom.conf instead  
of extensions_additional.conf, does anyone know?

I have an A@H box with an unused TDM11P card in it at home in my  
basement. The A@H box normally handles incoming calls for my small  
business, but I wanted to plug my home phone line into the FXO port,  
and all of my phones into the FXS port (They're cordless, so no  
worries about ringer equivalence, etc.). That way I can route  
outgoing calls over VOIP, but my incoming calls will still ring my  
home phones. The hitch with A@H was that AMP doesn't allow you to  
differentiate between incoming calls from Broadvoice (or wherever)  
and incoming calls on the FXO port. I wanted incoming calls on my  
home line to ring to ring the extension associated with the FXS port  
on my TDM card. All other incoming calls should still follow whatever  
I set up in AMP, since that is how I control where my incoming  
business calls go.

Here's what I did. I know that you aren't supposed to use the  
extension "_." but that is the only way I got it to work. Please let  
me know if there is a better way.

1.) Edit /etc/asterisk/zapata-channels.conf and change the context  
for your incoming port to something new. I used "tdm-in".
2.) Edit pico /etc/asterisk/extensions_additional.conf and add this  
at the bottom:

[tdm-in]
exten => _.,1,Goto(ext-local,200,1)    ;
3.) If you haven't already, add the ZAP channel as a trunk in AMP so  
you can make outgoing calls on this channel.

That's it,

Tom

You would be better using extensions_custom only because of the fact that
when you restart ampportal, it will overwrite extensions_additional with
what ever it has stored in the Database.


 

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Tom Rymes
Sent: Wednesday, 29 June 2005 2:47 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [Asterisk-Users] AMP/A@H (asterisk at home) custom incoming routing

Folks,

First off, this is messy, and I hope someone will be kind enough to help me
clean this up (the part added to extensions_additional.conf).  
You've been warned!

For those of your using AMP or A@H, there has been a lot of talk about how
to route incoming calls to different places based on which trunk is ringing.
The standard answer is that you can only do this by using DIDs, which is all
fine and good, unless you are using a plain old copper line that doesn't
support DID. Anyhow, I have figured out how to make a call that comes in on
a specific ZAP channel ring at a specific extension (not that it was brain
surgery). I'm not certain if it would be better to use the file
extensions_custom.conf instead of extensions_additional.conf, does anyone
know?

I have an A@H box with an unused TDM11P card in it at home in my basement.
The A@H box normally handles incoming calls for my small business, but I
wanted to plug my home phone line into the FXO port, and all of my phones
into the FXS port (They're cordless, so no worries about ringer equivalence,
etc.). That way I can route outgoing calls over VOIP, but my incoming calls
will still ring my home phones. The hitch with A@H was that AMP doesn't
allow you to differentiate between incoming calls from Broadvoice (or
wherever) and incoming calls on the FXO port. I wanted incoming calls on my
home line to ring to ring the extension associated with the FXS port on my
TDM card. All other incoming calls should still follow whatever I set up in
AMP, since that is how I control where my incoming business calls go.

Here's what I did. I know that you aren't supposed to use the extension
"_."
but that is the only way I got it to work. Please let me know if there is a
better way.

1.) Edit /etc/asterisk/zapata-channels.conf and change the context for your
incoming port to something new. I used "tdm-in".
2.) Edit pico /etc/asterisk/extensions_additional.conf and add this at the
bottom:

[tdm-in]
exten => _.,1,Goto(ext-local,200,1)    ;
3.) If you haven't already, add the ZAP channel as a trunk in AMP so you can
make outgoing calls on this channel.

That's it,

Tom
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.6/33 - Release Date: 28/06/2005
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.6/33 - Release Date: 28/06/2005

A few things to followup on my earlier post:

1.) Definitely put the [tdm-in] context in the file "/etc/asterisk/ 
extensions_custom.conf". That way your changes will not get overwritten.
2.) I am still unable to make call waiting on the incoming ZAP line  
work, b/c I have not thought up a good way to make this happen.  
hasn't anyone done this before?
3.) When setting up the ZAP trunk, I found it usefull to put "w" in  
the dial prefix field to force the system to wait for the dial tone.  
If I didn't do that, I could not call out on the ZAP Channel.

Tom

On Jun 29, 2005, at 12:46 AM, Tom Rymes wrote:
> Folks,
>
> First off, this is messy, and I hope someone will be kind enough to  
> help me clean this up (the part added to  
> extensions_additional.conf). You've been warned!
>
> For those of your using AMP or A@H, there has been a lot of talk  
> about how to route incoming calls to different places based on  
> which trunk is ringing. The standard answer is that you can only do  
> this by using DIDs, which is all fine and good, unless you are  
> using a plain old copper line that doesn't support DID. Anyhow, I  
> have figured out how to make a call that comes in on a specific ZAP  
> channel ring at a specific extension (not that it was brain  
> surgery). I'm not certain if it would be better to use the file  
> extensions_custom.conf instead of extensions_additional.conf, does  
> anyone know?
[snip]