| 00:05.50 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 00:21.15 | *** join/#asterisk drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 00:49.07 | *** join/#asterisk spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
| 02:24.41 | *** join/#asterisk MillerBoss (~shit@your.mom.loves.millerboss.com) |
| 02:39.21 | *** join/#asterisk MillerBoss (~shit@your.mom.loves.millerboss.com) |
| 03:21.07 | *** join/#asterisk lankanmon (~LKNnet@CPEb4fbe4e331bd-CM64777d632380.cpe.net.cable.rogers.com) |
| 04:01.35 | *** join/#asterisk MillerBoss (~shit@your.mom.loves.millerboss.com) |
| 04:20.53 | *** join/#asterisk tsal_ (~tsal@i59F5201C.versanet.de) |
| 04:23.23 | *** join/#asterisk tsal- (~tsal@i59F52E2E.versanet.de) |
| 04:26.11 | *** join/#asterisk tsal (~tsal@i59F5F893.versanet.de) |
| 04:34.10 | *** join/#asterisk EmleyMoor (42b789682f@firthpark.tinsleyviaduct.com) |
| 04:39.51 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.66) |
| 04:42.24 | *** join/#asterisk tsal_ (~tsal@i59F5F607.versanet.de) |
| 04:47.55 | *** join/#asterisk tsal (~tsal@i59F4AC46.versanet.de) |
| 04:50.22 | *** join/#asterisk tsal_ (~tsal@i59F528F2.versanet.de) |
| 05:18.32 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 05:26.49 | *** join/#asterisk mir100 (~Vladimir@207.237.220.139) |
| 05:32.19 | *** join/#asterisk tsal (~tsal@i59F4A2F3.versanet.de) |
| 05:35.37 | *** join/#asterisk tsal (~tsal@i59F4A2F3.versanet.de) |
| 05:39.08 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
| 05:41.59 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.81) |
| 06:25.00 | igcewieling | Samot: you around? |
| 07:52.45 | *** join/#asterisk sinaowolabi (~Sina@102.134.114.1) |
| 08:07.56 | *** join/#asterisk drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 08:17.28 | *** join/#asterisk lankanmon (~LKNnet@CPEb4fbe4e331bd-CM64777d632380.cpe.net.cable.rogers.com) |
| 08:59.11 | *** join/#asterisk rpifan (~rpifan@p200300d26700db44d1603b1cfbf16854.dip0.t-ipconnect.de) |
| 09:05.20 | *** join/#asterisk CatCow97 (~mine9@c-73-96-109-206.hsd1.or.comcast.net) |
| 10:20.56 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 10:37.59 | *** join/#asterisk Grommish_ (~quassel@dsl-50-5-33-79.fuse.net) |
| 11:05.30 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.66) |
| 11:08.02 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.66) |
| 11:21.32 | Samot | I am now. |
| 11:31.09 | *** join/#asterisk pa (~pa@unaffiliated/pa) |
| 11:35.12 | pa | any user of chan_dongle here? i know it's community so i don't expect to find many |
| 11:35.35 | pa | the problem i'm seeing is now that at machine reboot the device is properly picked up by the kernel, but asterisk doesn't see it connected |
| 11:35.43 | pa | i even tried to "soft reset" the usb, but nothing |
| 11:35.56 | pa | i wonder if sending an ATZ will help |
| 11:38.36 | pa | interesting that i can see an avalance of communication if i socat into that tty |
| 11:38.43 | pa | and the device replies alright |
| 11:38.49 | pa | not sure what's wrong with chan_dongle |
| 11:40.00 | pa | ok something else is weird here.. asterisk keeps restarting.. i suppose systemd does it |
| 11:40.03 | pa | but why? |
| 11:43.23 | pa | systemd[1]: asterisk.service: Start operation timed out. Terminating |
| 11:43.24 | pa | hmmm |
| 12:29.43 | *** join/#asterisk sekil (~sekil@nat-73.net011.net) |
| 12:47.48 | *** join/#asterisk paulgrmn (~paulgrmn@c-98-250-183-21.hsd1.mi.comcast.net) |
| 12:52.18 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 13:00.45 | *** join/#asterisk pa (~pa@unaffiliated/pa) |
| 13:09.13 | *** join/#asterisk sinaowolabi (~Sina@41.190.30.106) |
| 13:10.53 | *** join/#asterisk jkroon (~jkroon@165.16.204.107) |
| 13:24.19 | *** join/#asterisk MarcinWieczorek_ (~marcin@212.182.24.81) |
| 13:28.37 | *** join/#asterisk AsteriskRoss (~AsteriskR@r01.nt-r1.nor.gb.voicehost.co.uk) |
| 13:49.25 | *** join/#asterisk MarcinWieczorek (~marcin@212.182.24.66) |
| 13:53.53 | *** join/#asterisk Janos (~textual@201.204.94.76) |
| 14:02.01 | *** join/#asterisk MarcinWieczorek_ (~marcin@212.182.24.81) |
| 14:07.01 | *** join/#asterisk adeel (~adeel@fw1.ridgeway.scc-zip.net) |
| 14:17.05 | DanFromUK | Hi. Has anyone had issues with Polycom VVX phones incorrectly handling REGISTER OK packets when more than one contact is allowed for those SIP credentials? |
| 14:18.11 | DanFromUK | The Polycoms dont renew their registration in time so they keep expiring on the Asterisk server. |
| 14:18.27 | DanFromUK | I think the Polycom is using the expire time of the other contact which seems to be longer |
| 14:26.37 | Samot | What makes you think that? |
| 14:26.48 | Samot | Because I haven't experienced that. |
| 14:27.21 | *** join/#asterisk tips (~tips@pool-173-72-12-154.cmdnnj.fios.verizon.net) |
| 14:30.38 | DanFromUK | @Samot I cannot explain why the Polycoms are not re-registering before the expiry. They just seem to be getting the expiry time wrong. And then I found this, https://support.onsip.com/hc/en-us/articles/204028710-Polycom-Multiple-Contacts-Registration-Bug |
| 14:31.08 | DanFromUK | But that link relates to a very old firmware version, so I'm just using it as a possible reason, not a definitive reason |
| 14:31.35 | DanFromUK | Just moving the 2nd contact over to its own SIP account for testing to see if that resolves the issue. |
| 14:33.31 | Samot | What? |
| 14:33.48 | Samot | Are you talking about a Polycom with multiple accounts on IT |
| 14:34.09 | Samot | Or are you talking about multiple Polycoms on an AOR with multiple contacts? |
| 14:34.09 | DanFromUK | No. One Polycom deskphone + one mobile softphone. |
| 14:34.22 | Samot | OK the expiry time is set by the device. |
| 14:34.33 | Samot | So each device can have their own expiry time |
| 14:34.42 | *** join/#asterisk kharwell (uid358942@gateway/web/irccloud.com/x-cygkwhwcflzkttkm) |
| 14:34.42 | *** mode/#asterisk [+o kharwell] by ChanServ |
| 14:35.08 | Samot | You have a min expire time which means if you have that as 60 and the device sends 30, it will use 60 |
| 14:35.10 | DanFromUK | Yes, but from that link, it seems that there was previously a bug in the Polycom firmware and it was using the expiry time of the other device. |
| 14:35.16 | Samot | But if the device sends 80, it will use 80. |
| 14:35.23 | Samot | How? |
| 14:36.25 | Samot | And I'm not even going to address that link. |
| 14:36.32 | Samot | That is from 2009 on the 2.x software. |
| 14:36.46 | Samot | Completely and utterly irrelvant. |
| 14:37.50 | Samot | Plus that is from OnSIP talking about the issue THEY are having. |
| 14:37.56 | Samot | So it's not a Polycom bug. |
| 14:38.45 | Samot | DanFromUK: So what issue are you having? |
| 14:38.47 | DanFromUK | No idea. But I dont consider that link irrelevant as it describes an identical issue OnSIP had with a version of Polycom firmware. Although I'm running the latest version, this issue appears to be identical and only started since I upgraded to the latest firmware. |
| 14:40.00 | DanFromUK | @Samot: Any Polycom phones, that have also have a softphone registered to that SIP account, are re-registering too late and therefore expiring on the Asterisk server. |
| 14:40.45 | DanFromUK | But any Polycom phones that do NOT have a softphone reigstered to their SIP account, are functioning normally. Same config for all Polycom phones, with the exception of their SIP credentials. |
| 14:41.52 | Samot | What softphone are you using? |
| 14:42.01 | Samot | Because I have VVX's and Bria and I don't have this issue. |
| 14:42.01 | DanFromUK | Bria Stretto |
| 14:43.43 | Samot | Show what you see in Asterisk |
| 14:43.51 | Samot | Where contacts are expiring.. |
| 14:44.53 | DanFromUK | Oddly, the Asterisk logs don't show the "is not Unreachable" in these events. I just see loads and loads of "is now Reachable" for the affected extensions. But if I do "pjsip show endpoint XXX" then I can see that the Polycom keeps disappearing. |
| 14:45.00 | DanFromUK | and reappearing |
| 14:45.18 | Samot | No. |
| 14:45.27 | Samot | pjsip show aor XXX |
| 14:45.32 | Samot | pjsip show contacts |
| 14:46.01 | DanFromUK | the contacts are listed at the top of the "pjsip show endpoint XXX" output. |
| 14:46.15 | Samot | What is the AOR config? |
| 14:46.31 | DanFromUK | I've now moved an app away from a polycom's extension, and that seems to have settled the problem. |
| 14:46.33 | DanFromUK | 1sec |
| 14:47.04 | Samot | Also, showing the endpoint is a summary of the AOR/contacts. |
| 14:47.20 | DanFromUK | https://www.irccloud.com/pastebin/taYhR5AG/ |
| 14:47.34 | *** join/#asterisk bford (uid283514@gateway/web/irccloud.com/x-dqylfwwnjismlpon) |
| 14:47.34 | *** mode/#asterisk [+o bford] by ChanServ |
| 14:48.55 | DanFromUK | Nothing is output to the asterisk verbose 3 logs when the Polycom contact expires. Usually, I'd expect to see "is now Unreachable"? |
| 14:52.52 | DanFromUK | This is from another extension. It is currently showing both Polycom and Bria registered. |
| 14:52.56 | DanFromUK | https://www.irccloud.com/pastebin/3ss2DuTd/ |
| 14:53.44 | DanFromUK | But in a moment, the 2nd contact (polycom at 185.XX.XX.179) will disappear from that output, but no "is now Unreachable" is displayed by the Asterisk verbose logs. |
| 14:54.28 | DanFromUK | Again, this is identical to the old issue that OnSip described in their post. |
| 14:55.42 | DanFromUK | But. you've answered my question, you aren't experiencing the same issue, with the same setup |
| 14:56.14 | DanFromUK | @Samot: Actually, if possible, could you confirm the firmware version you are currently running on your VVXs? |
| 14:56.30 | Samot | The latest. |
| 14:57.16 | Samot | What is the expire time set in the polycom? |
| 14:58.49 | DanFromUK | I think I've got confirmation now from the Polycom's logs. |
| 14:58.53 | DanFromUK | https://www.irccloud.com/pastebin/y3gwsHzH/ |
| 14:59.33 | DanFromUK | The OK shows that the Bria is expiring in 816 seconds. But the last line of the Polycom's logs show that it's taken that expiry time for itself. |
| 15:00.12 | DanFromUK | Maybe it's a NAT issue since the Polycom doesn't realise that the 185.58 address is itself. It's just taking the first Contact's expiry time. |
| 15:01.41 | Samot | That's not an answer to my question. |
| 15:01.50 | Samot | What is the expire time configured for in the Polycom. |
| 15:03.45 | DanFromUK | 300 seconds. |
| 15:04.10 | DanFromUK | The OK response to the register I posted above, shows that the Polycom contact has 299 seconds remaining. |
| 15:04.27 | DanFromUK | But the last line of the Polycom logs shows that it thinks there are 816 seconds remaining. |
| 15:04.41 | Samot | Either raise it in the polycom or lower it Asterisk. |
| 15:04.43 | DanFromUK | It's ok. I've sent this to our Polycom distributors now and they are going to test |
| 15:05.20 | Samot | Also, dude. |
| 15:05.27 | Samot | 13.7.1? |
| 15:05.31 | Samot | It was known to have bugs. |
| 15:05.47 | file | newer versions return the IP address/port they gave, and not the NAT one |
| 15:05.49 | Samot | So, yeah. Try to get on something that's not a couple years old and had a bug. |
| 15:06.15 | Samot | Well 300 seconds on both ends. |
| 15:06.24 | Samot | So it becomes a race. |
| 15:06.54 | Samot | Asterisk could drop it at 300 seconds for Asterisk, which could be off in timing to the Polyco. |
| 15:07.15 | Samot | So the Polycom expires at 300 seconds, sends the REGISTER but oh it's a few seconds slower than Asterisk. |
| 15:07.23 | Samot | Or minutes slower. |
| 15:10.36 | DanFromUK | Asterisk is expiring the Polycom at 300 seconds, but the Polycom doesn't realise this until the expiry time of the other contact. |
| 15:11.41 | DanFromUK | @file: Ah. So that could allow the Polycom to pick up the correct contact? Does the latest v13 release include that change, or do I have to move to the next major Asterisk release? |
| 15:12.27 | file | I believe 13 has it |
| 15:12.42 | *** join/#asterisk Venu (~ven.u@213.177.194.66) |
| 15:15.28 | DanFromUK | Thanks. That's very helpful. I'll try to give it a go. Hopefully I can do it this evening if things are quiet. |
| 15:16.45 | igcewieling | Samot: do you run chr in a KVM VM? |
| 15:17.31 | drmessano | I do |
| 15:18.29 | igcewieling | drmessano: I was hoping to get a dumpxml from a working CHR VM. |
| 15:18.57 | igcewieling | I managed to get it to boot, but not to see the NIC. |
| 15:19.03 | file | Do note 13 goes security only next month |
| 15:19.10 | file | I'll be buying a cake. |
| 15:19.45 | drmessano | Ahhh... Yeah I don't have access to the host. Using Vultr VPSes |
| 15:19.54 | igcewieling | oh, OK. |
| 15:24.07 | igcewieling | WinBox is sort of cool. I've never seen an application so exactly copy a web gui. Other than that I did not find it very useful. |
| 15:25.11 | drmessano | The WebIf is actually a copy of Winbox |
| 15:25.30 | drmessano | I never use the WebIf. Just has some quirks |
| 15:27.16 | Samot | Yes, I run CHR in VMs. |
| 15:27.18 | igcewieling | I really don't see the point of WinBox. Maybe I have filters somewhere, but Winbox was never able to find the hEX box unless I manually input the IP. |
| 15:27.46 | Samot | Did you got to the Neighbors tab? |
| 15:27.55 | Samot | And where were on the same L2 as the hex? |
| 15:28.08 | Samot | And where you on the same L2 as the hex? |
| 15:28.43 | igcewieling | I'd have to open it back up to be sure, but I think I saw the neighbors box, it was empty. Yes, it should be on the same L2 LAN. |
| 15:29.14 | igcewieling | Once I figured out the correct IP and manually input it, then it connected. |
| 15:29.18 | drmessano | I've got a whole network sitting here I am building, accessing all of it via MAC-winbox |
| 15:29.58 | drmessano | Was Port 2-5 of the HEX plugged into the network? |
| 15:30.12 | drmessano | Because port 1 is WAN and firewalled |
| 15:30.17 | igcewieling | drmessano: yes, because I was able to access the web GUI on the router. |
| 15:30.17 | drmessano | With the default config |
| 15:30.23 | drmessano | ok |
| 15:30.29 | igcewieling | drmessano: yes, I figured out about eth1 evenually. |
| 15:33.47 | igcewieling | I really don't care about WinBox. IF the router has enough IP setup to connect with WinBox, then it is setup enough to access the web GUI. |
| 15:35.23 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 15:38.22 | Samot | OK |
| 15:38.36 | Samot | But, this is very important, it is inferior to Winbox. |
| 15:38.54 | igcewieling | In what way? |
| 15:39.24 | Samot | Options not being available. |
| 15:39.31 | Samot | Formatting not the same. |
| 15:39.41 | Samot | In regards to layout and functionality that you can do |
| 15:40.52 | drmessano | Putting something in a box and it failing for an unknown reason. |
| 15:41.08 | igcewieling | drmessano: Huh? |
| 15:41.08 | drmessano | Winbox displays much more verbose errors |
| 15:41.19 | drmessano | Validation of settings |
| 15:41.56 | igcewieling | *shrug* If it becomes a problem, I'll deal with it at that time. The GUI is just for setting the box online enough for me to upload a config file. |
| 15:42.30 | drmessano | There were a number of cases where I tried to input something ROS didn't like into a field and webif was braindead in the error reporting |
| 15:42.49 | Samot | Just learn and love Safe Mode |
| 15:43.07 | igcewieling | safe mode lets me script the setup? |
| 15:43.45 | Samot | Safe Mode is what you enable via Webfig, Winbox or the CLI before you make changes. |
| 15:44.04 | Samot | That way if you are dumped for screwing up something, all the changes made are reverted. |
| 15:44.20 | Samot | And you don't lock yourself out or take it offline |
| 15:44.40 | igcewieling | I assume there is a safe mode in the CLI too? |
| 15:44.53 | Samot | It also will tell someone else who logs in "Hey, safe mode is enabled by another session. You can't do jack" |
| 15:45.03 | Samot | That would be why I had it in the list. |
| 15:45.06 | igcewieling | I'd be happy to give up all GUI if I could have a damn console port. 8-| |
| 15:45.38 | Samot | Again, serial ports are going the way of the dodo |
| 15:45.40 | drmessano | 1995 is over |
| 15:45.58 | igcewieling | No, they are not. Not for commercial/telco grade stuff. |
| 15:46.32 | Samot | OK |
| 15:46.43 | igcewieling | every single router and switch on our network, 200+ of them have console ports. |
| 15:46.46 | Samot | We rarely used serial ports unless it was needed when I was at the LECs. |
| 15:46.48 | Samot | So yeah. |
| 15:47.04 | drmessano | Is there anything where you don't insist you know more than everyone else, even gear thats new to you? JFC |
| 15:47.54 | drmessano | Open the box "I'm an expert now, thx" |
| 15:48.03 | igcewieling | What I know is that console ports saved our ass many many times. |
| 15:48.09 | Samot | Yes, it can. |
| 15:48.12 | Samot | As a backup |
| 15:48.37 | drmessano | So can configuration management |
| 15:51.14 | drmessano | You're really going to hate Mikrotik. I can think of a number of things that are modern enough to be subject of a rant. |
| 15:51.22 | drmessano | So good luck. |
| 15:52.16 | igcewieling | Mostly I dislike the CLI, but that is just because I've spent 20 years using the Cisco/Adtran CLI, not because there is anything wrong with the Mikrotik CLI. |
| 15:53.32 | igcewieling | drmessano: *shrug* We install Adtran 3140/3120s at customers where we might use Mikrotik in the future. If I dislike Mikrotik enough to not use it, we'll just continue to install Adtran routes at the sites. For the cost difference Mikrotik would have to be pretty bad to not be worth it. |
| 15:56.08 | Samot | The CLI is pretty close to Cisco |
| 15:57.14 | drmessano | Oh I don't think it's bad at all. I've sold and deployed lots of Mikrotik kit. Have about 70 devices in the field now, from routers to switches to APs, to LTE boxes and bridges. But most guys stuck 20 years in the past with Cisco and Adtran gear seem to hate it. |
| 15:57.39 | Samot | Or you know, Ubiquity users. |
| 15:57.48 | drmessano | Right |
| 15:57.49 | Samot | It lacks the Clown Key |
| 15:58.10 | igcewieling | drmessano: So far, I'd recommend it to any home type of users. It is a great SoHO router. |
| 15:58.47 | Samot | Its almost like they made the for ISP/WISPs to use as CPEs for their users. |
| 15:58.55 | igcewieling | For my use, I'm still considering things and working out how to adapt out adtran configs. |
| 15:58.58 | sibiria | the one not so great thing about ubiquity's products are that so many of them offer no web-based interface, but demands that you download their smartphone app |
| 15:59.24 | Samot | well based on your use... |
| 15:59.26 | drmessano | Most Ubiquiti requires a controller or clown key |
| 15:59.28 | sibiria | ubiquiti* |
| 15:59.30 | Samot | It's pretty basic. |
| 15:59.31 | igcewieling | I have a PoS EdgeSwitch16 |
| 15:59.48 | Samot | You need a GRE tunnel and some firewall rules. |
| 16:01.01 | sibiria | also, ubi's stuff phones home and was found out to shuttle data other than crashes, contrary to what they publically stated some time ago |
| 16:02.26 | Samot | Well Mikrotik EOL's hardware. |
| 16:02.52 | Samot | But just because they don't make it anymore doesn't mean RouterOS can't work on it anymore. |
| 16:03.15 | Samot | So I can get a 15 yr RouterBoard and put the current version of firmware on it. |
| 16:03.39 | Samot | The hardware becomes my limitations. |
| 16:04.35 | Samot | If I buy the $30 hap mini I can do OSPF, BGP, VRRP, multiple DHCP servers, VLANs, GRE, IPSEC all the fun stuff. |
| 16:05.10 | Samot | But then I'm on low CPU, low RAM, low space device. |
| 16:08.42 | *** join/#asterisk tsal (~tsal@i59F527B2.versanet.de) |
| 16:39.09 | *** join/#asterisk rpifan_ (~rpifan@p200300d26700db09e2a976f1f72ef5d9.dip0.t-ipconnect.de) |
| 16:47.28 | *** join/#asterisk qakhan (~qakhan@50-204-254-11-static.hfc.comcastbusiness.net) |
| 16:47.52 | qakhan | Hi all, can voice mailbox be read-only? |
| 16:48.10 | qakhan | user can hear the voicemail but cannot delete it |
| 16:48.44 | igcewieling | you could chown the relevant message files, but I doubt that is what you are looking for. |
| 16:49.27 | qakhan | user can hear the voicemail but cannot delete it |
| 16:51.29 | *** join/#asterisk AsteriskRoss (~AsteriskR@37.157.48.2) |
| 16:52.24 | Samot | The simple answer to this is: No. |
| 16:52.31 | Samot | It cannot be read only. |
| 16:53.08 | qakhan | ok thaks |
| 16:53.12 | qakhan | ok thanks |
| 16:53.35 | igcewieling | You can send copies of the same voicemail to multiple mailboxes |
| 17:32.57 | *** join/#asterisk tsal (~tsal@i59F4AE7B.versanet.de) |
| 17:39.21 | *** join/#asterisk Milos (~Milos@pdpc/supporter/student/milos) |
| 17:50.06 | *** join/#asterisk tsal (~tsal@i59F4A31E.versanet.de) |
| 17:59.57 | *** join/#asterisk AsteriskRoss (~AsteriskR@37.157.48.2) |
| 18:05.50 | *** join/#asterisk opal (~wowaname@volatile/founder/wowaname) |
| 18:07.10 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
| 18:07.35 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 18:12.38 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 18:12.53 | *** join/#asterisk dacod (~dacod@191.243.8.195) |
| 18:12.57 | *** join/#asterisk sa02irc (~mbax@155-079-043-212.ip-addr.inexio.net) |
| 18:15.14 | *** join/#asterisk tsal (~tsal@i59F52D66.versanet.de) |
| 18:15.57 | *** join/#asterisk dakudos (~dakudos@c-73-229-175-50.hsd1.co.comcast.net) |
| 18:22.16 | *** join/#asterisk dakudos (~dakudos@c-73-229-175-50.hsd1.co.comcast.net) |
| 18:29.49 | *** join/#asterisk dakudos (~dakudos@c-73-229-175-50.hsd1.co.comcast.net) |
| 18:40.47 | eppigy | hello |
| 18:40.47 | eppigy | I am Daver |
| 18:40.47 | eppigy | DAVE |
| 18:42.32 | *** join/#asterisk yuljk (~yuljk@unaffiliated/yuljk) |
| 18:43.48 | Samot | Dave's not here man. |
| 18:44.25 | *** join/#asterisk yuljk (~yuljk@unaffiliated/yuljk) |
| 18:47.15 | *** join/#asterisk pchero (~pchero@ip-213-127-77-245.ip.prioritytelecom.net) |
| 18:50.30 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 18:54.21 | eppigy | Hi Samot |
| 18:54.23 | eppigy | long time |
| 18:54.34 | eppigy | drmessano: hi doc |
| 19:06.30 | *** join/#asterisk rpifan (~rpifan@p200300d26700db09e2a976f1f72ef5d9.dip0.t-ipconnect.de) |
| 19:08.45 | *** join/#asterisk drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 19:40.24 | *** join/#asterisk sinaowolabi (~Sina@102.134.114.1) |
| 19:42.02 | *** join/#asterisk Jesterboxboy (~Thunderbi@84-115-150-8.cable.dynamic.surfer.at) |
| 19:47.20 | *** join/#asterisk sh_smith (~sh_smith@cpe-172-88-21-24.socal.res.rr.com) |
| 19:51.06 | *** join/#asterisk akp55 (~akp55@c-73-148-15-31.hsd1.va.comcast.net) |
| 19:57.45 | *** join/#asterisk hfb (~hfb@47.139.23.22) |
| 20:06.17 | *** join/#asterisk overyander (~overyande@216.163.24.236) |
| 20:41.05 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 21:28.49 | *** join/#asterisk puzzola (~puzzola@unaffiliated/puzzola) |
| 21:57.55 | *** join/#asterisk paulgrmn (~paulgrmn@c-98-250-183-21.hsd1.mi.comcast.net) |
| 22:25.37 | *** join/#asterisk mir100 (~Vladimir@207.237.220.139) |
| 22:46.49 | *** join/#asterisk tsal (~tsal@i59F52F83.versanet.de) |
| 22:50.12 | *** join/#asterisk ih8wndz (jwpierce3@mail.000.srv.trnkmstr.com) |
| 22:59.15 | *** join/#asterisk SSlater (~simon@203.214.65.15) |
| 23:05.59 | *** join/#asterisk overyander (~overyande@216.163.24.236) |
| 23:10.42 | *** join/#asterisk pchero (~pchero@2a02:a210:2241:6480:4dc5:df3a:1e9f:43be) |
| 23:21.38 | *** join/#asterisk verzo (~verzo@gateway/tor-sasl/verzo) |
| 23:27.04 | *** join/#asterisk scampbell (~scampbell@mail.scampbell.net) |
| 23:40.19 | *** join/#asterisk ih8wndz (jwpierce3@mail.000.srv.trnkmstr.com) |
| 23:49.08 | *** join/#asterisk spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |