Tom Rymes wrote:
On Nov 1, 2005, at 11:54 AM, Kevin Hanson wrote:
<snip>
You do not deal with [EMAIL PROTECTED] limitations, but rather the AMP system. I
do not
find AMP limiting, and if you look at the configuration files there
is a way
to override every customization installed by AMP.
There are two things that I cannot find a way to customize via the
xxxx_custom.conf files:
1. Inbound routing based on analog trunk: If I want to route calls
coming in on zap/1 differently than zap/2 I have to modify
extensions.conf directly (fake AMP out into thinking DID is available).
A google search for "AMP Custom Incoming" turns up this post I made
to the Asterisk-users list a while back about just this:
<http://lists.digium.com/pipermail/asterisk-users/2005-June/114246.html>
read the whole thread, b/c I corrected an error or two in my original
post. HTH
Based on more searching this is what I ended up doing. Works quite well
and only zapata-auto.conf is at risk of being overwritten, but only by
genzatelconf (which I don't really use anyway):
zapata-auto.conf:
context=to-did1
group=1
channel => 1-2
context=to-did2
group=2
channel => 3-4
extensions_custom.conf:
[to-did1]
exten => s,1,Goto(from-pstn,YOURDID1,1)
[to-did2]
exten => s,1,Goto(from-pstn,YOURDID2,1)
Then just use 'Inbound Routing' to route YOURDID1 and YOURDID2. Works like a
champ. No mucking w/ files AMP 'owns'.
Cheers,
Kevin
_______________________________________________
Asterisk-Biz mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-biz
