Summary:ASTERISK-16128: Poor man's find-me/follow-me dialplan implementation
Reporter:Philip Prindeville (pprindeville)Labels:
Date Opened:2010-05-21 19:12:38Date Closed:2011-06-07 14:10:04
Versions:Frequency of
Description:Yes, you can use the app_followme, but sometimes you want to be able to have finer levels of control over things yourself via the dialplan.

Here's an example of a simple FM/FM using the Local/ channel:

; list of extensions to dial for Philip
exten => 111,1,NoOp(Exten: ${EXTEN})
same => n,Gosub(${EXTEN},stdexten(${PHILIP},redfish))
same => n,Goto(s,exten)
exten => _NXXXXXXXXX,1,NoOp(Follow-me: ${EXTEN} From: ${CALLERID(num)})
same => n,Wait(${GLOBAL(FM_DELAY)})
same => n,Dial(${GLOBAL(TRUNK)}/${EXTEN})

Comments:By: Paul Belanger (pabelanger) 2010-05-23 09:59:21

Patch?  Where do you see this going into the source? What about just making this a blog post?

By: Philip Prindeville (pprindeville) 2010-05-23 13:43:44

It would eventually be a patch against trunk, but if it takes a while to get approved there's no point in creating a patch that's just going to get out of phase with SVN anyway.

By: Leif Madsen (lmadsen) 2010-05-25 13:07:32

This really feels like something better implemented as a blog post or perhaps a recipe here:  http://etel.wiki.oreilly.com/wiki/index.php/Main_Page

I don't want to see the extensions.conf file getting made into a "how to do everything you could do in dialplan" file. Examples should be showing functionality of how to use a specific feature or application, but not how to build prototypes of functionality.

If you want to do that, then you could build a TeX document that gets used by the PDF and text file generation from doc/tex/

By: Philip Prindeville (pprindeville) 2010-05-25 22:06:41

Well, the problem with "blog posts" is they quickly get out of phase with the current release.  If you go on voip-info.org for instance, the SLA examples are for Asterisk 1.2.

This is exactly what I'm trying to avoid.

What about creating a subdirectory configs/extensions/ and then extensions.conf.sample could include fragmentized examples from there?

As for "showing functionality", that's exactly what I was trying to show: how to use the Local/ channel.  I figured the example might as well do something useful.

By: Leif Madsen (lmadsen) 2010-05-27 10:48:58

I don't know, I'm not convinced. The extensions.conf.sample file is already hard to parse. I think this would be best as a document in doc/tex/ as I've already mentioned.

By: Leif Madsen (lmadsen) 2010-05-27 10:49:20

In fact there is already a document dealing with Local channels, so you could just expand on that.

By: Philip Prindeville (pprindeville) 2010-05-27 14:38:35

And indeed, there's a tex document on SLA... and it's inaccurate, incomplete, and out-of-date.  This is the fate that I'm trying to avoid.

My experience tells me that the examples are better up kept than the documentation.

By: Leif Madsen (lmadsen) 2010-06-08 09:29:08

I disagree. The document may be all of those things, but that isn't because of the type of document or where it is -- it's because no one has gone through and updated the document or submitted changes to it.

Documentation in the TeX directory exists and is being updated by many people in different areas, but that doesn't mean all areas are updated equally.

I pointed to the Local channel documentation as well, not the SLA document, which is where I believe this should go. It was recently updated -- by me and Kobaz.

By: Leif Madsen (lmadsen) 2010-06-08 09:30:05

BTW: I'm leaving this in the Feedback state for now. This documentation should go into one of the appropriate TeX documents, so if you want to update one of the documents and place the information there, you are welcome to. If you don't wish to do that, then I will go ahead and close this issue.

By: Philip Prindeville (pprindeville) 2010-06-13 16:20:07

Ok, leave it open.  I'll patch the Local documentation.

By: Paul Belanger (pabelanger) 2010-06-25 08:59:05

Suspending for now, we can re-open once patch is ready.
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines