00:11.42 | *** join/#asterisk tris (tristan@camel.ethereal.net) |
00:41.58 | *** join/#asterisk spatel (~spatel@pool-96-237-230-175.bstnma.fios.verizon.net) |
00:59.37 | *** join/#asterisk m4rcu5 (nobody@84-106-248-133.cable.dynamic.v4.ziggo.nl) |
01:29.03 | *** join/#asterisk mindthelion (~techquila@116.90.74.243) |
01:44.16 | *** join/#asterisk techquila (~techquila@2407:7000:9125:e400:f1c2:df9f:be37:22a2) |
02:03.42 | *** join/#asterisk MICROburst1 (~Thunderbi@x590c9113.dyn.telefonica.de) |
02:05.28 | *** join/#asterisk mindthelion (techquila@gateway/vpn/protonvpn/techquila) |
02:09.03 | rue_mohr | coppers only good for 300' |
02:09.18 | rue_mohr | fibers fine, not sure on the range for T1 |
02:13.30 | Samot | What? |
02:13.42 | Samot | T1 is copper, DSL is copper. |
02:13.56 | Samot | You can do DSL up to 6,000'. |
02:15.18 | Samot | I mean it's literally call the "last mile" for a reason. |
02:23.39 | Reinhilde | Samot: can either modulation run over a 2 inch thick steel pipe? |
02:24.38 | Samot | I'm not sure I understand the question. |
02:24.43 | Samot | You mean laying over it? |
02:24.47 | Samot | Running through it? |
02:24.52 | Samot | Along side it? |
02:26.06 | Samot | The 300' rule is for Ethernet. for 10/100/1000 speeds. |
02:26.13 | Samot | T1's are not that. |
02:26.26 | Samot | 1.5Mbps |
02:28.01 | *** join/#asterisk techquila (~techquila@2407:7000:9125:e400:f1c2:df9f:be37:22a2) |
02:33.54 | Reinhilde | Samot: So let's say I have 250' of steel 2in by 4in bars. If I have enough of them isolated from each other, can I run T1 or DSL over them, using them as the wires in a phone wire? |
02:34.58 | Samot | No, copper. |
02:36.12 | Reinhilde | Is there something about copper that makes it more suitable than steel? |
02:37.59 | Samot | It handles voltage and data better. |
02:39.28 | Reinhilde | That's very nebulous. |
02:39.40 | Samot | It's highly conductive. |
02:39.46 | Samot | It can power things over it. |
02:39.59 | Samot | Like analog phones etc. |
02:40.17 | Samot | It handles transmission of data over it better. |
02:41.39 | Reinhilde | I know that thicker is not always better, but in this case, if I didn't have copper and only had steel, would making the wire thicker effectively help workaround the deficiency? |
02:41.51 | Samot | Steel is not as conductive. |
02:42.08 | Samot | It wouldn't be able to handle what is needed. |
03:27.44 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
03:38.33 | *** join/#asterisk mindthelion (techquila@gateway/vpn/protonvpn/techquila) |
04:01.23 | *** join/#asterisk techquila (techquila@gateway/vpn/protonvpn/techquila) |
04:07.41 | *** join/#asterisk LiuYan (~NiHola@unaffiliated/liuyan) |
04:28.54 | drmessano | The conductance of steel is so low, that none of the signal would pass from one end to the other |
04:29.11 | drmessano | It would just be very long resistor |
04:30.44 | Samot | ^ That |
04:31.06 | Reinhilde | I have the french guy on ignore |
04:31.22 | Samot | What french guy? |
04:32.01 | Reinhilde | whoever you up-arrowed, truth be told he's probably not french |
04:36.33 | *** join/#asterisk eharris (~eharris@unaffiliated/eharris) |
04:38.31 | rue_mohr | really long resistors are also known for their inductance |
04:38.55 | rue_mohr | if its me, I'm not french |
04:39.13 | rue_mohr | gad I dispise french, but whatever |
04:40.04 | drmessano | Really long conductors show both inductive reactance and capacitive reactance |
04:40.21 | rue_mohr | yes |
04:40.24 | drmessano | But in the context of the question, no, you couldn't use a long piece of steel to pass data |
04:40.42 | drmessano | At least not at the levels provided by your typical provider |
04:40.44 | rue_mohr | indeed, I'm glad I didn't ask that |
04:43.57 | rue_mohr | Obviously, carbon is the best thing to use |
04:44.01 | rue_mohr | (graphine) |
04:49.25 | *** join/#asterisk aness (~aness@cm-84.209.54.51.getinternet.no) |
05:16.18 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
05:39.28 | *** join/#asterisk [TK]D-Fender (~joe@64.235.216.2) |
05:43.39 | *** join/#asterisk sysgrammer (~sysgramme@d205-234-50-53.yt.northwestel.net) |
05:45.57 | *** join/#asterisk overyander (~overyande@209.141.208.197) |
05:47.42 | *** join/#asterisk LiuYan (~NiHola@unaffiliated/liuyan) |
06:38.17 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
06:40.36 | *** join/#asterisk overyander (~overyande@209.141.208.197) |
06:54.38 | *** join/#asterisk jkroon (~jkroon@165.16.203.126) |
07:03.38 | *** join/#asterisk ircarcs (~quassel@169.9.159.77.rev.sfr.net) |
07:14.37 | *** join/#asterisk pchero_work (~pchero@87.213.247.82) |
07:44.09 | *** part/#asterisk LiuYan (~NiHola@unaffiliated/liuyan) |
08:09.17 | *** join/#asterisk tehgooch (tehgooch@unaffiliated/tehgooch) |
08:47.35 | *** join/#asterisk defsdoor (~Andrew@cpc120600-sutt6-2-0-cust232.19-1.cable.virginm.net) |
09:07.18 | *** join/#asterisk hehol (~hehol@gatekeeper.loca.net) |
09:13.03 | *** join/#asterisk infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
09:13.03 | *** topic/#asterisk is AstriCon 2019 in Atlanta! http://www.astricon.net/ -- #asterisk The Open Source PBX and Telephony Platform (asterisk.org) -=- LTS: 13.29.2 (2019/11/21) 16.6.2 (2019/11/21) Standard: 17.0.1 (2019/11/21); DAHDI: 3.0.0 (2018/11/15); libpri 1.6.0 (2017/01/27) -=- Wiki: wiki.asterisk.org -=- Code of Conduct: bit.ly/1hH6P22 |
09:46.57 | *** join/#asterisk alexandre9099 (~alexandre@unaffiliated/alexandre9099) |
12:12.02 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
12:36.36 | *** join/#asterisk dacod (~dacod@201.47.74.146) |
12:45.40 | *** join/#asterisk brad_mssw (~brad@66.129.88.50) |
13:17.52 | *** join/#asterisk tomaluca95_ (~quassel@kde/developer/tomaluca) |
13:25.39 | *** part/#asterisk LunaLovegood (~merv@75.98.139.193) |
13:37.28 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
13:40.24 | *** join/#asterisk tomaluca95_ (~quassel@kde/developer/tomaluca) |
13:45.10 | *** join/#asterisk [TK]D-Fender (~joe@216.191.106.165) |
13:54.32 | *** join/#asterisk tomaluca95 (~quassel@kde/developer/tomaluca) |
13:58.36 | *** join/#asterisk gerhard7 (~gerhard7@ip5657ee30.direct-adsl.nl) |
14:35.24 | *** join/#asterisk Janos (~Janos@201.204.94.76) |
14:38.54 | *** join/#asterisk bford (uid283514@gateway/web/irccloud.com/x-kkfdpcqsmtckfcrd) |
14:38.54 | *** mode/#asterisk [+o bford] by ChanServ |
14:45.55 | *** join/#asterisk engine20191 (~engine201@190.145.222.242) |
14:46.17 | *** join/#asterisk overyander (~overyande@216.163.24.235) |
14:46.33 | *** join/#asterisk eharris (~eharris@unaffiliated/eharris) |
14:50.47 | *** join/#asterisk Slade (~user@unaffiliated/slade) |
15:02.41 | *** join/#asterisk kharwell (uid358942@gateway/web/irccloud.com/x-iqmbrggmuzeanuar) |
15:02.41 | *** mode/#asterisk [+o kharwell] by ChanServ |
15:38.14 | *** join/#asterisk jkroon (~jkroon@165.16.204.110) |
16:00.14 | overyander | when using postgres odbc how/where do you specify the schema where asterisk should find its tables? |
16:14.48 | igcewieling | I only know about mysql odbc, sorry. |
16:31.22 | *** join/#asterisk overyander (~overyande@216.163.24.235) |
16:37.13 | *** join/#asterisk CatCow97 (~mine9@c-73-96-109-206.hsd1.or.comcast.net) |
17:15.17 | *** join/#asterisk overyander (~overyande@216.163.24.235) |
17:28.24 | *** join/#asterisk bengoa (~alberto@194.50.55.200) |
17:58.59 | *** join/#asterisk eharris (~eharris@unaffiliated/eharris) |
18:09.31 | *** join/#asterisk alexandre9099 (~alexandre@unaffiliated/alexandre9099) |
18:30.03 | *** join/#asterisk miralin (~Thunderbi@46.63.153.43) |
18:56.53 | *** join/#asterisk hfb (~hfb@107-1-3-130-ip-static.hfc.comcastbusiness.net) |
20:10.51 | *** join/#asterisk miralin1 (~Thunderbi@host-46-45-217-207.stavropol.ru) |
20:16.08 | *** join/#asterisk stux|work (stux@2a01:270:2050:1337::1) |
20:55.58 | *** join/#asterisk overyander (~overyande@216.163.24.235) |
21:19.01 | *** join/#asterisk AsteriskRoss (~AsteriskR@r01.nt-r1.nor.gb.voicehost.co.uk) |
21:38.06 | *** join/#asterisk spatel (~spatel@static-71-174-102-211.bstnma.fios.verizon.net) |
21:49.32 | overyander | is it recommended to use res_pgsql or res_odbc ? |
22:06.17 | *** join/#asterisk overyander (~overyande@216.163.24.235) |
22:08.12 | overyander | i'm trying to connect asterisk to a postgres sql server. is it recommended to use res_pgsql or odbc? |
22:08.53 | *** join/#asterisk spatel (~spatel@static-71-174-102-211.bstnma.fios.verizon.net) |
22:13.22 | *** join/#asterisk ghoti (~paul@dhcp-108-168-13-54.cable.user.start.ca) |
22:15.49 | *** join/#asterisk spatel (~spatel@static-71-174-102-210.bstnma.fios.verizon.net) |
22:21.38 | *** join/#asterisk rwb (~Thunderbi@65.183.138.202) |
22:25.02 | kharwell | overyander: I'd say res_odbc. It's core supported, whereas the other is extended |
22:25.28 | kharwell | also here is the configuration I use for odbc and postgres: https://pastebin.com/va1kN50y |
22:26.03 | overyander | thanks |
22:26.10 | overyander | that doesn't have ssl options though |
22:27.07 | overyander | ssl is what i'm having a problem with at the moment |
22:51.43 | *** join/#asterisk miralin1 (~Thunderbi@46.63.153.43) |
22:52.30 | *** join/#asterisk [TK]D-Fender (~joe@64.235.216.2) |
23:23.06 | *** join/#asterisk mindthelion (~techquila@2407:7000:9125:e400:f1c2:df9f:be37:22a2) |
23:32.17 | *** join/#asterisk overyander (~overyande@209.141.208.197) |
23:34.49 | *** join/#asterisk jeffspeff (~overyande@209.141.208.197) |