IRC log for #asterisk on 20180515

00:21.56*** join/#asterisk infobot (ibot@rikers.org)
00:21.56*** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.21.0 (2018/05/01), Standard: 15.4.0 (2018/05/01); DAHDI: DAHDI-linux 2.11.1 (2016/03/01), DAHDI-tools 2.11.1 (2016/03/01); libpri 1.6.0 (2017/01/27) -=- Wiki: wiki.asterisk.org -=- Code of Conduct: bit.ly/1hH6P22 -=- Logs: bit.ly/1s4AKKu
00:34.55*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)
00:54.40*** join/#asterisk Chotizei (chotaire@unaffiliated/chotaire)
00:58.12*** join/#asterisk Chotaire (chotaire@unaffiliated/chotaire)
01:33.41*** join/#asterisk Oatmeal (~Suzeanne@rrcs-74-62-242-19.west.biz.rr.com)
02:13.50*** join/#asterisk sawgood (~sawgood@unaffiliated/sawgood)
03:07.09*** join/#asterisk jeffspeff (~me@209.141.208.197)
03:30.21*** join/#asterisk gringo (~gringo@unaffiliated/gringo)
04:07.36*** join/#asterisk Maliuta_ (maliutamat@gateway/shell/matrix.org/x-dgsrqkveflpzwecb)
04:29.34*** join/#asterisk koss (~koss@koss.downlink.org)
04:50.44*** join/#asterisk CatCow97 (~mine9@c-24-22-38-85.hsd1.or.comcast.net)
04:55.45*** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl)
04:58.08*** join/#asterisk ttyX (~ttyX@121.242.156.1)
04:58.16*** part/#asterisk ttyX (~ttyX@121.242.156.1)
05:13.05*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)
05:54.59*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
05:54.59*** mode/#asterisk [+o cresl1n] by ChanServ
06:03.49*** join/#asterisk jeffspeff (~me@209.141.208.197)
06:06.02*** join/#asterisk miralin (~Thunderbi@91.237.94.10)
06:27.45*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
06:27.45*** mode/#asterisk [+o cresl1n] by ChanServ
06:38.30*** join/#asterisk jkroon (~jkroon@uls-154-73-35-201.wall.uls.co.za)
07:02.26*** join/#asterisk sebastienthiry (~Thunderbi@109.134.212.7)
07:05.20*** join/#asterisk hehol (~hehol@gatekeeper.loca.net)
07:06.43*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
07:06.43*** mode/#asterisk [+o cresl1n] by ChanServ
07:22.19*** join/#asterisk waldo323_ (~waldo323@12.239.4.3)
07:47.10*** join/#asterisk Chainsaw (~chainsaw@gentoo/developer/chainsaw)
08:00.51*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
08:00.51*** mode/#asterisk [+o cresl1n] by ChanServ
08:25.32*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
08:25.32*** mode/#asterisk [+o cresl1n] by ChanServ
08:39.44*** join/#asterisk jamesaxl (~James_Axl@41.249.34.137)
08:45.10*** join/#asterisk defsdoor (~Andrew@cpc120600-sutt6-2-0-cust232.19-1.cable.virginm.net)
08:51.52*** join/#asterisk Hamagid (~Mutter@net-188-152-239-192.cust.vodafonedsl.it)
09:21.10*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
09:21.10*** mode/#asterisk [+o cresl1n] by ChanServ
09:31.49*** join/#asterisk war9407 (war@pool-70-106-236-148.clppva.fios.verizon.net)
09:51.02*** join/#asterisk evilman_work (~evilman@87.244.6.228)
10:14.45*** join/#asterisk Ast001 (~uros@p5DCD6D28.dip0.t-ipconnect.de)
10:15.51Ast001Hi is there a way to force asterisk to write maxforward in sip invite message ? I uncommented maxforward=70 in sip.conf but it seems there is no maxforward line in sip invite and some softphones does not like it and hangup call after 30 seconds (linphone) ?
10:17.10*** join/#asterisk Iamnacho (~Iamnacho@ip68-103-241-71.ks.ok.cox.net)
10:21.57Ast001https://issues.asterisk.org/jira/browse/ASTERISK-24807 offers solution for pjsip, but what with ordinary sip.conf ?
10:36.19SamotAst001: There's no further development on Chan_SIP
10:36.37SamotOutside of community submitted patches/updates
10:44.40Ast001Can I force it somehow like this SipAddHeader(Max-Forwards: 70) ?
10:47.13SamotWhy? It gets added
10:50.15SamotMax-Forwards is a required header.
10:50.21SamotIt defaults/starts at 70
11:00.24*** join/#asterisk lankanmon (~LKNnet@CPE64777d632383-CM64777d632380.cpe.net.cable.rogers.com)
11:10.25*** join/#asterisk CatCow97 (~mine9@c-24-22-38-85.hsd1.or.comcast.net)
11:10.39Ast001It does not show in sip set debug on, and linphone says bad request because of that and hangup call after 30 seconds or so.
11:11.00Ast001with SipAddHeader it shows and is visible in sip debug
11:13.24SamotWell then something isn't right. I see it added in all the headers I'm sending out
11:14.16SamotIn the OPTIONS, NOTIFYs, all of it.
11:15.21*** join/#asterisk forgotmynick (uid24625@gateway/web/irccloud.com/x-mvhonzabpbynkwwk)
11:40.42Ast001Which version of Asterisk do you use ?
11:50.06Ast001I see now in Invites Max-Forwards, but yesterday on linphone to linphone call over Asterisk I didn't see.  I will recheck.
11:54.43*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
11:54.43*** mode/#asterisk [+o cresl1n] by ChanServ
12:04.53*** join/#asterisk kunwon1 (~kunwon1@unaffiliated/kunwon1)
12:09.34tomaluca95Hi, i would like to get asterisk data about sip peers in a python script to do some monitoring, there is a way to have something like json/yaml/xml peers information?  I'm using debian 9
12:10.01SamotARI.
12:10.48fileARI isn't really meant for that, such information isn't available there
12:11.08fileyou can get it in a general sense using the endpoint route
12:11.11filebut nothing in great detail
12:13.17*** join/#asterisk nighty- (~nighty@s229123.ppp.asahi-net.or.jp)
12:13.39*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:13.39*** mode/#asterisk [+o cresl1n] by ChanServ
12:15.36SamotTrue.
12:15.49SamotThen I guess it's AMI and parsing the data.
12:17.49tomaluca95Thanks, I'll do some search about it
12:19.15*** join/#asterisk Sepultura (~Sepultura@unaffiliated/sepultura)
12:23.52*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:23.52*** mode/#asterisk [+o cresl1n] by ChanServ
12:24.42*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:24.42*** mode/#asterisk [+o cresl1n] by ChanServ
12:25.25*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:25.25*** mode/#asterisk [+o cresl1n] by ChanServ
12:26.14*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:26.14*** mode/#asterisk [+o cresl1n] by ChanServ
12:27.00*** join/#asterisk cresl1n (~Adium@asterisk/libpri-and-libss7-expert/Cresl1n)
12:27.00*** mode/#asterisk [+o cresl1n] by ChanServ
12:28.31*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)
12:37.52*** join/#asterisk AndyCap (~aoy@pdpc/supporter/sustaining/AndyCap)
12:46.02*** join/#asterisk [TK]D-Fender (~joe@216.191.106.165)
12:47.16*** join/#asterisk cresl1n (uid299068@asterisk/libpri-and-libss7-expert/Cresl1n)
12:47.16*** mode/#asterisk [+o cresl1n] by ChanServ
12:48.41tomaluca95AMI is the solution, thanks
12:51.08*** join/#asterisk sekil (~sekil@nat-73.net011.net)
12:55.10*** join/#asterisk brad_mssw (~brad@66.129.88.50)
12:56.53*** join/#asterisk jetlag (~jetlag@c-71-226-222-56.hsd1.nj.comcast.net)
13:01.53*** join/#asterisk pawiecki (~pawiecki@89.238.53.32)
13:44.08*** join/#asterisk jetlag (~jetlag@c-71-226-222-56.hsd1.nj.comcast.net)
13:59.01*** join/#asterisk kharwell (kharwell@nat/digium/x-ejzagrpusbzllfno)
13:59.01*** mode/#asterisk [+o kharwell] by ChanServ
14:45.50*** join/#asterisk bford (uid283514@gateway/web/irccloud.com/x-bxyucwdknpsddwlr)
14:45.50*** mode/#asterisk [+o bford] by ChanServ
15:05.16*** join/#asterisk TheGoodGuy (~TGGG@mail.thegoodguysgroup.ca)
15:13.57*** join/#asterisk Eloy (~Eloy@89.101.24.185)
15:18.08*** join/#asterisk Givemelove (d80e0f82@gateway/web/freenode/ip.216.14.15.130)
15:18.25GivemeloveHey @all, I have some issues with dahdi on a new box.
15:19.06GivemeloveI've had a Digium T1 card TE110p for years. Our system (built on Asterisk 1.6) crashed yesterday and we had to rebuild from scratch
15:19.35GivemeloveIn an effort to save time, I used Ubuntu's packages, which got me up and running pretty quickly, the configuration files being pretty similar still
15:20.35Givemelovethe issue I have with dahdi is that dahdi_tool doesn't list the card anymore. If I do dahdi_hardware, I do see the card being listed (pci:0000:09:04.0     wcte11xp+    e159:0001 Digium Wildcard TE110P T1/E1 Board) and lsmod shows that the wcte11xp module is loaded yet not in use (wcte11xp               32768  0)
15:20.52GivemeloveAnyone has a pointer for me to get it up and running again?
15:21.59igcewielingGivemelove: sounds like your kernel was upgraded without rebuilding DAHDI.
15:22.43Givemelove@icewiegling shucks. I had issues compiling dahdi from source so I went with the apt-get method
15:23.10Givemelovewould that still be the case if the module loads with modprobe?
15:25.58*** join/#asterisk Worldexe (~Worldexe@95-107-33-134.dsl.orel.ru)
15:26.50cresl1nyou might look at the dmesg log after you load the wcte11xp module
15:26.56cresl1nto see if it found the card
15:27.13SamotIt's an EOL card.
15:27.29SamotIs it even able to run with current DAHDI tools?
15:27.36cresl1nnot sure
15:27.49cresl1nbut if you have the wcte11xp driver, it should find it
15:27.55cresl1nthat's what I would think at least
15:29.31SamotWell at this point, it's a 10+ year old card.
15:29.44GivemeloveI agree it's a very old card. I believe we got it in 2007
15:29.47SamotI'd say you got your money out of it and would get a current and supported card.
15:29.51Givemelovethe module loads apparently [   18.026809] wcte11xp 0000:09:04.0: PCI IRQ 106 -> rerouted to legacy IRQ 18 [   18.027736] FALC version: 00000005 [   18.027776] TE110P: Setting up global serial parameters for T1 FALC V2.2 [   18.027825] TE110P: Successfully initialized serial bus for card [   18.027899] Found a Wildcard: Digium Wildcard TE110P T1/E1
15:32.58cresl1nlooks good
15:33.05cresl1ndid you setup your /etc/dahdi/system.conf for it?
15:33.11cresl1nor use dahdi_genconf?
15:33.48GivemeloveI did, says "Empty configuration -- no spans"
15:34.29GivemeloveI had my old system.conf, but I'm given to understand genconf overrides it, right?
15:34.39cresl1nyeah, probably
15:34.53cresl1nthen run dahdi_cfg
15:35.25Givemelovetried it: Timeout waiting for all spans to be assigned. DAHDI_SPANCONFIG failed on span 1: No such device or address (6)
15:35.53Givemelovewhen I do dahdi_genconf; dahdi_cfg, I only get this: Timeout waiting for all spans to be assigned.
15:36.38cresl1nwhat does your /etc/dahdi/system.conf look like?
15:36.45Givemelovecould it be that the telco deactivated the T1? I'd think that this is independent of it
15:36.53cresl1nalso, if you cat /proc/dahdi/1, what's the out put
15:37.00*** join/#asterisk tpdmoore (4b96ddc7@gateway/web/freenode/ip.75.150.221.199)
15:37.01Givemelovewhen I run dahdi_genconf, I only have loadzone= us defaultzone= us
15:37.02cresl1nNo, I think this is separate
15:37.08cresl1nAhhhhh
15:37.12cresl1ndo you have your old system.conf?
15:37.39GivemeloveIf I load the conf I had in the past, I add span=1,1,0,esf,b8zs dchan=24 bchan=1-23
15:37.54Givemelovewith newlines, of course
15:38.26Givemelove@creslin I don't have /proc/dahdi/1
15:38.52GivemeloveI'm putting the old system.conf and rebooting the box
15:39.10cresl1nthat's not good
15:39.22cresl1n(the lack of /proc/dahdi/1)
15:39.28GivemeloveI agree
15:39.50GivemeloveI'm assuming it should detect the interface regardless of the T1 line status
15:40.04cresl1nyep
15:40.28Givemeloveoriginally it tried loading another module instead of wcte11xp
15:40.51Givemeloveit was throwing me a warning when I was running dahdi_hardware
15:41.02GivemeloveI blacklisted that module and the pseudo dahdi interface
15:41.09Givemeloveshall I keep the pseudo interface?
15:42.09cresl1nHow did you blacklist the pseudo interface?
15:42.14cresl1nI'd keep it for now
15:42.55Givemelove<PROTECTED>
15:43.05Givemelovethe module was named `netjet`
15:43.10cresl1nOhhhhhhh
15:43.22cresl1nok
15:43.24tpdmoorehi, i am using the ARI to set device states. When I restart asterisk, the device states have persisted. Where are those stored, and/or how can i reset them?
15:44.10tpdmoorei know that i will have to manage them within the ARI app, but during testing i'd like them to just clear out when i restart asterisk
15:44.16cresl1nI'd keep that module blacklisted
15:44.20igcewielingtpdmoore: that sort of thing is often saved in the AstDB.    The backend for AstDB on modern Asterisk versions in SQLite 3
15:44.47cresl1n+1
15:44.48igcewielingtry "database show" in the Asterisk CLI
15:45.07tpdmooreigcewieling: that's the ticket, tyvm
15:45.31igcewielingyw
15:46.41Givemelovefor some reason, I can't compile dahdi from source
15:47.08GivemeloveI must've been out of sysadmin for too long. I'm getting basic compilation errors that I can't figure out
15:47.10tpdmoore`database deltree StasisDeviceState` does exactly what i need, in case anyone else finds this useful
15:47.30GivemeloveI may try installing debian and try to compile everything from source
15:47.48tpdmooreGivemelove: have you installed whatever your platform's equivalent of 'build-essential' is?
15:48.36Givemelove@tpdmoore yeah, it is installed.
15:48.58*** join/#asterisk imcdona (~imcdona@2607:f0d8:20:1001:2424:45bd:9c99:58c8)
15:50.07GivemeloveI think I have another card
15:50.21Givemelovenot the same model, but the same age. I'll try that before going berserk
15:53.44*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
15:54.07SamotJust my two cents, why spend all this time trying to get EOL/unsupported cards that are 10+ years old?
15:58.43*** join/#asterisk jkroon (~jkroon@165.16.204.171)
15:59.18Givemelove@Samot I agree with you. It's a mgmt decision not to keep the system current
15:59.27GivemeloveI'm running on 8yr old hardware
15:59.38SamotThat's a poor decision.
15:59.51Givemeloveand sure enough, the entire RAID failed yesterday and since we're running on a legacy version of asterisk, it's not making things easy
15:59.53Givemeloveagree 100%
15:59.58Givemelovecan't do much about it
16:02.18cresl1nyou might try to replicate the version of Asterisk and DAHDI that you originally were running
16:02.49Givemelovei though about it, it's too much of a challenge
16:02.53igcewielingIf you have to start from scratch anyway, why not use FreePBX?
16:03.21Givemelovethe version of asterisk was 1.6, which is way unsupported
16:03.56igcewielingI meant a modern version.  Maybe even the FreePBx distro
16:04.02Givemelove@Icewieling I still have my asterisk configuration, which contains Dialplan etc. in there
16:05.25igcewielingit will be a lot of work regardless of what you do.
16:07.26craigifyGivemelove, what linux distro are you using?  I have some very specific instructions to get Asterisk 1.6 to compile on Ubuntu 16, which will also probably work on the Debian distro it was built on
16:07.31craigifythe big issue is the gcc version
16:08.26craigifyit won't compile with gcc that comes with it
16:11.05GivemeloveI'm on 18.04 LTS
16:11.11SamotWell hopefully management will have an attitude adjustment after this.
16:11.22Givemelovebut I'm tempted to start from scratch; either Debian or ubuntu
16:11.31Givemelove@Samot One can only dream
16:11.48SamotWell, the bill on this will be a nightmare.
16:12.02cresl1nigcewieling: first step is to get it working as it did before, second step is to upgrade, IMHO
16:12.41SamotThat's the problem though, isn't it?
16:12.56craigifyGivemelove, you are trying to compile asterisk 1.6 on 18 LTS, correct?
16:12.59Samot"Working as before" means an old OS, old versions of stuff that is 10 years old.
16:12.59Givemelove@Creslin Agreed, I can work on the dialplan on a dev system
16:13.06Givemeloveyes
16:14.06Givemelove1.6 on 18.04 LTS
16:14.06craigifyI am going to private message you something
16:14.21*** join/#asterisk masoudd (~masoudd@5.52.167.7)
16:21.11SamotI'd just drop ship a new card, build a new/current box, migrate.
16:21.58*** join/#asterisk dar123 (~dar@2600:1700:38d0:1470:dc60:8e29:5e84:69b7)
16:26.51cresl1nSamot: that's probably the easiest way
16:28.08masouddHello, I'm new to asterisk. I am writing a program that needs to place several calls through a trunk like this: 'originate sip/mytrunk/<phone number> application playback <sound-file>'. There is only one outgoing valid pstn line, and I have several calls to make. When I make several of these 'originate...' requests at the same time, only the first one rings and the rest seem like being discarded. How can I make it so that after the first call is
16:28.08masouddterminated the next one is dialed?
16:28.11SamotThe easiest, most cost/time effective and future proof way.
16:28.57Samotmasoudd: You have to wait for the first call to return a DIALSTATUS showing it's completed.
16:29.04[TK]D-Fendermasoudd, It's your job to queue these up yourself
16:29.26SamotIf you send 5 Originate commands, it's going to originate 5 calls.
16:29.32[TK]D-Fendermasoudd, so either monitor the progress of the ones you originate, or have that channel kick off the next as it is about to exit
16:30.05masouddIsn't there a queue like feature that I can use?
16:30.10SamotNo.
16:30.21SamotOriginate is Originate.
16:30.27SamotYou send the command, it executes.
16:31.07masouddI see. Thank you all
16:31.25SamotYou can basically send one call at a time.
16:32.40masouddRelated question: How can I monitor the state of a call? Where does it return the DIALSTATUS?
16:32.55SamotIn the dialplan.
16:33.00SamotWhen the call is completed.
16:33.08SamotIt will give you the status of that call.
16:33.21Samot~wiki
16:33.34Samothttp://wiki.asterisk.org
16:33.47masouddThank you again. I'll read the docs
16:33.53Samot^^ You really should learn the basics of how Asterisk works so you can understand how to write this program.
16:34.49masouddYes. I need to learn. That's what I'm trying to do.
16:40.01*** join/#asterisk kfife (~Miranda@home.chicagoventure.com)
16:41.05kfifeIs there a way to invoke a dynamic feature into an existing call using AMI?
16:42.55SamotMight be able to set it on the channel.
16:44.06[TK]D-Fenderkfife, as in?
16:45.05kfifeCurrently, calling party can invoke a feature by sending in-band *3.  This injects a tone, and sets a local channel variable
16:45.06*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
16:45.42kfifeI'd like to call this same but trigger it via AMI
16:46.04kfifeI'd like to invoke this same dynamic feature but trigger it via AMI
16:47.07kfifeMaybe this is the wrong approach.
16:49.04kfifeFor example if I PlayDTMF into the calling-party's channel that might invoke the same feature
16:49.14kfifeHowever I'd like to avoid the inband DTMF
16:59.59SamotWait, so all *3 does it set a channel variable?
17:00.38kfifeNo, but it also does that.
17:01.15SamotSo you want AMI to trigger that *3 for you?
17:01.39kfifepossibly, but I don't need (or want) the in-band DTMF
17:02.02kfifebecasue it causes a audible artifact in the call
17:02.22SamotOK so you don't want the the user to dial *3?
17:03.00kfifeUser can dial *3, but they are also looking at a Web UI that can send commands via AMI
17:03.34SamotDo you need to have the actual tone?
17:03.39kfifesuch as one that invokes the same dialplan code associated with the dynamic feature defined in features.conf, and in the channel
17:03.41kfifeno
17:03.46SamotOr do you need to just trigger stuff to happen?
17:03.48kfifeThe tone is just a way to invoke the feature.
17:04.08SamotSo then you have AMI trigger that context.
17:04.26SamotOr do whatever it is you need to do.
17:04.27kfifelike action:originate?
17:04.33SamotSure.
17:04.39SamotOr set channel variables.
17:04.40kfifeWouldn't that be a different scope?
17:04.49SamotWell AMI doesn't need to send *3
17:04.53SamotIt can just send commands
17:05.05SamotTo do what you want. Set a channel variable? Send that command.
17:05.22SamotCall on a Dialplan app, can do that
17:05.32SamotThere are numerous actions that can be done.
17:05.53kfifeI can certainly re-create all of the code in the dialplan via AMI, but then I have to maintain the one feature in two places.
17:06.03SamotOK
17:06.07SamotSo then you send DTMF
17:06.18kfifeSo therefore, it would be cleaner to invoke a dynamic feature via AMI if that's possible
17:06.40SamotBy "invoking" you mean "sending"
17:06.51SamotNot set a dynamic feature on the channel
17:06.56SamotBut use one that already exists.
17:07.13kfifeThat's correct.
17:07.16kfifeOne that already exists.
17:07.24SamotThat's not how I understood it.
17:07.28kfifeAh...
17:07.38SamotSo my suggestion of AMI was to set the dynamic feature on the channel.
17:07.49SamotSo  it could then be used, ie the *3.
17:08.09*** join/#asterisk ih8wndz (jwpierce3@srv001.trnkmstr.com)
17:08.19SamotAMI is an outside thing.
17:08.23SamotFrom the outside to Asterisk
17:08.31SamotDialplan is an inside thing. In the call.
17:08.49SamotSo yes, you would have to maintain two ways of doing this. Because you will have two ways of doing this.
17:10.04kfifeSeems like a missing feature to me.
17:10.12SamotNo.
17:10.29SamotLook, my users can trigger call forwarding via a feature code.
17:10.39SamotWhen they do that, they have to enter digits for that destination.
17:10.44SamotDialplan has to deal with that
17:10.52SamotOr they can use a web GUI that triggers AMI
17:11.16SamotWhich is just submitting the data to AstDB to be looked at in the dialplan.
17:11.41SamotThey both store the information in AstDB, however, how that information is collection and triggered to be stored is two different things.
17:11.52SamotOne is done "in-call" and one is done from the outside.
17:12.07SamotAMI is meant to take outside actions in inject them into Asterisk.
17:13.07kfifeBut not trigger a predefined 'inside' feature?  And that's not desirable why?
17:13.23SamotAMI doesn't execute dialplan like that
17:13.43kfifeAnd that's not desirable why?
17:13.59SamotWhat do you mean?
17:14.17kfifei.e. manager show command DynamicFeature
17:14.35*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
17:14.42*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)
17:14.47kfifethis would allow an outside event to trigger a predefined dynamic feature into a specific channel
17:15.07kfifeif within scope to that channel
17:15.16[TK]D-Fenderthat there does not
17:15.22kfifei.e. _myfeature or __myfeature
17:15.56kfifeSorry.  Typo.
17:16.36kfife_DYNAMIC_FEATURES=myfeature or __DYNAMIC_FEATURES=myfeature
17:16.40SamotYes.
17:17.02SamotA Dynamic Feature lets you _map_ a * code to a function or application in Asterisk.
17:17.12SamotAMI lets you call on those functions or applications directly
17:17.19SamotNo need to map digits to it.
17:18.51kfifeBy that logic, there's no need for more than one turing-complete language.
17:19.12SamotOK
17:19.21kfifeI guess I should have asked you if you think we need more than one turing complete language ;-)
17:19.27SamotSo far what I've gotten from this is "I don't want to maintain dialplan and AMI code for this"
17:21.21kfifeYou are correct.  That is exactly what I'm saying.
17:22.43kfifeEver heard of D.R.Y.?  Especially important in something like asterisk where regression testing is a challenge.
17:24.37SamotDon't Repeat Yourself.
17:24.39SamotYes. I have.
17:24.54SamotSo then just have AMI send PlayDTMF to trigger your *3
17:25.39*** part/#asterisk Ast001 (~uros@p5DCD6D28.dip0.t-ipconnect.de)
17:27.24SamotAt the end of the day, you're still maintaining AMI code in your web GUI code.
17:27.36SamotNo matter if it's just sending *3 or actually triggering apps.
17:27.52SamotIt's not like a class that you can just call on between dialplan and AMI
17:30.32craigifykfife, you could use AsyncAGI over AMI and implement this in some external software, then trigger it using both dynamic feature codes and via AMI directly? You'd solve your issue by having the code in one place.  You'd have to do a lot of legwork though, but you could probably use a async-agi library for your programming language of choice.
17:30.51craigifyIt would also help to understand the evolution of Asterisk from a PBX into more like a communications/telephony framework
17:31.05SamotThe code would not be in one place.
17:31.09SamotThat is incorrect.
17:31.13SamotThere is the dialplan.
17:31.14craigifyyes it would
17:31.23SamotThen there is the code to trigger AMI outside of Asterisk.
17:31.36craigifyyes, you'd have code in many places to handle triggering
17:31.38SamotBe it using any of the AMI actions like AGI or PlaDTMF
17:31.40craigifybut your business logic could be in one place
17:31.50craigifyare we splitting hairs here?
17:32.10Samot1:19:27 PM <Samot> So far what I've gotten from this is "I don't want to maintain dialplan and AMI code for this"
17:32.10Samot1:21:22 PM <kfife> You are correct.  That is exactly what I'm saying.
17:32.24craigifywell, then it's impossible
17:32.28SamotMy point.
17:32.39craigifyI thinnk he means the business logic
17:32.47SamotRegardless of what the AMI command is doing...
17:32.51craigifywhatever the thing that the dynamic feature triggers
17:32.52SamotThere's code for it outside of Asterisk
17:33.07SamotYou have to connect, send the commands, logout
17:33.13craigifyyeah, youd have to do all that
17:33.15craigifyright
17:33.19SamotAnd of course, deal with those responses.
17:33.22craigifybut then your business logic is in one place
17:33.38craigifyI'm trying to show how that it is possible, but probably not the best choice for one single task
17:34.05craigifyunless there is some larger overall picture here and other features could be developed and implemented
17:35.34kfifeEspecially since it seems like ti would be easy to do.
17:36.19craigifythis is getting into more of a fundamental software architecture discussion
17:36.50craigifyIMO, I wouldn't call it 'easy' to implement the way I am saying, but rather an alternative to consider by weighing in other factors in the project as a whole
17:38.06craigifyand it specifically addresses your comment about a missing feature
17:38.18craigifyor well, I was trying to at least
17:39.42kfife+1 craigify
17:39.47craigifyfurthermore, as was said, you'd still have to handle the dynamic feature when it's keyed in, and you'd have to handle the external system to know how and when to trigger some AMI command, and then you'd have your business logic implemented in yet another part that uses both AMI and AsyncAGI to perform the action, and that other part could be called pragmaticaally from a number of different ways
17:39.50SamotI'm not sure it is.
17:39.57craigifynow, this is starting to get complicated
17:40.14craigifyso, a takeaway message would be, is this complexity worth it?  Is it just a simple fix?
17:40.17SamotAMI is for outside interaction with Asterisk.
17:40.32SamotAGI / Diaplan is for in-call interaction with Asterisk.
17:40.37craigifyAsyncAGI
17:40.40craigifyover AMI
17:40.45SamotSure.
17:40.46craigifybe sure to make the distinction
17:40.54SamotIt's an outside action to trigger an inside action.
17:40.57craigifyusing those two things you could build something in NodeJS, or whatever
17:41.01SamotStill outside of Asterisk.
17:41.03craigifyimplement your logic in there
17:41.05craigifyyes it would be
17:41.15craigifyI'm not arguing your point there
17:41.18SamotI can make it so my users can do things via the dialplan.
17:41.27SamotAnd a GUI using AMI
17:41.30SamotOr one or the other.
17:41.32craigifyok, also a suggestion
17:41.49craigifyyou'll run into issues with the Dial application when in a bridged call though
17:41.54craigifyblocking the dialplan
17:42.12craigifyhence the need for dynamic features in the first place
17:43.05SamotA dynamic feature is to map digits to application/functions.
17:43.13SamotSo when I dial *3 it does something.
17:43.44SamotI can make it so *3 does something different for every call
17:43.47SamotOr user..
17:44.07SamotJust all depends on what is what.
17:44.16SamotAnd how you configure things.
18:00.00igcewieling*sigh*  To day we are installing at a site which uses different ISPs depending on where you are physically located in the building.
18:00.50SamotFun
18:01.04igcewielingApparently it was too much trouble to run a line to a different floor.
18:16.20*** join/#asterisk sebastienthiry (~Thunderbi@109.134.212.7)
18:17.47*** join/#asterisk clarjon1 (~clarjon1@unaffiliated/clarjon1)
18:23.19*** join/#asterisk tonsofpcs (~mythbuntu@rivendell/member/tonsofpcs)
18:40.30*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)
18:54.44kfifecraigify: I wonder if there are special shoes for digging in one's heels. :-)
19:19.34*** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl)
19:27.10*** join/#asterisk Iamnacho (~Iamnacho@ip68-103-241-71.ks.ok.cox.net)
19:29.06*** join/#asterisk AntonioTejeda86 (~antonio@187-162-76-72.static.axtel.net)
19:30.12AntonioTejeda86What is the purposse of this chat?
19:30.28AntonioTejeda86can we share doubts about asterisk?
19:30.50[TK]D-FenderWe do't generally have doubts about it
19:30.56[TK]D-FenderWe kinda just use it...
19:31.12[TK]D-FenderThis is a place to talk ABOUT it though....
19:32.50craigifylol
19:34.00AntonioTejeda86Ok, so I've been using Asterisk 6 years ago I'm Dcap, so nice to meet you all, whatever the purposse this chat has lol
19:34.30craigifyIt's usually people coming in here and asking all sorts of questions
19:35.18[TK]D-Fender<[TK]D-Fender> This is a place to talk ABOUT it though....
19:35.32craigifyI, for one, really like Asterisk, and I'm glad it exists.  I've based a cloud based telephony project on Asterisk and rely on it every day in a production environment, as do lots of others in here from what I can tell.
19:35.51craigifydo I think it's perfect? No software is.
19:54.22*** join/#asterisk WizJin (~Ozzy@150.129.105.149)
19:54.36WizJinHello
19:58.57*** join/#asterisk jkroon (~jkroon@165.16.204.171)
19:59.18*** join/#asterisk rrittgarn (~rrittgarn@75-150-221-205-Illinois.hfc.comcastbusiness.net)
20:00.48*** join/#asterisk dacleaner (~dacleaner@12.229.24.212)
20:22.09*** join/#asterisk Oatmeal (~Suzeanne@66-214-156-171.static.mtpk.ca.charter.com)
20:49.07*** join/#asterisk war9407 (war@pool-70-106-236-148.clppva.fios.verizon.net)
20:53.04*** join/#asterisk CatCow97 (~mine9@c-24-22-38-85.hsd1.or.comcast.net)
20:55.35*** join/#asterisk Typhon (~Typhon@ipservice-092-211-209-209.092.211.pools.vodafone-ip.de)
21:08.41*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
21:27.39*** join/#asterisk [TK]D-Fender (~joe@64.235.216.2)
22:06.14*** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca)
22:20.22*** join/#asterisk imcdona (~imcdona@2607:f0d8:20:1001:b88f:115c:5675:b5f7)
22:31.10*** join/#asterisk bmg505 (~leon@196-210-23-42.dynamic.isadsl.co.za)
23:02.55*** join/#asterisk sibyakin (~sibyakin@188.162.228.26)
23:12.19drmessanoI doubt Asterisk even exists
23:12.55drmessanoI once opened Mark Spencer's vault, looking for Asterisk
23:12.58drmessanoand it was EMPTY
23:51.23*** part/#asterisk kharwell (kharwell@nat/digium/x-ejzagrpusbzllfno)
23:55.45*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-157-202.satx.res.rr.com)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.