| 01:09.24 | *** join/#asterisk-scf-dev leedm777 (~Adium@user-69-73-1-116.knology.net) |
| 02:04.22 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 03:28.32 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 10:08.57 | *** join/#asterisk-scf-dev Qwell (~north@northantara-2-pt.tunnel.tserv3.fmt2.ipv6.he.net) |
| 10:09.51 | *** join/#asterisk-scf-dev kenhunt (~kenhunt@nat/digium/x-nxffeiguepswvnnb) |
| 12:39.35 | *** join/#asterisk-scf-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 12:44.05 | *** join/#asterisk-scf-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 13:27.32 | *** join/#asterisk-scf-dev b3nt_pin (~b3ntpin@142.162.36.51) |
| 13:35.56 | *** join/#asterisk-scf-dev wesphillips (~wphill04@137-237-233-124.harris.com) |
| 13:55.48 | *** join/#asterisk-scf-dev leedm777 (~Adium@nat/digium/x-xyhetiszyhoalkpy) |
| 14:17.30 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 14:18.03 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 14:18.49 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 14:48.16 | *** join/#asterisk-scf-dev icegnome (~blongberg@nat/digium/x-qfvbuywuijcebjun) |
| 14:51.04 | *** join/#asterisk-scf-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 14:59.39 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 15:13.20 | *** join/#asterisk-scf-dev vitreous_oculi (~b3ntpin@142.162.36.51) |
| 16:01.38 | *** join/#asterisk-scf-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 16:19.13 | dms1 | well, it certainly helps to have a previous set of icebox processes not running if you plan to start another set |
| 16:19.30 | dms1 | 5 minutes I'll never get back |
| 16:19.56 | *** join/#asterisk-scf-dev malcolmd (~malcolmd@nat/digium/x-edidgosvytxtwoki) |
| 16:19.56 | *** join/#asterisk-scf-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 16:20.23 | *** join/#asterisk-scf-dev Qwell (~north@pdpc/sponsor/digium/Qwell) |
| 16:20.41 | kpfleming | s/icebox process/asterisk scf service components/ |
| 16:21.01 | dms1 | indeed |
| 17:19.56 | *** join/#asterisk-scf-dev jeffg (~jeffg@pdpc/supporter/professional/jeffg) |
| 18:13.15 | *** join/#asterisk-scf-dev vitreous_oculi (~b3ntpin@142.162.36.51) |
| 19:11.47 | *** join/#asterisk-scf-dev b3nt_pin (~b3ntpin@142.162.36.51) |
| 19:33.39 | dms1 | b3nt_pin: ping |
| 19:34.00 | file | ping him harder! |
| 19:34.05 | b3nt_pin | hi.. 1s phone connection is down |
| 19:34.14 | dms1 | ack |
| 19:34.34 | file | b3nt_pin, you are not having a very good day |
| 19:36.41 | b3nt_pin | no not really |
| 19:42.11 | b3nt_pin | holy cow |
| 19:42.17 | b3nt_pin | I can't link up with vpn |
| 19:42.21 | b3nt_pin | no phone.. |
| 19:42.24 | b3nt_pin | hrmm |
| 19:42.29 | dms1 | must be getting some crazy packet loss |
| 19:42.42 | b3nt_pin | my network apparently is still buggered |
| 19:43.12 | b3nt_pin | trying something else |
| 19:44.24 | file | Skype? |
| 19:44.32 | b3nt_pin | !!!!! |
| 19:44.37 | b3nt_pin | oh wait |
| 19:59.16 | *** join/#asterisk-scf-dev vitreous_oculi (~b3ntpin@142.162.36.51) |
| 20:40.41 | dms1 | late lunch . . bbiab |
| 20:43.41 | *** join/#asterisk-scf-dev file (~file@asterisk/developer-and-muffin-lover/file) |
| 21:23.16 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 21:33.04 | *** join/#asterisk-scf-dev b3nt_pin (~b3ntpin@142.162.36.51) |
| 21:56.40 | b3nt_pin | my network is fixed |
| 21:56.48 | b3nt_pin | I can even make PHONE CALLS !!!! |
| 21:58.44 | dms1 | \ o / |
| 21:58.46 | file | nobody wants to make phone calls |
| 22:08.50 | kpfleming | b3nt_pin: welcome back! |
| 22:16.19 | *** join/#asterisk-scf-dev leedm777 (~Adium@user-69-73-1-116.knology.net) |
| 22:17.56 | *** join/#asterisk-scf-dev vitreous_oculi (~vitreous_@142.162.36.51) |
| 22:27.47 | vitreous_oculi | dms1: how did the failover testing go today? |
| 22:28.28 | dms1 | vitreous_oculi: wow . . that's a name |
| 22:28.34 | dms1 | :) |
| 22:28.42 | vitreous_oculi | hehe.. it's my slashdot handle |
| 22:28.46 | dms1 | I'm right in the middle of it . . give me 5 |
| 22:28.53 | *** part/#asterisk-scf-dev wesphillips (~wphill04@137-237-233-124.harris.com) |
| 22:29.30 | vitreous_oculi | no biggie... just thought I would check in as this is the first moment I've had today where I was starting to relax on the whole "network go boom" thing. |
| 22:30.57 | vitreous_oculi | I have to take the kids to their music lessons, but I'm hauling my mobile gear with me so I'll be working in the lobby |
| 22:34.20 | dms1 | np . . short of it thus far . . most of the replicator configs were missing topic manager proxy info and were generating errors . . easy fix though (not pushed yet) . . had to setup corosync on testsuite-remote-3 and testsuite-remote-4 with a shared ip |
| 22:34.44 | vitreous_oculi | nods |
| 22:34.54 | dms1 | had to download bria so I could configure more than one endpoint on my softphone too |
| 22:36.03 | dms1 | at the moment, something is quirky with the shared ip as I'm not seeing sip traffic hit either of the testsuite remote servers |
| 22:36.40 | kpfleming | topic manager proxies don't need to be configured any longer, the components are able to discover that themselves now, that's why we took them out of the config files |
| 22:37.07 | dms1 | ya, I wasn't sure about that, but the components were complaining about it so I stuck it in there. I'll take it out. |
| 22:37.23 | vitreous_oculi | hrmm |
| 22:37.43 | dms1 | several of the other component configs had the topic manager proxy settings set |
| 22:37.43 | vitreous_oculi | were all of the components complaining or only certain ones... e.g. bridging |
| 22:38.23 | dms1 | not sure if it was all of them (I can confirm real quick if you'd like), but it was certainly a few of them |
| 22:38.26 | dms1 | likely all |
| 22:38.54 | vitreous_oculi | ack |
| 22:42.05 | kpfleming | vitreous_oculi: when you can spare a moment, i have a question for you regarding your ccache-mkshlib branch in the ice integration repo |
| 22:42.33 | vitreous_oculi | ack |
| 22:43.08 | vitreous_oculi | I'm about to make the drive to kid's music, but I'll be back online when I get there. |
| 22:43.44 | file | I doubt kpfleming will be |
| 22:43.45 | kpfleming | probably not |
| 22:43.58 | kpfleming | this can wait until tomorrow anyway |
| 23:02.33 | *** join/#asterisk-scf-dev dms1 (~dms@user-24-214-92-191.knology.net) |
| 23:05.40 | *** join/#asterisk-scf-dev vitreous_oculi (~vitreous_@184.151.115.29) |
| 23:08.41 | *** join/#asterisk-scf-dev dms2 (~dms@user-24-214-92-191.knology.net) |
| 23:13.25 | vitreous_oculi | kpfleming: situated... just pulling down those branches to my notebook |
| 23:15.18 | kpfleming | ahh |
| 23:15.26 | file | over a mobile hotspot... brave |
| 23:15.52 | kpfleming | just wondering sort of ccache install required changing CXX. on our installs ccache is just in the PATH ahead of the actual compiler and no environment variable muckery is required. |
| 23:19.17 | vitreous_oculi | unsure... iirc, the issue was that in our nightly builds, the value of CXX was actually a wrapper ("ccache-c++" or something maybe), so the fix was very much directed at that specific situation. |
| 23:19.35 | kpfleming | ok, will investigate tomorrow, thanks. |
| 23:19.41 | vitreous_oculi | dms2 can confirm or deny that :) |
| 23:19.56 | vitreous_oculi | file: it was pretty fast actually |
| 23:20.54 | vitreous_oculi | I am not a heavy data user on my phone so I am not overly concerned. I think I have 6GB of data a month with my current plan |
| 23:20.59 | vitreous_oculi | I need to use it more |
| 23:28.10 | *** join/#asterisk-scf-dev leedm777 (~Adium@user-69-73-1-116.knology.net) |
| 23:38.57 | *** join/#asterisk-scf-dev icegnome (~blongberg@adsl-98-81-157-105.hsv.bellsouth.net) |
| 23:54.18 | *** join/#asterisk-scf-dev vitreous_oculi (~vitreous_@142.162.36.51) |