IRC log for #asterisk on 20181011

00:12.40*** join/#asterisk lankanmon (~LKNnet@CPE64777d632383-CM64777d632380.cpe.net.cable.rogers.com)
00:14.21*** join/#asterisk [d__d] (~d__d]@ec2-54-85-45-223.compute-1.amazonaws.com)
00:14.30*** join/#asterisk remote (~remote@50.116.54.131)
02:24.48*** join/#asterisk infobot (ibot@208.53.50.136)
02:24.48*** topic/#asterisk is #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.23.1 (2018/09/20) 16.0.0 (2018/10/09), Security Only: 15.6.1 (2018/09/20); 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
02:31.48*** part/#asterisk ssieb (~chatzilla@S010610bf487c4f29.cc.shawcable.net)
02:45.47*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
02:54.05*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
02:59.55*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
03:10.45*** join/#asterisk _mwoodj_ (~mwoodj@pdpc/sponsor/digium/hyper-eye)
03:21.57*** join/#asterisk Cory (~Cory@unaffiliated/cory)
03:26.55*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
04:08.52*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
04:09.22*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
04:13.50*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
04:30.50*** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl)
04:59.15*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
05:33.25*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
06:22.46*** join/#asterisk pchero (~pchero@87.213.247.82)
06:27.48*** join/#asterisk pchero (~pchero@87.213.247.82)
07:02.11*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
07:08.24*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
07:20.54*** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch)
07:46.05*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
07:47.10*** join/#asterisk evil_gordita (robert@ip70-188-41-127.rn.hr.cox.net)
07:58.27*** join/#asterisk miralin (~Thunderbi@194.8.128.68)
08:05.29*** join/#asterisk pchero (~pchero@60.30.148.146.bc.googleusercontent.com)
08:45.02*** join/#asterisk stefanauss (~stefanaus@host222-246-static.59-217-b.business.telecomitalia.it)
08:54.47*** join/#asterisk kangtastic (~kangtasti@2600:1700:31e0:5d90:6dde:6c84:759:b5d2)
10:25.41*** join/#asterisk qxork (~qxork@unaffiliated/qxork)
10:32.58*** join/#asterisk bhuddah (~michael@unaffiliated/bhuddah)
10:48.11*** join/#asterisk MarkSX (~MarkSX@unaffiliated/marksx)
10:49.19*** join/#asterisk lankanmon (~LKNnet@CPE64777d632383-CM64777d632380.cpe.net.cable.rogers.com)
11:11.11*** join/#asterisk pchero (~pchero@87.213.247.82)
11:46.03*** join/#asterisk pchero (~pchero@87.213.247.82)
11:57.24*** join/#asterisk sh_smith (~sh_smith@cpe-76-174-26-91.socal.res.rr.com)
12:08.26*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
12:21.43*** join/#asterisk samwierema (~samwierem@195.240.143.134)
12:29.22*** join/#asterisk [TK]D-Fender (~joe@216.191.106.165)
12:29.30*** join/#asterisk pchero (~pchero@87.213.247.82)
13:06.43*** join/#asterisk jjg (~clh@75-147-197-114-Atlanta.hfc.comcastbusiness.net)
13:06.47*** join/#asterisk xyz111 (~Thunderbi@2a02:c7d:3c50:3a00:cbe:abcc:b354:3ba0)
13:12.10*** join/#asterisk soloma (~soloma@5.152.45.182)
13:13.15solomaHello all. Could you help me with devices states sharing? Is there a way to subscribe for presence and dialog event from asterisk to kamailio?
13:13.39*** join/#asterisk brad_mssw (~brad@66.129.88.50)
13:14.26*** join/#asterisk cresl1n (uid299068@asterisk/libpri-and-libss7-expert/Cresl1n)
13:14.26*** mode/#asterisk [+o cresl1n] by ChanServ
13:19.29SamotNot without some serious coding.
13:19.30*** join/#asterisk pchero (~pchero@87.213.247.82)
13:20.57solomaSamot: What do you propose?
13:21.18Samotsoloma: You would have to take the SUBSCRIBE from the device at the Kamailio level and have it register to the watchters via Kamailio...
13:21.35SamotThen use the UAC module to send another SUBSCRIBE message to Asterisk.
13:21.59solomaIt is a little bit different from my case.
13:22.04SamotSo that Asterisk will send the NOTIFY to Kamailio and then you'll need to take that NOTIFY and process it to update all the watchers that are subscribed to it.
13:22.07SamotOr...
13:22.27SamotYou can do what I do.
13:22.46solomaI have devices registered at Kamailio, and the current dialog and presence states are stored here.
13:23.01solomaAnd I need to populate them to Asterisks
13:23.19SamotThen you're writing code for this.
13:23.25SamotJust as I outlined above.
13:25.00SamotJust one small problem to keep in mind. Kamailio doesn't do outbound REGISTER/SUBSCRIBEs.
13:25.08solomaI already have that. I'm simply update states within pua_publish when I need to change states FROM asterisk.
13:25.20solomaThere is no problem.
13:25.46SamotIn order for Asterisk to update you on a device state, the Hint needs to be SUBSCRIBEd to.
13:25.55SamotWhich means Kamailio is going to have to do that.
13:26.22SamotBut it doesn't so you have to deal with the workaround.
13:27.04solomaFor example, I want to get devices states with simple command from asterisk dialplan
13:27.12SamotThat's AMI
13:28.01solomaSo, there is no other, only push events to some app and updated device stated with setdivstate action?
13:28.02*** join/#asterisk dandann00dle (uid120491@gateway/web/irccloud.com/x-xxumigmbidaluvdp)
13:28.11SamotSigh.
13:28.23*** join/#asterisk elcontrastador (~textual@70-90-215-98-BusName-ca.sacra.hfc.comcastbusiness.net)
13:28.33SamotIn order for Asterisk to automatically update and send a NOTIFY for a device/hint...
13:28.38SamotIt needs to be SUBSCRIBEd to.
13:28.54SamotOtherwise you need to use an AMI event listener for device state event changes.
13:28.57solomaBut I cannot finf how to subscribe asterisk to kamailio
13:28.57fileSamot: soloma is referring to the reverse I think
13:29.05SamotNo.
13:29.19SamotHe wants to use Kamailio for Presence/Watchers.
13:29.36SamotAnd let Kamailio push those NOTIFYs and handle the SUBSCRIBEs.
13:29.38solomaAnd as publisher
13:29.45*** join/#asterisk u0m3 (~u0m3@82.76.83.7)
13:29.51solomaok.
13:29.53solomaSTOP
13:29.55SamotSo in order to get the device states from Asterisk...
13:30.10filethere is no included integration to allow such information from Kamailio to be pushed into Asterisk for usage
13:30.18SamotRight
13:30.32Samot9:26:20 AM <Samot> But it doesn't so you have to deal with the workaround.
13:30.43solomacrap.
13:30.55SamotWhich is what I've been trying to explain.
13:31.55solomaI think that it will be expensive to habdle each event and publish state from AMI.
13:32.00SamotYou can create a Hint in Asterisk that can be SUBSCRIBEd to OR you can use an AMI even listener to get the states.
13:32.45solomae.g. '1001' =>         hint: PJSIP/proxy-admin/sip:1001@admin.example.com:5060, [exten_test.conf:12]
13:32.55solomaIt does not work.
13:33.07SamotDid you SUBSCRIBE to it?
13:33.32SamotThere is a third option.
13:33.40solomaDo you mean to send subscribe from kamailio?
13:33.45SamotYES
13:34.13solomaI need send event in reverse. From Kamailio to Astersik
13:34.20Samot9:21:34 AM <Samot> Then use the UAC module to send another SUBSCRIBE message to Asterisk.
13:34.32SamotHuh?
13:34.38fileKamailio is the presence source in soloma's case, not Asterisk
13:34.44solomayeap
13:34.46SamotI know.
13:34.57filebut they want to be able to push the calculated presence information in Kamailio to Asterisk
13:35.06solomano
13:35.10solomabackward
13:35.34filethis is too confusing, I give up
13:35.36solomasorry. file is RIGHT
13:35.50solomafrom Kamailio to Asterisk ))))
13:35.57SamotWhy?
13:36.23solomathey are helpful in some application that required to skip busy users.
13:36.46solomaI think that the best way will be using FUNC_ODBC and database function
13:36.53SamotWait...
13:37.09SamotDo you have individual peers/endpoints set up on Asterisk?
13:37.41solomaNo. It is just media/application. All registration is handled by Kamailio
13:37.51SamotThen it's not going to work.
13:38.11solomawhat exactly?
13:38.14SamotThere's nothing on Asterisk for it to care about a "device" state.
13:39.21Samot9:32:44 AM <soloma> e.g. '1001' =>         hint: PJSIP/proxy-admin/sip:1001@admin.example.com:5060, [exten_test.conf:12]
13:39.40SamotIf there is no PJSIP endpoint 1001, not a thing is going to update that hint. There's no "device" to update.
13:41.17SamotThe only place that is going to know if that device is "busy" is Kamailio by checking if the device has an active INVITE dialog happening.
13:42.14solomaI think that it is the better way . Just use func_odbs and function that calculates state
13:42.28solomabased on presensity table
13:43.02SamotOr you can use AMI and the AstDB and have Kamailio fire off an AMI action to update the AstDB with the device state.
13:43.12SamotAnd then you can look in the AstDB for the current state.
13:43.20solomait won't load system as updates through AMI on each event.
13:44.05solomaThe only thing I'm worrying about is queues module.
13:44.18SamotYou need actual endpoints.
13:44.59SamotI just create an endpoint on Asterisk that I associate to the user on Kamailio.
13:45.19solomaok. It works?
13:45.20SamotI let Asterisk deal with device states/BLF updates.
13:45.39SamotYes. I create a static contact that points to the user on Kamailio.
13:46.02SamotWhen that endpoint is Dial()'d Asterisk updates the Hint.
13:46.03solomaand you see the state of device at asterisk?
13:46.13solomaHmm
13:46.32SamotWhich sends the NOTIFY to Kamailio. Kamailio in turn just does a lookup() for the user and then sends the NOTIFY to the device.
13:46.36Samotor devices.
13:46.43SamotDepending on how many contacts are registered.
13:46.59SamotWhen the device sends the SUBSCRIBE, I just route it to the associated endpoint on Asterisk.
13:47.30SamotIt was too much a PITA to get Presentity to play middle man.
13:47.31solomaNo. It won't work for me.
13:47.47SamotPlus it allows Asterisk to monitor the state of each endpoint.
13:47.51SamotFor things like Queues.
13:48.31solomaI have a bunch of asterisks behind Kamailio
13:48.38SamotSo do I.
13:48.57SamotMost of them in a multi-tenant setup on Asterisk.
13:49.25solomaHow about sharing this status between asterisks?
13:49.30solomaCorosync?
13:49.41SamotNope.
13:49.48soloma?
13:49.48SamotI don't bounce them around systems.
13:50.00SamotThere are primary systems then there are backups.
13:50.05solomaUnfortunatelly I do.
13:50.08SamotI don't "load balance" like that
13:50.13SamotBecause, why?
13:50.43solomaTo avoid problems with scaling system horizontally.
13:50.51SamotIt's 2018.
13:50.54SamotVMs.
13:50.58solomayeap
13:51.09SamotFirst, my boxes where built with a cap.
13:51.15SamotX user/Y Calls, etc.
13:51.32SamotWhen that cap gets to be over 80% full...
13:51.41SamotI schedule 15 minutes to resize the system.
13:53.12solomaOk. But, in this 15 minutes, do you will have a problem with states and application availability?
13:53.25SamotNo.
13:53.38Samot9:49:59 AM <Samot> There are primary systems then there are backups.
13:53.42sibiriawe scale stuff like this horizontally instead of vertically, to avoid downtime on any single machine unless necessary
13:53.57solomaso do I
13:54.16*** join/#asterisk waldo323 (~waldo323@75-151-31-89-Michigan.hfc.comcastbusiness.net)
13:54.24solomaI do not want to worry that some conference or parking lot became unavailable
13:54.30SamotWell
13:54.38sibiria(not that we ever really need to do much scaling - asterisk, the way we use it, is incredibly resource-efficient)
13:54.40SamotAt 5am, it is generally not a concern.
13:54.55SamotPlus, they move to the _backup_ system.
13:55.01solomaOf cource it is possible to move services such those to a dedicated server
13:55.01SamotWell they don't.
13:55.06SamotThey're on Kamailio.
13:55.35solomaConferences& Parked calls?
13:55.42SamotHuh?
13:55.49SamotI have a BACKUP of the PRIMARY system.
13:56.04SamotIf primary system go buh-bye, Kamailio flips them to the backup.
13:56.40SamotWill calls go down? Sure.
13:57.20SamotI also said I do my updates at like 5AM.
13:57.52SamotI also do silly things like send Maintenance Notices to the end users in advanced.
13:57.59solomaI'm saying about case when you scale asterisks dynamically. Based on your actual load
13:58.19Samot"Hey, going to be doing updates between 5AM and 5:30AM. Could (or will be) X amount of downtime."
13:58.31SamotI don't scale "dynamically"
13:58.46SamotI setup a system that can support X Y and Z
13:59.00solomaI understand. I have another case.
13:59.23solomaI need to have ability to shut off 3 of 5 asterisk by night.
13:59.58SamotYou mean shut off the servers or just stop Asterisk from running?
14:00.33solomashut off server. Imagine that system is deployed on AWS.
14:00.53SamotSo you want to shut down the server to save on billable resources?
14:01.43solomaYes.
14:02.16solomasibiria: Do you have something like I described?
14:02.43sibiriasoloma: no we run the servers 24/7, but i do understand your concern, especially since you're using AWS which is expensive as hell
14:03.05SamotAnd a poor choice for running SIP services in general. IMO.
14:03.20SamotSo are you Kamailio boxes on AWS?
14:03.22solomaIt is requiments of few customers.
14:03.26SamotSo are your Kamailio boxes on AWS?
14:03.33sibiriasoloma: you could start with moving from on-demand to reserved. it will reduce your costs a lot
14:03.52solomaI now
14:03.59solomaI know
14:04.00SamotSo are your Kamailio boxes on AWS?
14:04.34solomaNo. Primary deal is just scalable multitenant. AWS was asked by few customers.
14:04.53SamotSo are these 5 Asterisk boxes the customers?
14:06.04solomaSome of sysytems will be customerrs and hosted on their sites.
14:07.24SamotI personally wouldnt do daily power downs and startups
14:08.13SamotYou are asking for trouble.
14:08.59fileit takes a lot of work to do it right, in the end
14:09.08SamotNot to mention the added costs
14:09.09solomayes...
14:10.07SamotBecause if you power down the system and dont have Elastic IPs....
14:10.32SamotYou might end up with a different public ip when you power up
14:10.45solomaI was thinking about role-based system. Which is much more simplier.
14:11.35solomaNo. Dummy load balancer <-> kamaili+failover one <-> asterisks as media/application servers
14:12.05SamotNo to the ip?
14:12.37solomaPablic IP is bound to load balancer
14:12.51SamotOn AWS?
14:13.52solomaAWS is one of the cases which a far away from me now )))) it was just extreme example
14:14.07SamotOk but i was refering to tgat
14:14.25*** join/#asterisk jjg (~clh@75-147-197-114-Atlanta.hfc.comcastbusiness.net)
14:14.55SamotIf you do this on AWS and are going to power down instances..you need Elastic IPs to ensure the public ip is always the same when they power back up
14:15.04solomaLoad balancer on Elastic IP, PROXY/REGISTRAR Kamailio could have dynamic IP public IP
14:16.49SamotSo Kamailio will be on AWS
14:18.36solomaEnywhere. IThere was a few requests about using system on AWS.
14:19.57Samot10:11:34 AM <soloma> No. Dummy load balancer <-> kamaili+failover one <-> asterisks as media/application servers
14:19.59solomaI do not undestand that. Because there is billable traffic besides EC2 instances.
14:20.10Samot^^ In that scenario, Kamailio is on AWS.
14:20.32soloma)))
14:20.32SamotAWS just doesn't give you public IPs.
14:21.03SamotThe public IP an EC2 instance is assigned when it is powered up is Dyanmic.
14:21.06SamotThe public IP an EC2 instance is assigned when it is powered up is Dynamic.
14:21.14solomaI know!
14:21.51SamotSo in the context of doing this on AWS there are some considerations that need to be kept in mind.
14:22.08solomaThe system is not going to be used espesially at AWS. As I mentioned, we had requests from customers about ability to host it there.
14:22.25SamotThe powering down of systems will lose their public IP unless it is an Elastic IP.
14:22.33solomaElastic IP is cost $3 per month
14:22.45SamotAdditionally, running Kamailio on AWS means that it is now behind NAT.
14:22.58solomaOnly load balancer requires for static IP address.
14:23.10solomasymmetric NAT
14:23.12SamotSo Kamailio will need to be setup not only to advertise it's public IP
14:23.55SamotBut also to use that IP as it's "socket" IP instead of the private IP it will be bound to. So that when Kamailio sends out requests it has the proper IP populated.
14:26.44solomaSamot: please, forget about AWS. I need to make a lot of other things before start thinking about AWS deployment
14:28.02solomaI have a wroking config of Kamailio and Freeswitch somewhere. Honestly, I did not test it well. And it was a long ago.
14:30.22solomaI've just remembered one presentation from kamailio world. Which can help to make more efficient device state resolving.
14:30.39solomaIn the queue module
14:31.35SamotWell was the presentation on FreeSWITCH or Asterisk and Queues?
14:34.30solomaasterisk and queues
14:35.45sibiriaelastic IPs are free while connected. they only cost while reserved but not allocated or connected to a powered-down instance
14:36.35sibirianot really a cost to consider if you intent to only have those machines turned off 8 hours per day
14:36.38sibiriaintend*
14:37.30SamotSure but then you have that whole, powering up/down daily thing going on.
14:37.51solomahonestly, I do not understand reason to host system on aws. but its ability was requested.
14:37.53SamotSomeone in #freepbx thought it was a good idea. Since the office was close, just turn off the server each night...
14:38.05SamotUntil one morning, the instance wouldn't boot back up.
14:38.29sibiriasoloma: surely because of its popularity. people without insight in the product still conflate it with quality
14:38.33solomaDon't touch if works
14:39.02sibiriato amazon's defense, AWS is a much better choice than GCE for many reasons
14:39.14SamotSure.
14:39.25SamotBut as someone who is providing voice services to customers...
14:39.36SamotWhy would you set your voice platform up in the cloud behind NAT?
14:39.46*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
14:39.56solomasome regulations acts, etc... of cource there could be reasons for enterprise or govs
14:41.16*** join/#asterisk rmudgett (rmudgett@nat/digium/x-zgkovsorpnysrwnr)
14:41.16*** mode/#asterisk [+o rmudgett] by ChanServ
14:43.58solomaSamot: I think that problem with powered off machine has a simple cause...
14:44.40*** join/#asterisk pchero (~pchero@87.213.247.82)
14:48.56solomasibiria: you wrote that you're using horizontal scaling. how do you resolve states sharing?
14:49.49solomasibiria: or you route calls to exact asterisk?
14:53.38*** join/#asterisk samwierema (~samwierem@195.240.143.134)
14:56.37*** join/#asterisk samwierema (~samwierem@195.240.143.134)
15:03.41sibiriasoloma: for inbound calls we use route53 (aws) to manage distribution/failover. as for outbound calls our application runs in parallel on all available machines; it scales automatically as per us just firing up one more instance
15:05.26sibiriaand, equally, if one machine suddenly dies it just means we're running with less total capacity until the machine is up again
15:14.32*** join/#asterisk pigpen (~mark@216-177-181-17.block0.gvtc.com)
15:14.40solomasomething likes I'm trying to make now, but I guess  you have the specific application.
15:17.33pigpenSo, I have a customer who decied to go with a Mitel solution.  They are in South Dakota, I'm in Texas, so I understand wanting local support.
15:17.58pigpenA feature they "touted" was called "Hot Desking".
15:18.42*** join/#asterisk jjg (~clh@107-202-133-88.lightspeed.tukrga.sbcglobal.net)
15:18.54*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
15:18.54pigpenSo how it works, is in short, a call comes into the system, and rings both the desk phone and their cell.  You answer the cell.  You can then hit a button or exten and "pull" it to the desk phone.
15:19.18pigpeneasy.  I figure that part out.
15:19.38pigpenBut the "push" part it a little more tricky.  Or I'm making it more difficult than it should be.
15:19.43*** join/#asterisk K0HAX (~michael@gateway/tor-sasl/k0hax)
15:20.20pigpenSo with the call activly on the desk phone, they have a "push" button.  The call is "seamlessly" transfered/bridged to the cell.
15:21.02pigpenTiming has to be right for the far end not to notice, but it seems the call must be answered at the cell before the call is bridged and send away from the desk phone.
15:21.31pigpenideas?
15:22.26SamotYou could probably setup an In-Call feature that calls the cell phone via an Originate / Local channel and when the cell phone is answered trigger an AMI action to Redirect / bridge the call to the cell phone channel.
15:23.30SamotThe program a softkey on the phone that has that feature code+destination number( or lookup the destination number based on the user's CID)
15:24.18SamotProbably do the same thing in reverse but would have to use the actual feature code since it's a cell phone..
15:24.20pigpenyeah.  I like that.  I was coming up with pieces of that, but not put together.  I was thinking of an "in call" feature too.
15:25.34pigpenPulling the call back is pretty easy.  in the dialplan I just grab the associated channel and bridge it back to the desk phone.
15:26.23pigpenI havne't done anything with AMI.  I've been more old school with asterisk.  May be a good time to play.
15:27.33SamotAMI is as old school as it gets.
15:27.48SamotARI would be the new school.
15:30.08pigpenMaybe I'm just getting my acronyms wrong.  ie: I spend most of my time in extensions.conf since 2006-2007.  If this is amy then, yes.  AMI.
15:33.16pigpenheh, just googled AMI.  Yeah, I've used that mostly for school districts processing bells and announcements.  dam handy.
15:47.57*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
15:48.49*** join/#asterisk hehol (~hehol@gatekeeper.loca.net)
15:50.52*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
15:51.28*** join/#asterisk elcontrastador (~textual@70-90-215-98-BusName-ca.sacra.hfc.comcastbusiness.net)
16:03.51*** join/#asterisk dakudos (~dakudos@c-73-243-106-97.hsd1.co.comcast.net)
16:06.06*** join/#asterisk kharwell (~kharwell@67.231.202.3)
16:06.06*** mode/#asterisk [+o kharwell] by ChanServ
16:25.27*** join/#asterisk Oatmeal (Suzeanne@gateway/vpn/privateinternetaccess/suzeanne)
16:29.13*** join/#asterisk Chotizei (chotaire@unaffiliated/chotaire)
16:35.40*** join/#asterisk Cory (~Cory@unaffiliated/cory)
16:39.06*** part/#asterisk kharwell (~kharwell@67.231.202.3)
16:57.21*** join/#asterisk SeRi (~wtf@unaffiliated/seri)
16:58.20*** join/#asterisk SeRi (~wtf@unaffiliated/seri)
17:01.06SeRiPenguin: whats going on man. Is been some time.....
17:04.02*** join/#asterisk awkwardpenguin (~awkwardpe@cpe-172-118-246-147.socal.res.rr.com)
17:12.07*** join/#asterisk russellb (~rustlebee@redhat/russellb)
17:12.07*** mode/#asterisk [+o russellb] by ChanServ
17:17.00*** join/#asterisk tripleslash (~triplesla@unaffiliated/imsaguy)
17:18.20*** join/#asterisk tripleslash (~triplesla@unaffiliated/imsaguy)
17:48.16PenguinSeRi: Hey!  Where you been?
17:50.53SeRiPenguin: dude!
17:51.03SeRibeen around and about!
17:51.05SeRiLOL
17:51.22SeRiPenguin: how u been bro?
17:53.18*** join/#asterisk tafa2 (~tafa2@t.ldn.dsrtnet.com)
17:53.35PenguinTypical stuff here.
17:53.47SeRiI hear that
17:54.00SeRiI was in and out... never saw you or dijib online
17:54.06SeRiso I just quit
17:54.07SeRiLOL
17:54.12SeRiStill using asterisk though
17:54.34SeRiyou going to laugh
17:54.54SeRiI just upgraded from 1.8 to 13 and I am still needing to catch up
17:54.55SeRiLOL
17:57.57SeRimoved everything from oVirt to KVM (plain KVM) and shit just went to hell
17:57.58SeRilol
17:59.29*** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net)
18:15.00*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)
18:16.14*** join/#asterisk defsdoor (~Andrew@cpc120600-sutt6-2-0-cust232.19-1.cable.virginm.net)
19:13.47*** join/#asterisk setham (~textual@unaffiliated/setham)
19:23.29*** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net)
19:40.26*** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net)
19:41.23*** join/#asterisk adhawkins (~adhawkins@musicbrainz/user/adhawkins)
19:42.27*** join/#asterisk fonefreak (~root@c-76-105-87-190.hsd1.ga.comcast.net)
19:49.38*** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net)
20:28.51*** join/#asterisk wakko1 (~wakko@176.164.185.84)
20:48.25*** join/#asterisk Penguin (~xwQ5kwYl6@our.systems.are.full.of.penguins.at.penguinsystems.net)
21:00.20*** join/#asterisk miralin (~Thunderbi@194.8.128.68)
21:10.07*** join/#asterisk yokel (~yokel@unaffiliated/contempt)
21:15.29*** join/#asterisk [TK]D-Fender (~joe@64.235.216.2)
21:24.35*** join/#asterisk Jesterboxboy (~Thunderbi@84-115-150-8.cable.dynamic.surfer.at)
22:06.19*** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca)
22:49.35*** join/#asterisk forgotmynick (uid24625@gateway/web/irccloud.com/x-zgtwzfhvkezeuyhs)
23:27.52*** join/#asterisk jjg (~clh@mobile-166-172-59-241.mycingular.net)
23:37.54*** join/#asterisk cemotyz09 (~cemotyz09@cpe-70-121-128-59.satx.res.rr.com)

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