| 00:12.38 | *** join/#asterisk-dev schmooze (n=schmooze@69.129.142.83) |
| 01:21.15 | *** join/#asterisk-dev sruffell (n=sruffell@adsl-074-185-078-025.sip.bhm.bellsouth.net) |
| 01:21.15 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 01:34.40 | *** join/#asterisk-dev tzafrir_laptop (n=tzafrir@local.xorcom.com) |
| 01:34.40 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 01:42.14 | *** join/#asterisk-dev droem (n=droem@p548EA904.dip0.t-ipconnect.de) |
| 03:47.34 | *** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 03:47.34 | *** mode/#asterisk-dev [+o lmadsen] by ChanServ |
| 03:57.24 | *** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-232-167.bur.connect.net.au) |
| 03:57.24 | *** mode/#asterisk-dev [+o snuff-home] by ChanServ |
| 04:23.57 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.176) |
| 04:38.56 | *** join/#asterisk-dev Deeewayne (n=dwayne@c-76-29-245-9.hsd1.al.comcast.net) |
| 04:38.56 | *** mode/#asterisk-dev [+o Deeewayne] by ChanServ |
| 04:45.04 | codefreeze-lap | sruffell: aha! OK, I hadn't thought of that; I could suppress loading dahdi_codec; but never having had a card that would require it left me wondering what was going on. |
| 05:00.46 | *** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 05:00.46 | *** mode/#asterisk-dev [+o lmadsen] by ChanServ |
| 05:53.17 | sruffell | codefreeze-lap: So you agree that keeping it an error and asking people to not load that module if they don't need it is the way to go? I guess the other way could be to just fail the load unless verbose is turned on. I guess I should look to see how chan_dahdi operates... |
| 06:46.06 | codefreeze-lap | sruffell: I don't know exactly what I want to say, just this: before this week, I hadn't noticed this, maybe I ignored it, but with a new dahdi installation, this is a WARNING and I felt obligated to check into it, maybe I malconfigured something, maybe some cool feature was not going to be available or something. So I asked around. How many more like me will there be? 0? 100? 1000? Do you really want to handle this over and over again? |
| 06:49.13 | sruffell | yeah...I know what you mean |
| 07:31.40 | *** join/#asterisk-dev seanbright (n=sean@asterisk/contributor-and-bug-marshal/seanbright) |
| 07:31.40 | *** mode/#asterisk-dev [+o seanbright] by ChanServ |
| 07:31.49 | seanbright | ok that was painful |
| 07:32.03 | seanbright | but finally on ubuntu 8.10 |
| 07:32.16 | seanbright | but i forgot to load this up in screen. brb. |
| 07:33.35 | *** join/#asterisk-dev seanbright (n=sean@asterisk/contributor-and-bug-marshal/seanbright) |
| 07:33.35 | *** mode/#asterisk-dev [+o seanbright] by ChanServ |
| 08:53.24 | *** join/#asterisk-dev qdk (n=qdk@78.156.208.216.bredband.3.dk) |
| 09:16.30 | mvanbaak | kpfleming: pong |
| 09:18.45 | *** join/#asterisk-dev qdk_ (n=qdk@212.27.26.160.bredband.3.dk) |
| 09:45.38 | *** join/#asterisk-dev sivadnz (n=sivad@202-78-149-14.cable.telstraclear.net) |
| 09:46.23 | sivadnz | tzafrir: ping |
| 09:49.14 | sivadnz | tzafrir: alecdavis here, do we need to discuss bug 14104 regarding VMWI generation? |
| 09:57.28 | tzafrir_laptop | sivadnz, pong |
| 09:59.17 | *** join/#asterisk-dev kamanashisroy (n=kamanash@202.56.7.21) |
| 10:03.20 | tzafrir_laptop | sivadnz, I'm trying to remember why there was ever a reason for that configuration item to remain static |
| 10:03.52 | tzafrir_laptop | At the time I converted most config items from static to channel-specific |
| 10:04.00 | sivadnz | tzafrir: Regarding VMWI generation, do I need to change anything, as far as I can tell the keyword mwisendtype is related to FXS, not to FXO as you believe. Can you give me a pointer that helps me understand where you understand differently. |
| 10:06.24 | sivadnz | chandahdi..V2 mostly had changes to incase chan_dahdi was patched but wctdm wasn't. |
| 10:09.19 | tzafrir_laptop | right, it seems so |
| 10:10.23 | sivadnz | tzafrir: Do you happen to know what the intended use of reversepolarity in wctdm is for, I asked this a couple times, but no reponses. |
| 10:11.22 | tzafrir_laptop | sivadnz, removing the current parsing will probably be a good idea anyway, as it is buggy |
| 10:12.42 | tzafrir_laptop | e.g. you add 'mwisendtype = rpas' in a specific section in zapata.conf or users.conf and hit reload, it changes the global value |
| 10:17.36 | tzafrir_laptop | sivadnz, what exactly is "ring pulse"? |
| 10:18.40 | sivadnz | not any more??? I'll have to set up another FXS port to check though. I was removing mwisendtype=rpas, reload chan_dahdi.so, and now the phone doesn't do the ring alert, add it back in, hit reload, and now it does ring. |
| 10:18.50 | tzafrir_laptop | (as in ring pulse alert send, rpas) |
| 10:20.53 | tzafrir_laptop | pulse of 250 ms and silense of 10 seconds (AS_RP_cadence) |
| 10:22.18 | sivadnz | rpas, It's before my time. But when you have a message left for you, the phone rings once, then the FSK is sent. Default is no 'rpas', so you don't get a ring pulse before the FSK. I understand some phone require this to wake them up, but not having an intellegent phone handy I;m unable to test the FSK, you can definately hear it if you pick the phone up when it's being sent. |
| 10:25.56 | sivadnz | Note: hearing the FSK, was happening before I started implementing VMWI Line Reversal. I believe the FXS module should stop sending FSK as soon as handset is picked up. At the moment, if you hear FSK you will not get a dialtone, you have to go ONHOOK the OFFhook again. |
| 10:27.57 | sivadnz | Anyway, 30 minutes before Xmas Day, better check the kids, and eat the carrots and chesse, and drink the milk thats been out for a few hours. |
| 10:30.53 | *** join/#asterisk-dev freddyk (n=freddy@host139-25-dynamic.11-79-r.retail.telecomitalia.it) |
| 10:31.37 | tzafrir_laptop | I occasionally heard the FSK due to state machine bugs. Mostly bugs in our drivers... |
| 10:34.50 | sivadnz | The FSK problem is repeatable, Go OnHook for 2 seconds, Go OffHook, FSK heard, Go ONHook for 2 seconds, Go OffHook, DialTone, Go OnHook for 2 seconds, Go OffHook, FSK heard, Go ONHook for 2 seconds, Go OffHook, DialTone... |
| 10:35.01 | sivadnz | Carrots are good |
| 10:43.46 | sivadnz | tzafrir: Are you now OK with keyword 'mwisendtype' and options 'rpas,lrev,hvdc,hvac' in chan_dahdi.conf? |
| 10:48.39 | *** join/#asterisk-dev eliel (n=eliel@200.61.172.61) |
| 10:48.39 | *** mode/#asterisk-dev [+o eliel] by ChanServ |
| 11:30.31 | *** join/#asterisk-dev Dovid (n=annon@tony09-118-62.inter.net.il) |
| 12:36.54 | *** join/#asterisk-dev snuff-home (n=snuffy@C-59-101-240-87.bur.connect.net.au) |
| 12:36.54 | *** mode/#asterisk-dev [+o snuff-home] by ChanServ |
| 12:46.41 | *** join/#asterisk-dev shazaum (n=shazaum@unaffiliated/shazaum) |
| 13:43.10 | *** join/#asterisk-dev sergee (n=serg@voip1.west-call.com) |
| 14:16.48 | *** join/#asterisk-dev qdk_ (n=qdk@195.242.194.42) |
| 14:17.26 | *** join/#asterisk-dev telecos (n=sergio@96.167.219.87.dynamic.jazztel.es) |
| 14:30.53 | *** join/#asterisk-dev moy (n=moy@74.12.127.97) |
| 14:32.50 | *** join/#asterisk-dev lmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 14:32.50 | *** mode/#asterisk-dev [+o lmadsen] by ChanServ |
| 14:38.25 | jsmith | Morning all! |
| 14:46.40 | lmadsen | MORNING!!!! |
| 14:47.00 | lmadsen | just got back from shoveling snow |
| 14:47.00 | lmadsen | from both his parents, and neighbors driveways |
| 14:47.47 | lmadsen | man... the bug tracker is whack-a-mole |
| 14:55.31 | Deeewayne | http://www.youtube.com/watch?v=FgBUqJzgvBo |
| 15:05.58 | lmadsen | heh, neato :) |
| 15:30.37 | *** join/#asterisk-dev DarkRift (n=dark@65.92.166.93) |
| 15:43.28 | *** join/#asterisk-dev CunningPike (n=arodgers@vpn.dnv.org) |
| 15:58.03 | kpfleming | mvanbaak: still around? |
| 16:03.12 | *** join/#asterisk-dev Deeewayne (n=Deeewayn@nat/digium/x-9d3207f5562d399f) |
| 16:03.12 | *** mode/#asterisk-dev [+o Deeewayne] by ChanServ |
| 16:43.45 | *** join/#asterisk-dev Iamnach0 (i=Iamnacho@ip68-103-153-140.ks.ok.cox.net) |
| 17:03.19 | *** join/#asterisk-dev outtolunc (n=me@adsl-66-218-53-172.dslextreme.com) |
| 17:14.34 | *** part/#asterisk-dev sivadnz (n=sivad@202-78-149-14.cable.telstraclear.net) |
| 17:19.08 | *** join/#asterisk-dev sasargen (n=chatzill@174-152-252-173.pools.spcsdns.net) |
| 17:35.45 | *** join/#asterisk-dev unixdawg (n=unixdawg@cpe-98-28-149-231.cinci.res.rr.com) |
| 17:35.49 | unixdawg | anyone here |
| 17:36.01 | file | M11261 |
| 17:36.03 | MuffinMan | [confirmed] [Asterisk] Channels/chan_h323 0011261: [patch] chan_h323 with H323Plus for TRUNK (SVN rev. 89183) reported by vhatz (Karma: neutral) http://bugs.digium.com/view.php?id=11261 |
| 17:36.04 | file | unixdawg: you are talking about that. |
| 17:36.04 | unixdawg | I found a issue in 1.60 and 1.61 in the configure script |
| 17:36.38 | unixdawg | no |
| 17:36.47 | file | yes, you are |
| 17:36.52 | unixdawg | I am talking about the configure script |
| 17:37.02 | file | right |
| 17:37.10 | file | which is essentially support for the conversion of openh323 to opal |
| 17:37.18 | unixdawg | yes |
| 17:38.14 | unixdawg | so when will 1.6.1 be patchesd to use opal then |
| 17:38.30 | file | no idea |
| 17:38.31 | unixdawg | as I cant submit my port till its fixed |
| 17:38.44 | kpfleming | it's not broken |
| 17:38.48 | unixdawg | so this now holds up 1.6.1 and 1.6.0 on bsd |
| 17:38.51 | unixdawg | it is |
| 17:39.03 | unixdawg | you cant compile with h323 support |
| 17:39.07 | unixdawg | that is a break |
| 17:39.32 | unixdawg | if it not looking for /usr/local/include/opal |
| 17:39.36 | unixdawg | then its a break |
| 17:39.37 | kpfleming | you can if you install openh323 instead of opal |
| 17:39.51 | kpfleming | if that platform does not offer openh323, then it's not a bug in asterisk |
| 17:40.19 | unixdawg | we have open h323 and opal and 2.9.xx of h323 it fails |
| 17:40.41 | unixdawg | 1..1 says that the openh323 is broken |
| 17:40.47 | unixdawg | and fails to compile |
| 17:41.16 | unixdawg | been fighting this for 3 days now on bsd |
| 17:41.19 | kpfleming | chan_h323 is not compatible with openh323 2.9 |
| 17:41.29 | unixdawg | and I have people screaming for h323 support |
| 17:41.33 | kpfleming | that is not a bug that is broken |
| 17:41.48 | kpfleming | i'm sorry to hear that, they should use a platform that provides what chan_h323 requires |
| 17:42.43 | unixdawg | then we are not talking about the same thing |
| 17:42.54 | unixdawg | cnah_openh323 is part of addons |
| 17:43.09 | unixdawg | so there for we are not talking about the same thing |
| 17:43.16 | kpfleming | no, chan_ooh323 is part of addons |
| 17:43.21 | kpfleming | there is no chan_openh323 |
| 17:43.42 | kpfleming | chan_ooh323 does not use openh323 nor opal |
| 17:44.00 | kpfleming | chan_h323 uses openh323 and not opal, and is only compatible with fairly old versions of openh323 |
| 17:44.31 | unixdawg | so is there a plan to move the chan_h323 to opal |
| 17:44.39 | kpfleming | not for any of us, no |
| 17:44.45 | kpfleming | there is no current maintainer for that channel driver |
| 17:44.50 | unixdawg | ok |
| 17:45.03 | unixdawg | so really h323 then should be pulled |
| 17:45.12 | unixdawg | execpt for ooh323 |
| 17:45.18 | unixdawg | or is it dead also |
| 17:45.19 | kpfleming | it works just fine on platforms that provide openh323 1.x, which is a lot of them |
| 17:45.25 | kpfleming | plenty of people use it on linux |
| 17:45.51 | unixdawg | running 1.4.x yes but as people update and move to opal for better support |
| 17:46.08 | kpfleming | then someone who has the knowledge and time will need to update chan_h323 to the new APIs |
| 17:46.18 | kpfleming | but there is no reason to pull it when it still works with older versions |
| 17:46.21 | unixdawg | we current have close to 40 thousand bsd/aterisk user |
| 17:46.35 | unixdawg | and we are doing our best to keep them supported |
| 17:46.40 | kpfleming | i'm glad to hear that |
| 17:47.13 | unixdawg | this means finding a h323 work around because with 1.6.1 it failing to build |
| 17:47.37 | kpfleming | it will fail to build with 1.4 as well, if all you have is newer openh323 than it supports |
| 17:48.17 | unixdawg | well 1.4.22 builds fine with 1.x of open h323 |
| 17:48.33 | unixdawg | but on the same system testbuilding 1.6.1 it fails |
| 17:48.50 | unixdawg | it says the h323 port is broken and to update the port |
| 17:49.46 | unixdawg | h323plus is not even in our ports that the discuss in that ticket |
| 17:50.13 | file | the ticket is discussing the future of chan_h323 basically, where it should go... ie using h323plus or opal |
| 17:50.17 | file | and backwards compatibility |
| 17:50.24 | unixdawg | ok |
| 17:50.39 | rene- | hey i installed branch 1.6.0 and still getting ast_careful_fwrite: fflush() returned error: Illegal seek |
| 17:51.05 | rene- | i was told that was due to a bad backport of mine (of the ast careful fwrite function) but branch does the same thing |
| 17:54.21 | unixdawg | well the need for h323 is there for some hardware |
| 17:54.37 | unixdawg | and it sucks that 1.6.1 is not building with it |
| 17:55.32 | unixdawg | I just emailed that like to the asterisk-bsd mail list asking for input on what they think we shold do for now |
| 17:56.59 | rene- | how can i add a note on a closed issue |
| 17:57.03 | rene- | on the bugtracker? |
| 18:05.16 | unixdawg | well for now I guess h323 is going to be pulled from the 1.6.1 unless some one can get it working |
| 18:05.25 | unixdawg | on bsd |
| 18:06.18 | *** part/#asterisk-dev Deeewayne (n=Deeewayn@nat/digium/x-9d3207f5562d399f) |
| 18:07.29 | rene- | is manager broken on 1.6.1 ? |
| 18:08.12 | unixdawg | we will know shortly |
| 18:08.21 | unixdawg | have not played with 1.6.x yet |
| 18:08.29 | unixdawg | just doing the basic ports ofr bsd |
| 18:08.35 | unixdawg | ofr/for |
| 18:09.13 | rene- | it seems a bit broken to me |
| 18:09.29 | rene- | i get disconnects and fflush errors |
| 18:13.06 | *** join/#asterisk-dev JimVanM (n=jimvanm@bas1-toronto63-1096578605.dsl.bell.ca) |
| 18:19.59 | unixdawg | you beta 3 or 4 |
| 18:20.11 | unixdawg | beta4 just came out for 1.6.1 |
| 18:20.14 | rene- | i am using branch |
| 18:20.21 | rene- | 1.6.0 branch |
| 18:20.25 | rene- | from yesterday |
| 18:20.31 | unixdawg | well you asked abotu 1.6.1 |
| 18:21.15 | rene- | sorry i meant 1.6.0 branch i was told it would be newer than the 1.6.1 betas |
| 18:21.50 | rene- | and the manager 'fix' was ported to1.6 and 1.6.1 |
| 18:55.04 | *** join/#asterisk-dev The_Boy_Wonder (n=vossel@74-47-21-87.dsl1.ckvl.tn.frontiernet.net) |
| 18:56.28 | seanbright | rene-: that is not what you were told |
| 18:56.51 | seanbright | rene-: you were told that the 1.6.0 branch is newer than 1.6.0-rc3 |
| 18:57.23 | rene- | yes 1.6.0.3-rc1 |
| 18:57.25 | rene- | sorry |
| 18:57.38 | rene- | hmm |
| 18:58.05 | rene- | well branch 1.6.0 manager seems broken, i get tons of ilegal seeks errors |
| 18:58.11 | rene- | should i try branch 1.6.1 |
| 18:58.12 | rene- | ? |
| 18:58.25 | seanbright | rene-: then you should submit a bug on the bugtracker |
| 18:58.27 | seanbright | http://bugs.digium.com/ |
| 18:58.35 | seanbright | rene-: you are welcome to try 1.6.1 if you'd like |
| 18:58.55 | rene- | i will try first otherwise i will submit the bug. thanks |
| 19:00.34 | *** join/#asterisk-dev eliel (n=eliels@151-202-114-200.fibertel.com.ar) |
| 19:00.34 | *** mode/#asterisk-dev [+o eliel] by ChanServ |
| 19:19.10 | *** join/#asterisk-dev gambler1 (n=mene_sun@dragan.eunet.yu) |
| 19:25.02 | *** part/#asterisk-dev macli (n=macli@nmc.brc.ubc.ca) |
| 21:31.18 | *** join/#asterisk-dev droem (n=droem@p548EA9AC.dip0.t-ipconnect.de) |
| 21:45.58 | *** part/#asterisk-dev The_Boy_Wonder (n=vossel@74-47-21-87.dsl1.ckvl.tn.frontiernet.net) |
| 23:27.30 | *** part/#asterisk-dev corramor (n=corramor@nat/digium/x-4f1ddb257d2b1b14) |
| 23:34.42 | *** join/#asterisk-dev qdk_ (n=qdk@212.27.26.160.bredband.3.dk) |