On Tue, Jun 20, 2006 at 11:29:58AM -0400, Lee Marzke wrote:
>
> If you use an Autoattendant you can add addtional custom code
> ( This was written for A@H 2.7)
>
> In extensions_custom.conf
>
> [aa_2-custom] # Auto-Attendant #2
> exten => s,10,Background(pls-wait-connect-call)
> exten => s,n,Wait(1)
> exten => s,n,Background(for-quality-purposes)
> exten => s,n,Background(this-call-may-be-monitored-or-recorded)
> exten => s,n,Setvar(DIAL_OPTIONS=tm) # Provide music instead of
> ringback
> exten => s,n,Setvar(_ALERT_INFO=Classic-1) # For Sipura-841 phones
> exten => s,n,Goto(ext-queues,280,5)
> ;exten => s,n,Goto(ext-group,1,1)
>
> This sets a special ring for SIP phones (Classic-1)
> My autoattendant for other lines sets a different ring.
>
> Alternatively, if you use inbound queues, you can set the queue
> "pre-announcment". This isn't quite as good, but the system will
> announce, for instance the "Company Name" to you when you pick
> up the phone - before connecting the caller. If you answer many
> different lines - this may actually be easier to use than remembering
> the type of ring - and it works on any type of phone.
>
> I'm actually combining both techniques - as you can see in the above
> code. The AutoAttendent branches to a queue. So I get distinctive
> ringing on the Sipura phones, and queue announcement for my
> business lines everywhere.
The problem is that the distRing goes on the channel definition, so
we're talking about modifying at the channel level, which is all
generated in the AGI script. I think it'll take a bit of work to modify
it there, as I will have to grok all that the AGI script does.
My best idea so far is to create separate ZAP definitions in the configs
(maybe separating the users and devices), each with a different "dial"
command.
While each extension/device has a "mailbox" setting, I think that is for MWI,
not for what VM is used on no answer. So, to have those separate
"extensions" tie to the same voicemail, I would have to manually symlink
the directories (which *would* work, it's just not The freePBX Way).
This theory suffers 2 drawbacks:
1. It is a kludge, and the computer scientist in me dislikes that.
2. It requires all IVRs to disallow direct extension dialing in their
configs and manually put in all extensions as IVR options...
> Ed W wrote:
> >I do the same as you on my hand-crafted asterisk box, and not having
> >this kind of feature is rather holding me back from trying FreePBX on my
> >main box.
> >
> >Interested to hear what you come up with
> >
> >Ed W
> >
> >
> >Michael George wrote:
> >
> >>I am writing an article for The Linux Journal about Trixbox as a home
> >>phone system for VoIP and POTS service.
> >>
> >>One thing I am doing now with my hand-crafted * 1.0.x system is that I
> >>have distinctive ring on my office phone. Normal ring if the call came
> >>from the Zap trunk (the normal POTS phone line), /r1 if the call came
> >>from an internal extension, /r2 if the call came from my office VoIP
> >>trunk and was from another office extension, and /r3 if the call came
> >>from my office VoIP trunk and was from an outside caller.
> >>
> >>On a new Trixbox system, I can emulate the /r2 and /r3 conditions by
> >>putting incoming calls from that VoIP trunk into a special context that
> >>will only ring my device and will append the /rX to the channel. A bit
> >>of a kludge, but it would work for my purposes.
> >>
> >>However, I have not yet figured out a way to put /r1 on the calls
> >>from other house extensions... I want voicemail and extension numbering
> >>and all that to remain the same, I just want the ring different.
> >>
> >>I haven't come up with a "freePBX way" to do it as it is now. I might
> >>be able to finesse it with the "devicesandusers" settings, I'll have to
> >>think about that...
> >>
> >>I also thought about modifying freePBX so that on a Zap channel one can
> >>define some CID reg.exps that are tied to /rX for 1 <= X <= 4 so that
> >>when a call comes to that channel, if it matches a regexp, that "/rX" is
> >>appended to the channel name. I've not yet looked into the freePBX
> >>source, so this would be a bit more involved and I wouldn't have that
> >>done by the deadline for my article...
> >>
> >>If anyone has achieved this Zap-channel distinctive ring with a standard
> >>freePBX system, I would appreciate the advice.
> >>
> >>If not, and I get it figured out (or modify freePBX to accommodate it),
> >>I will let the list know.
> >>
> >>Thanks!
> >>
> >>
> >>
> >
> >
> >
> >_______________________________________________
> >Amportal-users mailing list
> >Amportal-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> >https://lists.sourceforge.net/lists/listinfo/amportal-users
> >
>
> begin:vcard
> fn:Lee Marzke
> n:Marzke;Lee
> email;internet:lee-NUm6duiwBxSsTnJN9+BGXg@xxxxxxxxxxxxxxxx
> tel;work:800 393 5217
> tel;home:610 454 9354
> version:2.1
> end:vcard
>
> _______________________________________________
> Amportal-users mailing list
> Amportal-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/amportal-users
--
-M
There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.
|
