00:24.29 | *** join/#asterisk nickfennell (~nickfenne@unaffiliated/nickfennell) |
00:27.49 | *** join/#asterisk bkruse (~Adium@user-69-1-25-11.knology.net) |
00:54.26 | *** join/#asterisk italorossi (~Adium@179.234.138.92) |
00:55.26 | *** join/#asterisk bkruse (~Adium@user-69-1-25-11.knology.net) |
01:36.44 | *** join/#asterisk mjordan (~mjordan@75.76.55.191) |
01:36.44 | *** mode/#asterisk [+o mjordan] by ChanServ |
02:43.45 | *** join/#asterisk crocodilehunter (~Thunderbi@CPE-121-211-237-81.hhui7.cht.bigpond.net.au) |
03:00.01 | *** join/#asterisk darkbasic (~quassel@niko.linuxsystems.it) |
03:33.19 | *** join/#asterisk moe` (~moe@node-be028882.scarlet.cw) |
03:33.45 | moe` | can someone tell me, asterisk buffers syslog? |
03:35.29 | moe` | logging via syslog shows delays, logging direct to file does not... is this a function of asterisk not flushing to syslog? |
03:37.26 | WIMPy | Syslog can do its own buffering. |
03:37.38 | moe` | yeah, I know |
03:37.59 | moe` | but is there a toggle on the asterisk side for it running flush() to the handle? |
03:38.51 | moe` | hang on, installing lsof to see how asterisk opened syslog |
03:38.58 | WIMPy | I know I have it enabled, but I don't think I have ever tried to use syslog from Asterisk. |
03:40.43 | moe` | its using filesystem "socket" /var/run/log, not UDP |
03:40.46 | moe` | ok |
03:41.02 | moe` | er |
03:41.49 | moe` | no |
03:43.50 | WIMPy | udp? |
03:44.23 | moe` | uh, "logger reload" didn't work, but a complete "reload" did, now its logging everything properly |
03:45.35 | moe` | I dunno how the hell its logging, via what mechanism |
03:46.02 | WIMPy | A socket? |
03:46.38 | moe` | well its not UDP, dump on lo0 and local NIC src or dst port 514 shows nothing when events are logged |
03:46.42 | moe` | so filesystem socket |
03:46.43 | moe` | I assume |
03:46.59 | moe` | does asterisk open and close it on every log event I wonder? |
03:47.31 | WIMPy | The source is with you. |
03:48.24 | moe` | indeed |
03:50.15 | moe` | is there no asterisk source tarball on asterisk.org? |
03:50.24 | moe` | git annoys me, mostly |
03:51.25 | moe` | nevermind, found it |
03:51.26 | moe` | duh |
03:51.26 | WIMPy | downloads.asterisk.org. |
03:55.51 | moe` | no, it calls openlog() only once |
03:55.58 | moe` | closelog() on exit/reload etc |
04:00.19 | *** join/#asterisk spicyramen_ (~Adium@c-98-210-160-181.hsd1.ca.comcast.net) |
04:03.17 | *** part/#asterisk mjordan (~mjordan@75.76.55.191) |
04:05.12 | moe` | yeah, found the filesystem socket via lsof, was just looking incorrectly |
04:05.41 | moe` | syslog opens the /var/run/log, and of course associates a handle with it. asterisk opens the handle, not the filesystem path |
04:05.47 | moe` | man I've been out of coding too long |
04:06.30 | *** join/#asterisk gerhard7 (~gerhard7@77-172-82-111.ip.telfort.nl) |
04:07.18 | moe` | or at least that's how its represented with lsof |
04:08.59 | moe` | anyway, the whole point was to verify log rotation, and its working fine after rotation. |
04:11.02 | *** join/#asterisk crocodilehunter (~Thunderbi@CPE-121-211-237-81.hhui7.cht.bigpond.net.au) |
04:12.20 | moe` | oh nice, logchannel is indifferent to file or syslog, so multiple syslog channels (to different facilities) are possible. |
04:17.55 | moe` | (thus different verbosity levels to different facilities) |
04:34.35 | *** join/#asterisk protem (~protem@unaffiliated/protem) |
04:48.53 | *** join/#asterisk babak (uid19622@gateway/web/irccloud.com/x-epovgjouslgmnbku) |
07:19.07 | *** join/#asterisk Kilo`byte (~kilobyte@5.231.51.78) |
07:22.24 | *** join/#asterisk justdave (~dave@unaffiliated/justdave) |
07:25.10 | *** join/#asterisk LiuYan (~hola@unaffiliated/liuyan) |
07:38.39 | *** join/#asterisk zogm (~zogm@gateway/vpn/privateinternetaccess/zogm) |
07:50.12 | *** join/#asterisk darkbasic_ (~quassel@niko.linuxsystems.it) |
08:49.51 | *** join/#asterisk coppice (~chatzilla@123203240102.ctinets.com) |
09:22.21 | *** join/#asterisk Ice_Strike (~none@84.92.51.164) |
10:43.54 | *** join/#asterisk wonderworld (~ww@ip-176-199-166-61.hsi06.unitymediagroup.de) |
10:56.13 | *** join/#asterisk CustosL1men (~CustosLim@unaffiliated/cust0slim3n) |
10:58.58 | *** part/#asterisk LiuYan (~hola@unaffiliated/liuyan) |
11:16.32 | *** join/#asterisk darkbasic (~quassel@niko.linuxsystems.it) |
11:36.36 | janicez | Hu |
11:36.38 | janicez | Hi |
11:45.51 | *** join/#asterisk darkbasic_ (~quassel@niko.linuxsystems.it) |
11:56.04 | babak | Hi, Is there any colorful text editor designed for Asterisk Dialplans ? |
11:58.01 | dadrc | There's plugins for Notepad++ and Sublime Text |
11:58.37 | dadrc | For vim and emacs, too. |
11:58.41 | dadrc | of course. |
11:59.35 | *** join/#asterisk fstd (~fstd@unaffiliated/fisted) |
11:59.42 | babak | dadrc: thx , googling now which one you suggest running on windows ? |
12:00.41 | dadrc | I like Sublime, but Notepad++ is free, so I'd start there. |
12:01.19 | babak | dadrc: thx |
12:02.27 | *** join/#asterisk file (~file@asterisk/developer-and-muffin-lover/file) |
12:02.27 | *** mode/#asterisk [+o file] by ChanServ |
12:20.44 | *** join/#asterisk darkbasic (~quassel@niko.linuxsystems.it) |
12:26.16 | MaliutaLap | vim with syntax highlighting |
13:01.14 | *** join/#asterisk CustosL1men (~CustosLim@unaffiliated/cust0slim3n) |
13:22.49 | *** join/#asterisk evilman_work (~evilman@87.244.6.228) |
13:23.03 | *** join/#asterisk [Outcast] (outcast@nat/cisco/x-zggdjsfpglwzmnzk) |
13:24.06 | *** join/#asterisk darkbasic (~quassel@niko.linuxsystems.it) |
13:55.03 | *** join/#asterisk [TK]D-Fender (~joe@64.235.216.2) |
14:02.59 | *** join/#asterisk TriJetScud (~TriJetScu@van-app-svr.ad.v10networks.ca) |
14:02.59 | *** join/#asterisk nanoha-sama (~nanoha-sa@van-app-svr.ad.v10networks.ca) |
14:26.19 | *** join/#asterisk kritzikratzi (~kritzikra@cpe90-146-150-86.liwest.at) |
14:27.19 | *** join/#asterisk [Outcast] (outcast@nat/cisco/x-nrsgncoeukyylqgt) |
14:35.12 | *** join/#asterisk [sr] (~kvirc@pal-213-228-163-73.netvisao.pt) |
14:50.04 | *** join/#asterisk MarkSX (~MarkSX@unaffiliated/marksx) |
15:12.44 | *** join/#asterisk bkruse (~Adium@user-24-96-51-167.knology.net) |
15:21.23 | Ice_Strike | ~book |
15:21.23 | infobot | Asterisk: The Definitive Guide, 4th Edition (ISBN 1-4493-3242-0) available at http://oreilly.com/catalog/0636920025894 - Asterisk: The Definitive Guide is released under a Creative Commons License (http://creativecommons.org/licenses/by-nc-nd/3.0/us/) and a version is available for reading online at http://www.asteriskdocs.org/ or see ~buybook |
15:40.28 | Ice_Strike | Is there a way to use AMD (answering machine detection) in ARI? |
15:42.12 | [TK]D-Fender | AMI id a dialplan app |
15:42.23 | [TK]D-Fender | if you can call any diaplan app in ARI... then you can call that one |
15:47.15 | Ice_Strike | Ah ok |
15:47.42 | Ice_Strike | [TK]D-Fender I am just comparing with AMI and ARI. I am trying to make a decision which one to go for. |
15:49.05 | [TK]D-Fender | Well when you are talking about a diaplan app... you are talking about a diaplan app. You should instantly know if you can use them as-is or not.... |
15:49.30 | [TK]D-Fender | Shouldn't have to be a question basically. |
15:49.59 | Ice_Strike | I like to develop a predictive dialer system (Web base). Creating many outbound calls and live recordings. Also including AMD. That is why I am comparing which is right "approch" to use - AMI or ARI |
15:53.17 | [TK]D-Fender | or if you need either |
15:55.02 | Ice_Strike | AMI seem simpler |
15:55.19 | Ice_Strike | What if I want like ChanSpy functionality in ARI? |
15:57.34 | [TK]D-Fender | Read the docs? |
15:57.47 | [TK]D-Fender | ARI's API is very clearly listed..... |
15:58.22 | Ice_Strike | yes im reading |
15:58.28 | [TK]D-Fender | https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Channels+REST+API?focusedCommentId=32375948#comment-32375948 |
15:58.38 | [TK]D-Fender | Sroll up.... bad jump in link |
15:58.53 | Ice_Strike | ah |
16:00.23 | Ice_Strike | I wish there is ARI's API for AMD |
16:03.23 | [TK]D-Fender | it isn't a "function", it's a long result |
16:03.51 | [TK]D-Fender | ari is for having fine control on all the little pieces.AMD is a very specific collections of pieces |
16:03.56 | [TK]D-Fender | that's backwards |
16:04.04 | [TK]D-Fender | So either call the app ... or reimplement it |
16:04.12 | [TK]D-Fender | or use BOTH |
16:04.41 | Ice_Strike | Reading on the Mailing List: |
16:04.43 | Ice_Strike | "From what I know, not exactly. The best that Iâve come up with is to initially send the call to Stasis (so that youâre subscribed to the events), then send it to AMD, then back to Stasis in the dialplan. I subsequently read the channel variables." |
16:04.48 | Ice_Strike | No idea what that mean |
16:04.52 | Ice_Strike | http://www.spinics.net/lists/asterisk-app-dev/msg00699.html |
16:05.19 | WIMPy | Why don't you just use the dialplan? |
16:11.50 | Ice_Strike | WIMPy If I use ARI's API to originate the outbound call, how is it possible to use AMD dialplan at the same time? |
16:15.53 | [TK]D-Fender | Ice_Strike, Originate = ANOTHER CHANNEL |
16:16.05 | [TK]D-Fender | You point that to some spot in the dialplan |
16:17.06 | [TK]D-Fender | Originate. Dump to some point in the dialplan. Call AMD. Do other stuff. this can be PURE dialplan |
16:17.34 | [TK]D-Fender | You haven't stated anything to might require AMI, AGI, or ARI |
16:17.42 | [TK]D-Fender | Could even be launched off call files |
16:19.35 | Ice_Strike | I see, now I get it. |
16:20.34 | [TK]D-Fender | You need to really consider the exact interactions with the call you need before asking if X can do it |
16:20.48 | [TK]D-Fender | get the list thing and then find out the simplest method to do it |
16:21.03 | Ice_Strike | Yep. |
16:21.16 | [TK]D-Fender | There were predictive dialers around that used AMD long for ARI existed |
16:21.26 | [TK]D-Fender | So clearly it wasn't need for their methods and ideas. |
16:21.46 | [TK]D-Fender | Properly define your own needs and see where they are different or worth doing in a different way due to new means |
16:22.08 | Ice_Strike | Sure, good point |
16:23.23 | Ice_Strike | I will make a lists and requrement. And then decide which is easy and simple to implement via AMI or ARI. |
16:23.39 | Ice_Strike | I know AMI is old and its popular. |
16:26.41 | [TK]D-Fender | So far I can see plenty of cases for needed NEITHER |
16:26.45 | [TK]D-Fender | needing |
16:30.35 | Ice_Strike | Basically something like that: Get numbers from DB -> Make outbound concurrent calls -> If Answered then execute Answering Machine Detection -> If detected then hangup -> If customer speaking then start recording. Agent can Pause recording, Transfer Call, Hangup. |
16:33.17 | *** join/#asterisk evil_gordita (robert@ip70-188-63-173.rn.hr.cox.net) |
16:34.14 | [TK]D-Fender | So far that sounds like it's possibe iwht pure dialplan |
16:34.48 | [TK]D-Fender | 3 dialplan app. |
16:34.52 | [TK]D-Fender | maybe 4 |
16:35.31 | Ice_Strike | Yep, forgot to mention about Queue |
16:36.58 | *** join/#asterisk file (~file@asterisk/developer-and-muffin-lover/file) |
16:36.58 | *** mode/#asterisk [+o file] by ChanServ |
16:37.03 | Ice_Strike | Good thing about ARI that events in returned in json so it make coding much simple. |
16:37.56 | [TK]D-Fender | Question is "what actually REQUIRES more than the minimum" |
16:38.09 | [TK]D-Fender | With a vague reference to "queue" |
16:38.20 | [TK]D-Fender | You need to make a MUCH better description for this |
16:42.48 | Ice_Strike | [TK]D-Fender On the backend, Admin can create a new a Outbound Campaign which therefore create a new Queue Asterisk. |
16:42.59 | Ice_Strike | on Asterisk* |
16:43.07 | WIMPy | No |
16:43.17 | WIMPy | Not in Asterisk. In your application. |
16:44.18 | [TK]D-Fender | unless youa re talking about "app_queue".... it isn't asterisk |
16:44.41 | WIMPy | Don't get him in that direction again. |
16:45.07 | [TK]D-Fender | I'm trying to make sure he doesn't :) |
16:45.15 | Ice_Strike | O_o |
16:46.58 | *** join/#asterisk bkruse (~Adium@user-24-96-51-167.knology.net) |
16:47.17 | Ice_Strike | Why do you say app_queue isnt asterisk? |
16:47.27 | [TK]D-Fender | Read what I said again. |
16:47.31 | [TK]D-Fender | your read it very wrong |
16:47.31 | WIMPy | Noone said that. |
16:47.56 | [TK]D-Fender | UNLESS you are talking about "app_queue" then you are not talking about Asterisk. |
16:48.20 | Ice_Strike | Ahh ok |
16:48.30 | [TK]D-Fender | You just said "* calls out, checks AMD, then is talking to some kind of person you called "agent" and that call is recorded |
16:48.45 | [TK]D-Fender | Nothing about this has any hint of app_queue about it |
16:52.45 | *** join/#asterisk cyford (~cyford@c-73-137-1-6.hsd1.ga.comcast.net) |
16:58.02 | Ice_Strike | Well, While Originating a call, it goes to Queue($var_campaign) in the dial plan for example |
16:58.26 | WIMPy | What would it do there? |
17:02.34 | [TK]D-Fender | Does it? |
17:02.43 | [TK]D-Fender | You have not drawn a proper picture |
17:02.56 | [TK]D-Fender | stop now and actually write out your plan |
17:03.08 | *** join/#asterisk babak (uid19622@gateway/web/irccloud.com/x-arscvjchxqeokorf) |
17:03.20 | [TK]D-Fender | If this is going to trickle in one bit at a time we're going to end up wasting a lot of time |
17:04.34 | Ice_Strike | I'll draw a plan like a flowchart ;) |
17:04.39 | Ice_Strike | To get idea |
17:05.24 | WIMPy | If you're sure that YOU got the idea, you can tell us what it is. |
17:06.16 | Ice_Strike | I rather learn queue a bit more first and then decide. |
17:07.00 | WIMPy | How is that going to help you find out what your goal is? |
17:07.58 | WIMPy | Are you trying to pick some pieces, stick them together and see what it does? Or do yu have a task that needs implementing? |
17:10.03 | [TK]D-Fender | You should be thinking of the percieved actions, not the tool that does it |
17:10.32 | [TK]D-Fender | With the exception of AMD because that is at least a self-contained step |
17:30.54 | Ice_Strike | Ok, without going to technical details or what tools to use. I will try my best to explain the task. I like to develop a predictive dialler system. Admin can create many inbound campaigns and outbound campaigns. Admin can assign agents to specific inbound or outbound campaign. |
17:31.13 | Ice_Strike | Agents will have to login on the web via entering Extension number which will be shown on the hardware sip phone. Phone will ring and agent will press a key to sign in. |
17:31.34 | *** join/#asterisk darkbasic_ (~quassel@niko.linuxsystems.it) |
17:31.42 | *** join/#asterisk u0m3 (~u0m3@92.80.73.226) |
17:31.52 | Ice_Strike | For Inbound: Let say there are 5 agents in Support inbound campaign and it is currently full. Customer will have to wait in the queue and hear the background music. If any agent is available then waiting customer will automatically will be pushed to available agent. If wrap uptime is more than 5 minutes then agent should no longer be in the queue. |
17:32.55 | Ice_Strike | For Outbound: As explained before, make numbers of outbound calls and answers , do AMD detection. If any customer answer the call then abandoned other calls or direct answered to other available agents. (Not sure what benefit of using Queue for the Outbound calls?) |
17:33.07 | WIMPy | How is that related to your dialler app? Sounds like you just expanded your task massively. |
17:33.17 | Ice_Strike | :( |
17:35.11 | Ice_Strike | I thought I have explained about dialler app. Oh well. |
17:36.00 | WIMPy | You should make a very etailed concept. The what happens if ... - type. |
17:37.37 | Ice_Strike | Ok |
17:41.18 | Ice_Strike | Can you short example so I get the concept what you mean. |
17:52.33 | [TK]D-Fender | You also just call someone an Agent |
17:52.38 | [TK]D-Fender | What does that MEAN. |
17:53.02 | [TK]D-Fender | The title you put on a pay-cheque is not a "thing" to your phone system |
17:53.17 | Ice_Strike | Call Operator = Agent |
17:54.28 | [TK]D-Fender | So is this the chain : Call-out initiated. Other end answers. Passes AMD. Lands in an * queue that will ring up queue memebers. Someone answers and the call is recorded. |
17:54.33 | [TK]D-Fender | ? |
17:54.46 | Ice_Strike | Yes |
17:55.46 | Ice_Strike | But |
17:55.56 | Ice_Strike | one moment |
17:56.15 | WIMPy | Well, so far for "detail" and "concept"... |
17:56.44 | WIMPy | Lay out exactely what has to heppen in what circumstances. |
17:57.01 | WIMPy | Write it down in a flow chart or something. |
17:57.06 | Ice_Strike | Ok :) |
17:57.48 | [TK]D-Fender | And you're taking WAY too long to even finish that "but" with an actual difference or varience |
17:57.48 | WIMPy | And off course you could question if there isn't an easier way to piss off customers :-) |
17:58.05 | [TK]D-Fender | If I was missing something it should have been VERY fast to say "and I also want X in case Y", etc |
17:58.48 | Ice_Strike | I know, my mistake :) |
18:09.00 | *** join/#asterisk sruffell (~sruffell@asterisk/the-kernel-guy/sruffell) |
18:09.00 | *** mode/#asterisk [+o sruffell] by ChanServ |
18:09.33 | *** join/#asterisk busymind (~textual@c-24-21-79-235.hsd1.wa.comcast.net) |
18:09.40 | busymind | is anyone online this morning? |
18:10.25 | WIMPy | No. The internet has been switched of for political reasons. |
18:10.34 | WIMPy | Worldwide. |
18:10.36 | busymind | lol |
18:10.52 | busymind | well, i'm having a weird issue with chanspy |
18:11.10 | busymind | I can chanspy using g711 just fine, but when using g722, the audio quality is awful |
18:11.25 | busymind | on asterisk 11.18 |
18:11.43 | file | there was a bug, it'll be fixed in the next release |
18:11.48 | WIMPy | There was somethign about just that on issues.asterisk.org. |
18:12.14 | busymind | gotcha |
18:12.25 | busymind | any idea when the next release is going to be? |
18:12.54 | file | a week or so I'd say |
18:13.31 | busymind | whats the issue number? |
18:14.17 | file | ASTERISK-25247 |
18:14.44 | busymind | bingo - thats it |
18:14.53 | busymind | thank you @file |
18:15.30 | busymind | it says it was fixed? |
18:15.48 | file | yes, it was fixed in the tree |
18:15.51 | file | it has not yet landed in a release |
18:16.54 | busymind | gotcah |
18:17.01 | busymind | is the next release 11.19? |
18:17.13 | file | yes |
18:17.29 | WIMPy | You can always pull the current version from git. |
18:17.37 | file | sure can |
18:17.46 | WIMPy | But that requires some patience and much coffee. |
18:17.54 | busymind | nah, its not critical. I'd rather just use the official release lol |
18:18.42 | busymind | thanks @file for the help :) |
18:18.45 | busymind | i was going crazy |
18:19.14 | busymind | i thought timerfd was messed up |
18:30.46 | Ice_Strike | [TK]D-Fender Here the flowchart http://s1.postimg.org/8mrr8yd9r/Untitled_Diagram.png |
18:32.54 | [TK]D-Fender | only difference is that agents aren't "callerd' it looks like they are sitting in agent_login |
18:35.10 | Ice_Strike | Hmmm |
18:36.08 | WIMPy | Yes, that's what it looks like. But then that's probably what you want when doing outbound calls. |
18:36.29 | WIMPy | Oh, and BTW: Don't forget to consult a lawyer. |
18:40.29 | Ice_Strike | I am not too sure how it actually work. I have seen existing dailer system when Agent Login is sucessfull - it become "Pause" on the screen and agent press "Ready" which mean waiting it start making outbound calls and waiting for answered call. |
18:45.19 | Ice_Strike | [TK]D-Fender Do you have any suggestion or what the flaw in that design? |
18:53.34 | [TK]D-Fender | who said there was a flaw? |
18:54.07 | [TK]D-Fender | Why would someone loging and start on pause? |
18:54.17 | [TK]D-Fender | you don't start something just to be "stopped" |
19:05.51 | [TK]D-Fender | and if you actually even wanted to do this.. then script something to target that agent and set them to paused |
19:08.24 | WIMPy | And you need to find out how you get the calls to the "agents". |
19:10.57 | [TK]D-Fender | WIMPy, there are sitting in a queue actually |
19:11.07 | [TK]D-Fender | and the originated channels dump the callers there |
19:11.12 | [TK]D-Fender | So this is pretty basic |
19:11.22 | WIMPy | How do you have them waiting on the phone with app_queue? |
19:15.47 | [TK]D-Fender | agentlogin |
19:16.09 | [TK]D-Fender | active channel sitting literally waiting for app_queue to beep them |
19:16.19 | [TK]D-Fender | Something almost nobody uses |
19:16.48 | WIMPy | Hmm. Looks like somethign I don't have. |
19:18.56 | WIMPy | Where's that hidden away? |
19:23.55 | [TK]D-Fender | not sure if I'm missing a char on the name |
19:23.58 | [TK]D-Fender | but it's ancient |
19:24.17 | [TK]D-Fender | http://www.voip-info.org/wiki/view/Asterisk+cmd+AgentLogin |
19:24.17 | WIMPy | I see it in the wiki. |
19:25.24 | WIMPy | Looks like ou need chan_agent. But I still can't find that application. |
19:26.04 | [TK]D-Fender | not sure if it's still around really |
19:26.08 | [TK]D-Fender | I try not to think about it |
19:26.29 | WIMPy | It's in the wiki for 12. |
19:26.38 | *** join/#asterisk zapata (~zapata@2a02:b18:581:10:8c45:80c2:845d:15d6) |
19:27.49 | WIMPy | Ok. Helps if you actually load chan_agent... |
19:33.29 | *** join/#asterisk spicyramen_ (~Adium@c-98-210-160-181.hsd1.ca.comcast.net) |
19:52.37 | *** join/#asterisk zerohalo (~zerohalo@2601:199:4200:d92e:915f:288:f8dd:3bbd) |
19:54.24 | Ice_Strike | [TK]D-Fender Sorry I was away.. Ok that make a lot of sense. I won't use set them to paused on start. |
20:00.28 | *** join/#asterisk jdgirard (~quassel@43.65.50.123.dsl.dyn.mana.pf) |
20:03.17 | *** join/#asterisk F2Knight (~F2Knight@c-50-139-86-39.hsd1.or.comcast.net) |
20:03.46 | Ice_Strike | [TK]D-Fender You wrote "Something almost nobody uses" - what do you mean? |
20:13.30 | Ice_Strike | WIMPy Look like chan_agent removed in Asterisk 12 |
20:24.13 | WIMPy | Then wy is it in the wiki for 12? |
20:27.31 | [TK]D-Fender | * 12 = DEAD |
20:27.40 | [TK]D-Fender | Don't even think about it |
20:28.03 | *** join/#asterisk sparetire_ (~sparetire@unaffiliated/sparetire) |
20:33.27 | Ice_Strike | Ok other question. On the backend Admin can create a new Agent account with username and password (for web login) and select unused AgentLogin (user/pass) from agent.conf |
20:33.34 | Ice_Strike | Is that sound good approach? |
20:39.05 | [TK]D-Fender | apparently chan_agent and agentlogin are already dead going forawrd |
20:39.17 | [TK]D-Fender | which means this entire topic should be pointless |
20:39.22 | [TK]D-Fender | And you should consider another approach |
20:40.03 | *** join/#asterisk zogm (~zogm@gateway/vpn/privateinternetaccess/zogm) |
21:08.11 | Ice_Strike | What is another approach? |
21:09.22 | Ice_Strike | Are you sure agentlogin is going to die forward |
21:18.35 | Ice_Strike | If it is, does that mean agent.conf gonna disappear too? |
21:24.32 | [TK]D-Fender | Do you see the dialplan apps and channel driver in * 13? |
21:26.33 | Ice_Strike | Well, I see this: https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+Application_AgentLogin |
21:26.45 | Ice_Strike | Unless I am missing something. |
21:27.56 | [TK]D-Fender | Looks like it is still there |
21:28.04 | [TK]D-Fender | go test it |
21:28.12 | [TK]D-Fender | If so.. then it should be fine for now |
21:29.04 | Ice_Strike | Sure |
21:29.41 | Ice_Strike | Let assume in the future they gonna remove agentlogin - what is the alternative approach? |
21:32.16 | [TK]D-Fender | We don't know. |
21:32.18 | [TK]D-Fender | that's the future |
21:32.27 | [TK]D-Fender | at least it doesn't seem to be gone now. |
21:32.32 | [TK]D-Fender | maybe it will last around |
21:33.58 | *** join/#asterisk gringo (~gringo@unaffiliated/gringo) |
21:47.15 | Ice_Strike | hmm |
21:54.41 | esaym153 | if I configure MOH to use a streaming internet source, is it true that it will always be reading the stream even when MOH is not needed? That is what this article says: http://nerdvittles.com/?p=7248 |
22:47.40 | *** join/#asterisk K0HAX (~K0HAX@c-75-72-143-131.hsd1.mn.comcast.net) |
23:13.59 | *** join/#asterisk darkbasic (~quassel@niko.linuxsystems.it) |
23:20.03 | drmessano | After the first instance is run, yes |
23:20.40 | drmessano | esaym153, |
23:22.27 | *** join/#asterisk HeN (uid3747@gateway/web/irccloud.com/x-eorxumlannjzsmpf) |
23:38.31 | *** join/#asterisk crocodilehunter (~Thunderbi@CPE-121-211-237-81.hhui7.cht.bigpond.net.au) |
23:59.36 | *** join/#asterisk fstd (~fstd@unaffiliated/fisted) |