| 00:49.14 | *** join/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 00:49.14 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 01:40.16 | *** join/#asterisk-dev wudles (~wudles@gateway.secureinstrument.com) |
| 02:40.59 | *** part/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 02:47.16 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 02:47.16 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 02:55.59 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 02:55.59 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 06:29.28 | *** join/#asterisk-dev schmidts (~schmidts@Lo20-rt01.lm33.sil.at) |
| 06:29.29 | schmidts | good morning |
| 07:10.38 | *** join/#asterisk-dev wedhorn (~wedhorn@123-243-209-34.static.tpgi.com.au) |
| 07:11.40 | *** join/#asterisk-dev WIMPy (~wimpy@e183095026.adsl.alicedsl.de) |
| 07:29.14 | *** join/#asterisk-dev Corydon76-home (gold@c-69-137-80-31.hsd1.tn.comcast.net) |
| 07:29.14 | *** mode/#asterisk-dev [+o Corydon76-home] by ChanServ |
| 09:17.31 | *** join/#asterisk-dev tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 09:17.32 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 10:10.14 | *** join/#asterisk-dev snuff-home (~snuffy@203-219-29-182.tpgi.com.au) |
| 10:10.14 | *** mode/#asterisk-dev [+o snuff-home] by ChanServ |
| 13:31.04 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-tglvrzgkqveobwsn) |
| 13:31.04 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 13:46.35 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:46.35 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 13:47.36 | *** join/#asterisk-dev oron_laptop (~oron_lapt@local.xorcom.com) |
| 13:57.05 | pabelanger | waves |
| 14:01.54 | mjordan | hello |
| 14:08.51 | rustlebee | runs in circles |
| 14:10.58 | lifemadison | ohai |
| 14:21.49 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 14:21.49 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 14:51.37 | *** join/#asterisk-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 14:51.37 | *** mode/#asterisk-dev [+o leifmadsen] by ChanServ |
| 16:08.27 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 16:23.48 | *** join/#asterisk-dev w9sh (~chatzilla@64.238.96.125) |
| 16:27.32 | oron_laptop | sruffell: short question? |
| 16:27.39 | sruffell | hello |
| 16:28.06 | oron_laptop | sruffell: hi, the span attr 'spantype' has different names in different drivers... |
| 16:28.39 | oron_laptop | sruffell: for E1|T1|J1 all drivers put this strings... |
| 16:29.14 | oron_laptop | sruffell: the wcb4xxp put NT|TE, our BRI driver put 'BRI' |
| 16:29.32 | oron_laptop | sruffell: for analog, we fill 'FXS|FXO' others leave empty |
| 16:29.44 | oron_laptop | sruffell: what do you think? |
| 16:30.27 | sruffell | I think we should move that to an enum, make BRI a span that can be either TE or NT, otherwise it's fixed, should make it clearer. agree? |
| 16:31.13 | oron_laptop | sruffell: yes. but what shall we do about analog (some cards have mixed span... hint, hint) |
| 16:31.23 | sruffell | oh yeah….you mentioned that in your email.. |
| 16:31.33 | sruffell | thinks |
| 16:32.48 | oron_laptop | sruffell: also, after enum'ing it, I'll still want to export standard strings in the sysfs attr. |
| 16:32.50 | sruffell | so…yeah…set the enum to SPAN_TYPE_MIXEDANALOG , then dahdi-sysfs can turn that into FXS|FXO string. Or SPANTYPE_ANALOGFXO / FXS if they are all the same…… what about htat? |
| 16:32.51 | sruffell | that |
| 16:33.03 | sruffell | nods |
| 16:33.11 | oron_laptop | nods |
| 16:33.30 | sruffell | kk |
| 16:34.04 | oron_laptop | sruffell: Hmmm... but for the mixed case we still need to read individual channel attributes...(which reminds me) |
| 16:34.18 | oron_laptop | start converting to enum, I think... |
| 16:38.01 | sruffell | a lingering thought..dahdi-sysfs can't be the only place where the enum is convererted into a string since SPANINFO ioctl needs those as strings…but still just managed as strings in dahdi.ko as opposed to in the board drivers. |
| 16:44.03 | oron_laptop | sruffell: I'll just put a convertion function in dahdi-base.c that will be called by sysfs code (and the ioctl as well). |
| 16:44.15 | oron_laptop | sruffell: How are those names: https://gist.github.com/2239668 |
| 16:44.25 | oron_laptop | sruffell: do they cover our known cases? |
| 16:46.15 | sruffell | I don't think dynamic spans set anything in spantype (at least my grep didn't turn up any dynamic instances) should we add another general one for TDMoE and DYNLOC spans? |
| 16:46.23 | sruffell | ones, plural |
| 16:47.31 | oron_laptop | sruffell: we should, but I don't have any idea how they behave (E1/T1 like?, analog like?, another beast?) |
| 16:48.22 | oron_laptop | sruffell: maybe we'll add them as a separate patch. This way we can see if it's laid out in comfortable/flexible way. |
| 16:48.25 | sruffell | Mostly E1/T1 like. If you want to run "analog" type lines over them they use CAS like signalling. |
| 16:48.30 | sruffell | nods |
| 16:48.33 | sruffell | that makes sense to me. |
| 16:49.04 | sruffell | TDMOE I generally don't worry about too much, but I would like to start using Dynamic Local spans more for setting up "hardware-less" regression tests. |
| 16:49.22 | sruffell | also will allow me to help write unit tests for chan_dahdi that can run on the virtual machines. |
| 16:49.25 | oron_laptop | keeps coding (while oron watchs from the sidelines surprise |
| 16:50.06 | oron_laptop | sruffell: note taken (TDMOE), thanks. |
| 16:51.23 | WIMPy | Why do you differ between NT and TE on BRI but not on PRI? |
| 16:51.49 | Qwell | WIMPy: you don't have to with PRI |
| 16:52.07 | Qwell | at least, not at that level |
| 16:52.11 | sruffell | Because NT | TE requires a change in the pinout of the connector. Hx8 and astribank can control that in software, B410P have physical jumpers on the board. |
| 16:52.14 | WIMPy | Just as much as with BRI? |
| 16:52.20 | sruffell | PRI doesn't need to do that. |
| 16:52.52 | WIMPy | You need to chance pin-out on PRI as well. |
| 16:53.53 | sruffell | None of the boards that I've seen have jumpers for that though…you always need to use a cross-over cable depending on what you're doing. |
| 16:54.11 | sruffell | but for BRI…need a way to advertise how the pinout is configured. |
| 16:54.19 | WIMPy | I have one with jumpers. |
| 16:54.25 | sruffell | really? I Digium card? |
| 16:54.30 | sruffell | A Digium? |
| 16:54.33 | WIMPy | No |
| 16:54.46 | sruffell | Can you see in software how the jumpers are set? |
| 16:54.57 | WIMPy | No |
| 16:55.10 | sruffell | ahh..ok…so, then there wouldn't be anything for the drivers to do there. |
| 16:55.24 | WIMPy | And for most BRI cards you can't, either. |
| 16:55.56 | sruffell | true…probably added for the B410P specifically. |
| 16:56.09 | sruffell | (before my time at Digium) |
| 16:57.21 | WIMPy | I prefer to use cros over adapters anyway. Much easier that to open the box, remove the card, replace jumpers, the card and close the box. |
| 16:57.36 | WIMPy | And it's immediately obvious, what's going on. |
| 16:58.14 | WIMPy | But I already said that on the case of the wcb4xxp module only reading jumpers. |
| 16:58.43 | tzafrir_laptop | sruffell, astribank BRI module does require manual jumper settings to change NT/TE |
| 16:59.08 | sruffell | tzafrir_laptop: then how does dahdi_genconf configure it properly? |
| 16:59.17 | sruffell | if you're setting spantype to BRI? |
| 16:59.35 | sruffell | or you just default to TE mode by default? |
| 16:59.57 | tzafrir_laptop | Regardless. There are still jumpers. Much like in the Cologne reference design |
| 17:01.26 | sruffell | well…maybe then b410p should just export BRI….then push the check of any jumpers that can be read off to spanconfig and fail if the mode is being set counter to how the jumpers are configured? |
| 17:02.46 | tzafrir_laptop | Given that for some BRI devices (also some, but not all, of the HFC4/8 cards, IIRC), |
| 17:02.55 | tzafrir_laptop | I suppose it does need exposing |
| 17:03.11 | sruffell | nods |
| 17:03.20 | sruffell | WIMPy: what do you do about the termination jumpers? |
| 17:53.22 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-hvsptlgjucxoqxuy) |
| 18:18.00 | oron_laptop | return into a heated NT|TE discussion (sruffel: spantype patch on air to you) |
| 18:19.18 | oron_laptop | sruffell: for astribank bri, we simple export BRI_NT or BRI_TE (according to hw setup) |
| 18:19.38 | oron_laptop | sruffell: that's how dahdi_genconf, generates correct config for it. |
| 18:20.00 | sruffell | but not in spantype? |
| 18:20.22 | oron_laptop | sruffell: yes the spantype is either BRI_NT or BRI_TE |
| 18:20.38 | sruffell | oh..I thought you were saying that it was just BRI. |
| 18:20.57 | oron_laptop | sruffell: and that's why in the new enum code I added: BRI_NT, BRI_TE, BRI_SOFT (for software controlled) |
| 18:21.20 | oron_laptop | sruffell: (BRI_SOFT for Digium card of course) |
| 18:21.57 | sruffell | nods |
| 19:21.22 | tzafrir_laptop | sruffell, The basic difference between E1 and T1 is the number of channels (other things can be changed after registration) |
| 19:21.44 | tzafrir_laptop | tdmoe can have an arbitrary number of channels, right? |
| 19:25.37 | sruffell | Yes…up to a max. It's set in /etc/dahdi/system.conf |
| 19:28.47 | sruffell | 256 is current limit |
| 19:29.15 | sruffell | http://git.asterisk.org/gitweb/?p=team/sruffell/dahdi-linux.git;a=blob;f=include/dahdi/kernel.h;h=8097cb30d25b7d83e1f3468941320dcd7b2b664a;hb=HEAD#l1057 |
| 19:32.15 | *** join/#asterisk-dev SteveWilliams (~chatzilla@59.162.182.218) |
| 19:36.29 | SteveWilliams | Hi All! I have a noob question. I am trying to write a small phpagi script which when called by a browser, call a phone number. please help! here is the pastebin http://pastebin.com/TiZirehw |
| 19:37.21 | Qwell | SteveWilliams: #asterisk, please |
| 19:37.46 | SteveWilliams | Qwell : oops! im sorry... |
| 19:37.49 | SteveWilliams | bye |
| 19:38.01 | *** part/#asterisk-dev SteveWilliams (~chatzilla@59.162.182.218) |
| 19:58.39 | *** join/#asterisk-dev blitzrage (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 19:58.39 | *** mode/#asterisk-dev [+o blitzrage] by ChanServ |
| 21:41.09 | oron_laptop | sruffell, tzafrir_laptop: good night... left you a lot of stuff to look on until next week |
| 21:41.27 | sruffell | :) I noticed |
| 21:41.35 | sruffell | have a good weekend. |
| 21:41.46 | oron_laptop | sruffell: thanks, bye |
| 21:41.57 | oron_laptop | start hibernating.... |
| 21:55.47 | *** join/#asterisk-dev serafie (~erin@nat/digium/x-azanqkwvvqpkpcqx) |
| 22:31.25 | *** join/#asterisk-dev WIMPy (~wimpy@e183095026.adsl.alicedsl.de) |
| 22:51.26 | *** join/#asterisk-dev WIMPy (~wimpy@e183095026.adsl.alicedsl.de) |
| 23:36.26 | *** join/#asterisk-dev WIMPy (~wimpy@e183095026.adsl.alicedsl.de) |
| 23:58.48 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 23:58.48 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |