[Asterisk-Users] AMP/A@H (asterisk at home) custom incoming routing

[Tom Rymes]

Robert,

I think you jay be wrong on this. From the /etc/asterisk/extensions.conf
file included with A at H:

; Customizations to this dialplan should be made in
extensions_custom.conf ; See extensions_custom.conf.sample for an
example #include extensions_custom.conf

Tom

> -----Original Message-----
> From: Robert Webb [mailto:rwebb at ropeguru.com] On Behalf Of Robert Webb
> Sent: Saturday, July 02, 2005 11:27 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion; Tom Rymes
> Subject: RE: [Asterisk-Users] AMP/A at H (asterisk at home) 
> custom incoming routing
> 
> 
> 
> 
> > -----Original Message-----
> > From: asterisk-users-bounces at lists.digium.com 
> [mailto:asterisk-users- 
> > bounces at lists.digium.com] On Behalf Of Tom Rymes
> > Sent: Friday, July 01, 2005 11:27 PM
> > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > Subject: Re: [Asterisk-Users] AMP/A at H (asterisk at home) custom
> incoming
> > routing
> > 
> > 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
> > 
> 
> Tom,
> 
>   Actually, it is the extensions_custom.conf that DOES get 
> overwritten. Unles things have completely changed since 
> version 1.0. You should be using the extensions.conf to place 
> all your permamnant changes. The _custom was there to tell 
> you that those are the custom settings for *@Home.
> 
> 
> 
>