| 00:14.10 | *** join/#asterisk-dev smurf (n=smurf@debian/developer/smurf) |
| 00:20.25 | *** join/#asterisk-dev corramor (n=corramor@nat/digium/x-6c3e40d38044770e) |
| 00:30.05 | *** join/#asterisk-dev kpfleming (n=kpflemin@asterisk/digium-director-of-software-tech/kpfleming) |
| 00:30.05 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 01:36.09 | *** join/#asterisk-dev seanbright (n=sean@asterisk/contributor-and-bug-marshal/seanbright) |
| 01:36.09 | *** mode/#asterisk-dev [+o seanbright] by ChanServ |
| 02:03.57 | JBenden76_ | Quick question: What is the typical value people use for Zaptel/DAHDI taps? The available list looks to be 16, 32, 64, 128, and 256... But what is typical? |
| 02:32.26 | *** join/#asterisk-dev ManxPower (n=manxpowe@24.196.31.252) |
| 03:41.02 | *** join/#asterisk-dev kerframil (n=kerframi@gentoo/user/kerframil) |
| 07:27.11 | *** join/#asterisk-dev mog (n=mog@c-68-62-219-86.hsd1.al.comcast.net) |
| 07:27.11 | *** mode/#asterisk-dev [+o mog] by ChanServ |
| 09:24.22 | tzafrir_laptop | JBenden76_, the default of 128... (16ms) |
| 09:26.11 | JBenden76_ | that's what most use? (I am working on optimizing functions in dahdi using SIMD instructions and trying to ensure that the algorithms I choose are properly built.) |
| 09:45.35 | *** join/#asterisk-dev oej (n=olle@ns.webway.se) |
| 09:45.35 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 10:00.06 | *** join/#asterisk-dev eliel (n=Eliel@200.183.52.134) |
| 10:00.06 | *** mode/#asterisk-dev [+o eliel] by ChanServ |
| 10:59.45 | *** join/#asterisk-dev qdk (n=qdk@212.27.21.230.bredband.3.dk) |
| 11:31.25 | *** join/#asterisk-dev jbot (i=ibot@rikers.org) |
| 11:31.25 | *** topic/#asterisk-dev is Asterisk Development Discussion -=- http://www.asterisk.org/developers -=- Asterisk trunk: res_telepathy release tomorrow -=- Tier 2 and Tier 3.14159265 support is in #asterisk -=- Congrats -dev on the release of 1.6.0! -=- http://xkcd.com/303/ |
| 11:59.29 | *** join/#asterisk-dev oej (n=olle@ns.webway.se) |
| 11:59.29 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 12:06.01 | snuff-home | ping.. anyone that knows how to use review board got a sec? |
| 12:15.26 | *** join/#asterisk-dev kamanashisroy (n=kamanash@119.30.34.4) |
| 13:08.14 | *** join/#asterisk-dev oej (n=olle@ns.webway.se) |
| 13:08.14 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 13:53.18 | *** join/#asterisk-dev DarkRift (n=dark@65.92.165.119) |
| 13:56.22 | *** join/#asterisk-dev bbryant (n=brett@68.208.65.50) |
| 13:56.22 | *** mode/#asterisk-dev [+o bbryant] by ChanServ |
| 14:38.19 | *** join/#asterisk-dev IguanaNed (n=me@CPE000625db3f84-CM00111ae43f1e.cpe.net.cable.rogers.com) [NETSPLIT VICTIM] |
| 14:47.06 | *** join/#asterisk-dev IguanaNed (n=me@CPE000625db3f84-CM00111ae43f1e.cpe.net.cable.rogers.com) [NETSPLIT VICTIM] |
| 15:10.44 | *** join/#asterisk-dev d3wayne (n=dwayne@76.29.245.9) |
| 15:10.44 | *** mode/#asterisk-dev [+o d3wayne] by ChanServ |
| 15:33.47 | *** join/#asterisk-dev jtodd (n=jtodd@65.14.229.26) |
| 16:05.52 | *** join/#asterisk-dev jameswf (n=james@unaffiliated/jameswf-home) |
| 16:29.23 | *** join/#asterisk-dev oej (n=olle@ns.webway.se) |
| 16:29.23 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 16:43.10 | *** join/#asterisk-dev anthm (n=anthm@freeswitch/developer/anthm) |
| 17:01.43 | *** join/#asterisk-dev shazaum (n=shazaum@unaffiliated/shazaum) |
| 17:18.14 | *** join/#asterisk-dev bbryant (n=brett@68.208.65.50) |
| 17:18.14 | *** mode/#asterisk-dev [+o bbryant] by ChanServ |
| 17:47.35 | *** join/#asterisk-dev moy (n=moy@200.57.93.65) |
| 18:02.42 | *** join/#asterisk-dev Dovid (i=David_M_@tony09-121-90.inter.net.il) |
| 18:21.50 | tzafrir_laptop | tzanger, somewhat late pong |
| 19:34.19 | *** join/#asterisk-dev telecos (n=sergio@154.166.219.87.dynamic.jazztel.es) |
| 19:41.05 | *** join/#asterisk-dev telecos (n=sergio@154.166.219.87.dynamic.jazztel.es) |
| 20:08.43 | philipp64 | tzafrir_laptop: ping? |
| 20:09.41 | tzafrir_laptop | philipp64, here |
| 20:10.24 | philipp64 | hey. quick question: any idea why perl-ish regex's weren't supported in the dialplans? \d is so much nicer than [0-9] to write out... |
| 20:11.01 | philipp64 | other than the fact that we couldn't then link against the posix libs... |
| 20:11.03 | tzafrir_laptop | I figure that they were difficult to test |
| 20:11.27 | tzafrir_laptop | (or posix regex, or even posix basic regex) |
| 20:11.31 | philipp64 | ah. or perhaps too much of a source of confusion for non-programmer/scripter types... |
| 20:11.48 | philipp64 | well, you can write (who|where) ... that will work... |
| 20:12.29 | philipp64 | (the documentation in channelvariables.txt on what's supported and what isn't is awful. |
| 20:12.48 | tzafrir_laptop | If you want a really good answer, ask codefreeze (Steve Murphy) |
| 20:13.13 | philipp64 | ok. I'll do that... though he looks to be away. |
| 20:13.32 | philipp64 | codefreeze-lap: ping? |
| 20:13.39 | philipp64 | I could always mantis a bug... |
| 20:13.58 | philipp64 | worst that would happen is it would get closed out and I'd get negative kharma points. :-) |
| 20:16.33 | tzafrir_laptop | philipp64, bug for what? a feature request or a patch? |
| 20:16.59 | tzafrir_laptop | What specifically do you need it for? |
| 20:19.18 | philipp64 | feature request... |
| 20:19.31 | philipp64 | maybe get the documentation fluffed up a bit, too. |
| 20:22.03 | philipp64 | do you think it's not worth the trouble? |
| 20:22.30 | philipp64 | or is there anti-perl attitudes in this community I should be aware of? ;-) |
| 20:26.12 | tzafrir_laptop | no |
| 20:26.40 | tzafrir_laptop | (Though in this specific case posix regex would do just as well) |
| 20:27.11 | tzafrir_laptop | hmm.... t-prot as a message filter is really helpful |
| 20:27.12 | philipp64 | well, posix only allows [:digit:] or [0-9]... |
| 20:27.15 | kerframil | philipp64: I like the pcre syntax, but I'd say that linking to libpcre just to use \d over [0-9] or [:digit:] seems excessive. if expressions are used to match things other than just numbers then that's another matter :) |
| 20:27.28 | philipp64 | it lacks the short-hand notations that stop regexs from getting long and difficult to read. |
| 20:28.26 | philipp64 | excess? what's that? :-) |
| 20:28.42 | philipp64 | how many platforms other than linux does asterisk run on, anyway? |
| 20:29.28 | tzafrir_laptop | IIRC one problem with regex in an extension pattern is to get a metric for "which one matched better |
| 20:29.37 | tzafrir_laptop | IIRC there was also an issue with performance |
| 20:29.38 | snuff-home | philipp64: it can run on *BSD |
| 20:29.59 | philipp64 | ah... so MacOS then. |
| 20:30.17 | snuff-home | yep it will even work on solari |
| 20:30.19 | snuff-home | s |
| 20:30.19 | philipp64 | wonder if it's been ported to the Posix shell of any of the commercial RT OS's. |
| 20:30.23 | snuff-home | non sparc atm :) |
| 20:30.36 | philipp64 | endianness? |
| 20:30.40 | tzafrir_laptop | Anyway, I figure even something like: _12.3 would be helpful (12.*3) |
| 20:31.19 | tzafrir_laptop | philipp64, considering that there's gcc and minimal posix compatibility, I figure that there is |
| 20:31.32 | philipp64 | problem I'm having is some $%^&* Canadian telco is letting their FGD connected subscribers send bogus ANI's. |
| 20:32.39 | Juggie | philipp64, i've never had a problem sending any cid/cidname i want in canada. |
| 20:32.48 | Juggie | dont know if it applied to ani as well. |
| 20:33.07 | philipp64 | I tried to get REGEX("^506\d{8}$" ${CALLERID(num)}) working for 30 minutes before I just went with: $[${LEN(${CALLERID(num)})} > 10] |
| 20:33.48 | philipp64 | ok, in this case I think my local ILEC is cloning the ANI from the CID. |
| 20:34.17 | philipp64 | (they have a less-than-capable Coppercom... and little non-telephony expertise... so minimal configuration knowledge.) |
| 20:34.38 | philipp64 | I should *always* be getting the ANI on a trunk, even when the caller-id is blocked. |
| 20:35.16 | philipp64 | where is 506 anyway? |
| 20:35.21 | philipp64 | newfoundland? |
| 20:35.36 | Juggie | no, thats 709 |
| 20:35.44 | Juggie | Newbrunswick is 506 |
| 20:36.04 | philipp64 | damn. not as much fun to make jokes about. |
| 20:36.20 | philipp64 | actually, Fredrickton is a nice little town. good museum. |
| 20:36.23 | kerframil | philipp64: try "^506[0-9]\{8\}$" |
| 20:37.11 | philipp64 | I finally figured out (through trial and error) that \d didn't work... don't think we need the backslashes on the braces, though. |
| 20:37.26 | kerframil | philipp64: you most certainly do unless the function supports "extended" syntax |
| 20:37.45 | kerframil | (extended syntax is much closer to pcre) |
| 20:38.02 | philipp64 | just close enough to leave you frustrated and wistful. :-) |
| 20:38.06 | kerframil | heh |
| 20:38.46 | Juggie | woudnt, ${EXTEN:0:3} be an easier watch to match here? |
| 20:38.52 | philipp64 | I ended up with "^506[0-9]{8}$" and that seems to work. |
| 20:39.06 | kerframil | philipp64: I guess it does then |
| 20:39.21 | philipp64 | I'm not trying to block out 506... I'm trying to block 11-digit calls coming from 506. |
| 20:39.43 | Juggie | so match on 506 and then len > 10 |
| 20:39.47 | Juggie | :) |
| 20:39.47 | philipp64 | if they can't be bothered to generate valid caller-id, I don't want to be bothered with their calls. |
| 20:40.04 | Juggie | you could in theory block all non 10digit calls |
| 20:40.15 | philipp64 | or just all calls with more than 10 digits. |
| 20:40.16 | Juggie | philipp64, btw, are you on the do not call list. |
| 20:40.22 | philipp64 | or anything other than 10 digits... |
| 20:40.30 | philipp64 | got a callerid of "224" not too long ago. |
| 20:40.31 | Juggie | well some calls will be 11 |
| 20:40.39 | Juggie | if the 1 is tere |
| 20:40.41 | Juggie | *there |
| 20:40.45 | philipp64 | I am on the list. |
| 20:41.04 | Juggie | presuming your telco sends the 1-XXX-XXX-XXXX when the number is ld. |
| 20:41.08 | Juggie | and i'm assuming most do |
| 20:41.19 | philipp64 | no, they are always 10 digits, no 1-prefix. |
| 20:41.26 | Juggie | on t1 |
| 20:41.27 | Juggie | true |
| 20:41.31 | Juggie | i was thinking home phone. |
| 20:41.41 | philipp64 | ah... this is a SIP trunk. sorry. |
| 20:41.47 | Juggie | right... |
| 20:42.35 | philipp64 | when my voice-menus hairpin the call back out to my cell-phone, and they send the original caller-id as the ANI/CID... the $%^&* Coppercom switch rewrites the callerid with MY trunk id. |
| 20:42.39 | philipp64 | pinheads. |
| 20:43.32 | philipp64 | so it looks like I'm calling myself. not very useful. |
| 20:43.56 | philipp64 | since Coppercom is toes up, that won't be fixed any time soon. :-( |
| 20:44.30 | philipp64 | I keep telling them to get an Asterisk quad-proc with 2 OC3 cards, and the SS7 stack... |
| 20:44.40 | philipp64 | they won't listen to me, though. sigh. |
| 20:44.48 | *** join/#asterisk-dev DarkRift (n=dark@65.92.165.119) |
| 20:44.59 | Juggie | oc3 cards? |
| 20:45.10 | Juggie | whos making those |
| 20:45.20 | philipp64 | aren't there PCI OC3 cards? Or OC12? |
| 20:45.31 | Juggie | not that i'm aware of |
| 20:45.36 | philipp64 | Worst case, a couple of DS3's... |
| 20:45.39 | Juggie | digium announced one a few years back |
| 20:45.43 | Juggie | but it never got released |
| 20:45.50 | Juggie | unless sangoma is making one |
| 20:45.51 | philipp64 | that's too bad. |
| 20:46.34 | philipp64 | I saw some very early prototypes when I was at France Telecom... |
| 20:46.40 | philipp64 | actually, they were EISA. |
| 20:47.36 | philipp64 | <PROTECTED> |
| 20:47.46 | philipp64 | this is what I found on the Vyatta list. |
| 20:48.20 | Juggie | sangoma has the a301 but that is data only |
| 20:48.23 | Juggie | not channelized |
| 20:48.35 | philipp64 | this one will do STM-1. |
| 20:48.41 | philipp64 | and AAL0. |
| 20:51.01 | philipp64 | from what I can tell on the datasheet, it should support DS0's as 64-kbit CBR VC's with AAL0 encapsulation. |
| 20:54.03 | philipp64 | <PROTECTED> |
| 20:56.22 | philipp64 | <PROTECTED> |
| 20:56.26 | philipp64 | wonder what it goes for... |
| 21:01.38 | *** join/#asterisk-dev eliel (n=Eliel@151-202-114-200.fibertel.com.ar) |
| 21:01.38 | *** mode/#asterisk-dev [+o eliel] by ChanServ |
| 21:06.33 | tzafrir_laptop | eliel, now I recall I thought a bit further about the version field. What number is the version of asterisk 1.6.1? |
| 21:06.48 | tzafrir_laptop | (for [compat] in asterisk.conf) |
| 21:07.29 | eliel | mmm, 1.6 (?) |
| 21:08.29 | tzafrir_laptop | so what happens if you want to add a compat switch for something whose default has changed in 1.6.2 ? |
| 21:08.50 | tzafrir_laptop | (not to mention: what happens with asterisk 1.6.10 / 1.10 , whichever comes first) |
| 21:09.21 | tzafrir_laptop | perl used to represent its version number as float: 5.003004 |
| 21:09.59 | eliel | tzafrir_laptop: yes, you are right, right now I think it is not needed, thats why it was done in this way, also I think that compat issues are changes in "major" versions, like 1.X |
| 21:10.56 | eliel | or we are changing something in 1.6.X or 1.4.X that deprecates a command in older versions? |
| 21:20.41 | tzafrir_laptop | Something in 1.6.x that deperecates something 1.6.(x+1) ? |
| 21:20.43 | tzafrir_laptop | err... |
| 21:20.47 | tzafrir_laptop | Something in 1.6.x that deperecates something 1.6.(x-1) ? |
| 21:21.02 | eliel | yes |
| 21:21.23 | eliel | no |
| 21:22.16 | eliel | yes, he |
| 21:28.46 | eliel | tzafrir_laptop: i need to go, we can discuss this in another moment, sorry, see ya |
| 22:58.33 | *** join/#asterisk-dev qdk (n=qdk@94.191.227.209.bredband.3.dk) |
| 23:03.55 | *** join/#asterisk-dev bbryant (n=brett@c-68-59-20-153.hsd1.sc.comcast.net) |
| 23:03.55 | *** mode/#asterisk-dev [+o bbryant] by ChanServ |
| 23:44.37 | *** join/#asterisk-dev jtodd (n=jtodd@63.164.47.227) |