IRC log for #asterisk-dev on 20131029

00:01.06*** join/#asterisk-dev barbosa2 (~juliano.b@177.158.4.82)
00:17.29*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
00:29.09*** join/#asterisk-dev otherwiseguy (~otherwise@23-228-162-96.mci.googlefiber.net)
00:46.36*** join/#asterisk-dev suneye (~atcmmi@119.122.153.183)
01:18.01*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
01:23.16*** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-zruxehlkxnaczthc)
01:23.16*** mode/#asterisk-dev [+o mjordan] by ChanServ
02:00.51*** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-zruxehlkxnaczthc)
02:18.38*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
02:21.30*** join/#asterisk-dev atcmmi (suneye@116.25.194.0)
02:21.48*** join/#asterisk-dev mjordan (~mjordan@75.76.55.191)
02:21.48*** mode/#asterisk-dev [+o mjordan] by ChanServ
02:50.43*** join/#asterisk-dev suneye (~atcmmi@119.122.153.183)
03:17.28*** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell)
03:17.28*** mode/#asterisk-dev [+o sruffell] by ChanServ
03:19.10*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
03:29.17*** join/#asterisk-dev otherwiseguy (~otherwise@2605:a601:434:5101:3e97:eff:fe14:ef66)
04:19.40*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
04:38.10*** join/#asterisk-dev Shrimp_ (~shrimp@196-215-114-81.dynamic.isadsl.co.za)
05:20.15*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
06:07.24*** part/#asterisk-dev calidosinho (~santiago@181.132.97.244)
06:15.00*** join/#asterisk-dev suneye (~atcmmi@50.2.43.42)
06:20.43*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
06:34.53*** join/#asterisk-dev tzafrir (~tzafrir@bzq-218-28-58.cablep.bezeqint.net)
06:34.53*** mode/#asterisk-dev [+o tzafrir] by ChanServ
06:42.27*** join/#asterisk-dev atcmmi (suneye@116.25.194.0)
06:57.10*** join/#asterisk-dev suneye (~atcmmi@119.122.153.183)
07:51.12*** join/#asterisk-dev Matt__4 (~Matt_@196-215-114-81.dynamic.isadsl.co.za)
07:51.31*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
07:53.17*** join/#asterisk-dev suneye (~atcmmi@119.122.153.183)
08:48.36*** join/#asterisk-dev Matt__4 (~Matt_@196-215-114-81.dynamic.isadsl.co.za)
08:54.46*** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:1001:9285:b25f:15c4)
09:28.04*** join/#asterisk-dev Tim_Toady (~fuzzy@snf-33276.vm.okeanos.grnet.gr)
09:36.19*** join/#asterisk-dev bulkorok (~chatzilla@85.183.61.47)
09:37.28*** join/#asterisk-dev tzafrir (~tzafrir@local.xorcom.com)
09:37.28*** mode/#asterisk-dev [+o tzafrir] by ChanServ
09:50.26*** join/#asterisk-dev barbosa2 (~juliano.b@177-069-248-123.static.ctbctelecom.com.br)
11:02.34*** join/#asterisk-dev atcmmi (~atcmmi@50.2.43.42)
11:13.19*** join/#asterisk-dev suneye (~atcmmi@119.139.133.239)
11:21.35*** join/#asterisk-dev suneye (~atcmmi@119.139.133.239)
11:38.05*** join/#asterisk-dev Pullphinger (~Pullphing@12.40.23.68)
11:43.54*** join/#asterisk-dev zigg (~matt@unaffiliated/zigg)
12:05.26*** join/#asterisk-dev anonymouz666 (~anonymouz@189-25-117-45.user.veloxzone.com.br)
12:22.24*** join/#asterisk-dev bulkorok (~Benjamin@85.183.61.47)
12:27.36*** join/#asterisk-dev protocoldoug (~doug@unaffiliated/protocoldoug)
12:29.39*** join/#asterisk-dev snuff-work (~snuffy@210.8.167.13)
12:29.39*** mode/#asterisk-dev [+o snuff-work] by ChanServ
12:30.22*** join/#asterisk-dev mjordan (~mjordan@75.76.55.191)
12:30.22*** mode/#asterisk-dev [+o mjordan] by ChanServ
13:07.59*** part/#asterisk-dev mjordan (~mjordan@75.76.55.191)
13:13.35*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
13:44.02fileAHA!
13:44.18*** join/#asterisk-dev serafie (~erin@24.96.64.240)
13:55.17*** join/#asterisk-dev otherwiseguy (~otherwise@2605:a601:434:5101:3e97:eff:fe14:ef66)
14:00.31*** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell)
14:00.31*** mode/#asterisk-dev [+o sruffell] by ChanServ
14:04.13*** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-voqyjaqpfhgrzaqc)
14:04.13*** mode/#asterisk-dev [+o mjordan] by ChanServ
14:11.13*** join/#asterisk-dev kharwell (~kharwell@nat/digium/x-xqssdfzpvxzstsye)
14:11.46*** join/#asterisk-dev snuff-work (~snuffy@210.8.167.13)
14:11.46*** mode/#asterisk-dev [+o snuff-work] by ChanServ
14:16.46*** join/#asterisk-dev w9sh (~sph@50-79-224-193-static.hfc.comcastbusiness.net)
14:33.17*** join/#asterisk-dev newtonr (~newtonr@nat/digium/x-oiilafqnbyrxhuoh)
14:33.17*** mode/#asterisk-dev [+o newtonr] by ChanServ
14:33.26*** join/#asterisk-dev zigg (~matt@unaffiliated/zigg)
14:40.00*** join/#asterisk-dev tensai (~tensai@184-155-219-119.cpe.cableone.net)
14:50.47*** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd)
14:50.47*** mode/#asterisk-dev [+o malcolmd] by ChanServ
15:09.05filedanjenkins, attack!
15:09.28danjenkinsI have been rather quiet these past few days, you must be loving it file
15:09.48fileI know you are secretly plotting
15:20.33*** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net)
15:20.33*** mode/#asterisk-dev [+o oej] by ChanServ
15:53.22*** join/#asterisk-dev serafie (~erin@24.96.64.240)
16:14.36*** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson)
16:14.36*** mode/#asterisk-dev [+o putnopvut] by ChanServ
16:24.39*** part/#asterisk-dev bulkorok (~Benjamin@85.183.61.47)
17:05.54*** join/#asterisk-dev zigg (~matt@unaffiliated/zigg)
17:28.39PreatorianHey all
17:30.42PreatorianI have a problem with dahdi detecting a line hang-up, spended some hours on it + discussing with the guys in #asterisk, they suggest to try here due to the nature that perhaps it's not implemented or an error for not detecting it.
17:32.00mjordanPreatorian: you may have to describe what you're seeing in more depth; I didn't see the conversation in #asterisk (not that I can help you, but others in the channel may be able to with more info)
17:32.17PreatorianI'm typing, but want to keep it as simple as possible :)
17:33.36PreatorianHardware > PSTN Line --- Digium(wctdm24xxp) with 2 FXO modules
17:34.34PreatorianProblem > External caller, dials in, the card rings and the caller decides to hang up after a while because nobody picks up. But it takes 8 seconds for the DAHDI controller to notice this.
17:34.56mjordanleedm777: as an aside, a post-review went up cleanly
17:35.12leedm777\o/
17:35.35filegold star!
17:37.02sgriepentrogPreatorian: do you know if your pots line provider sends you a CPC Disconnect?
17:37.14PreatorianI'm affraid not
17:37.29datachomperpraetorian Yea it sounds like what you need is supervision
17:37.33PreatorianI've checked with dahdi-monitor and i'm getting the following (dont laugh lol).
17:38.37Preatorian*** Static noise  ***** ###Ring###---clean line---$$modulated sound for CLIP info$$ --- clean line --- ###RING###  ----clean line---- @Caller hangsup here *** Static noise  *****
17:38.41sgriepentrogUnfortunately, with pots, the only reliable way to know immediately that the line is if it is signalled.  Otherwise, you're depending on your dialplan to timeout and hangup, or the TDM interface driver to notice the reorder tone.
17:39.07PreatorianSounds stupid, but there is like a something is very clearly changing on the line
17:39.11sgriepentrogAh. you mean prior to answer?
17:39.26PreatorianYeah, he just hangs up without anyone picks up :)
17:39.31PreatorianBut then dahdi keeps ringing
17:39.58sgriepentrogOkay.  So 8 seconds is perfectly acceptable in that case.  You need 6 seconds minimum to know that you're NOT going to get another ring.
17:40.53PreatorianForgive me for something silly, but how come that when i plug a phone that is older then me (28 years young) on the line it stops immediatly (less then 2 seconds).
17:40.54sgriepentrogRings are 2 seconds on, 4 seconds off, 6 seconds cycle.  Waiting 8 seconds after last ring would be normal to indicate channel is no longer ringing.
17:41.26sgriepentrogThe phone stops ringing yes, but the dahdi driver won't be sure that it can signal end of ringing until 8 seconds have passed of quiet (or at least no ring voltage).
17:42.18PreatorianWhat is notice thought in the dahdi-monitor capture is also like a polarity/modulation that seems to stop when a call is inbound.
17:42.26PreatorianWhen you play it, you can very clearly hear it.
17:42.37sgriepentrogSo while unfortunate, the 8 seconds of ringing on dahdi channel past last ring voltage on pots line is unavoidable.  You might be able to tweak the code and turn it down to 6, but that's about it.
17:43.09filethere is no signal to say there will be no more ringing, the lack of expected ringing is what causes the hangup
17:43.54sgriepentrogIf you have a polarity reversal, or better yet voltage drop, that can be a CPC disconnect.  That's the only way to know immediately that it's dropped.
17:44.26sgriepentrogIt's possible that the CO could be sending a CPC even without answer, but if memory serves that's not required.
17:44.45Preatoriansgriepentrog, i think that's the case, since i can defo see a very clear change in terms of sound, it reverts back to it's static noise on the RX channel.
17:44.47sgriepentrogAnd it might not be in the dahdi driver even if it was.
17:45.00sgriepentrogAre you in loop start or ground start?
17:45.19PreatorianForgive me for asking, but what do you mean?
17:45.21sgriepentrogYou shouldn't get noise.
17:45.56mjordanleedm777: Automagic update!
17:46.04*** join/#asterisk-dev calidosinho (~santiago@181.48.9.61)
17:46.08PreatorianI start dahdi-monitor just before i make the call, and end it when i'm done and all is back to normal.
17:46.12leedm777Magic!
17:46.16sgriepentrogDifferent ways of electrically signalling the line.  I wouldn't expect to see noise on the line.  But ground start would mean you'd be seeing other issues.
17:46.36PreatorianWhen i play that recording in audacity, i can see in the beginning and on the end, like a constant static noise on the line.
17:46.45PreatorianDuring the actual call, it's completely gone and deadsilent.
17:46.55Preatorianand you just hear the ringing etc.
17:47.06sgriepentrogAre you familiar with the c code for dahdi?  It's possible you could trace the issue and come up with a patch that supports your case.
17:48.20PreatorianI'm affraid not, i'm just wondering if this is something i am missing or this is perfectly normal behavior and you cannot monitor/check on it.
17:48.23sgriepentrogIf not can you get a scope and document the line voltage you're seeing for somebody els eto fix it?
17:48.50PreatorianI can send you however the .raw file that dahdi captures to let you see what i mean
17:49.00Preatorianor .wav if you prefer
17:49.57sgriepentrogUnfortunatley, I'm not personally familiar with the dahdi code enough to help you.  And the wav likely won't translate to the signal levels well enough to be sure of a solution.
17:50.33PreatorianIs it possible to capture it in detail enough for you (or a developer) with dahdi-monitor?
17:51.22*** join/#asterisk-dev serafie (~erin@nat/digium/x-qqymgnnqfzsirptn)
17:51.33sgriepentrogSo: initially I can say you're seeing correct behavior - but you might be able to record enough data about your situation to get a fix for it, but I would do it with a scope to insure you have actual voltage levels.
17:52.26mjordanI love the smell of fresh automated documentation generation in the morning. Smells like victory.
17:52.55*** join/#asterisk-dev Pullphinger (~Pullphing@12.40.23.68)
17:52.58PreatorianI'm affraid i do not have such equipment at the office nor home, at least not those that can make such report that you're probably looking for :(.
17:54.25sgriepentrogAnd I'm afraid I don't have the answer for you on whether dahdi-monitor records voltage details.  It's been about 6 years since I used that and it was called zaptel back then.  Don't give up though.  You'll need to befriend somebody who knows Dahdi to make progress on this.
17:54.44datachomperPreatorian: have you tried calling digium tech support?
17:54.45mjordanPreatorian: you have a Digium card based on your description. Have you called support?
17:54.50datachomperhahaha
17:54.56mjordanjinx!
17:55.11sgriepentrogI should have though of that too ;-)
17:55.21mjordanthey can at least help you with the troubleshooting
17:55.25PreatorianThey said, "Did you tried turning it off and on again", i felt it-crowded.
17:56.00datachomperPreatorian: is your case still open?
17:57.11Preatoriandatachomper, sorry i did not called digium support, since i dont have service contract (i assume you need one for that O.o).
17:57.49PreatorianAt least, i'm used for always having SLA/Support contracts for the products i have.
17:58.38PreatorianBesides, i first did a fair amount of googling/configuration checking to make sure i didn't made a rtfm mistake.
17:58.38datachompernow i'm confused by the "it-crowded" comment
17:58.55PreatorianSorry, old irc joke :)
17:59.21PreatorianWatch the serie IT-Crowd and you will understand.
18:02.12Preatorianbut for clarification, i should file a support ticket @Digium support with this first? to make sure the card detects it correctly am i right?
18:04.21newtonrPreatorian, installation support and "is it working as expected?" support is included with Digium's cards as long as they are not really old End of Life'd models.
18:04.55PreatorianI love their music on the line lol
18:04.58Preatoriancalming :P
18:10.02mjordanleedm777: we need an XML markup for code examples. https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+Function_PJSIP_HEADER would look a lot prettier.
18:10.17mjordangoes back to what he should be working on
18:10.46filemjordan, aren't you just our mascot?
18:16.14PreatorianGuys, perhaps silly question, but is it normal to stay on-hold for 15 minutes for the UK support since they dont specifiy business/working hours D:
18:17.20mjordanfile: probably.
18:17.35mjordanfile: can I wear a panda suit?
18:17.41filemjordan, yes.
18:17.57mjordanI'm in
18:27.32*** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net)
18:27.44*** mode/#asterisk-dev [+o oej] by ChanServ
18:30.55newtonrPreatorian, our support guys are in the US. Typically wait times are under a minute from what I've heard.  It just depends on call volume of course.
18:33.53Preatoriani called UK
18:33.55Preatorian:P
18:37.07*** join/#asterisk-dev serafie (~erin@nat/digium/x-fqxpnvcwmtqewlcm)
18:44.38*** join/#asterisk-dev opticron (~opticron@pianoben.ch)
18:44.39*** mode/#asterisk-dev [+o opticron] by ChanServ
18:44.54*** join/#asterisk-dev t_dot_zilla (~vipkilla@unaffiliated/t-dot-zilla/x-2830497)
18:57.45*** join/#asterisk-dev Jamuel (~Adium@c-67-180-156-186.hsd1.ca.comcast.net)
18:59.37JamuelHi.  I was wondering if anyone had any background as to why app_originate doesn't support things like CallerID and channel variables like its cousin AMI Originate does?
19:01.09mjordanJamuel: why does the dialplan application need it?
19:01.41mjordanand better: how would you even specify such things in a sane fashion as dialplan arguments?
19:02.13Jamuelfor me we wanted a really fast way (i.e. not shelling out to AMI) to send announcements via ChanSpy to individual channels
19:03.00JamuelI wrote a patch and just extended the args to optionally allow for setting CNUM, CNAM, and then comma-delimited chan-vars (enclosed in quotes)
19:04.04mjordanwhy not Originate to a dialplan extension that does that?
19:04.16jsmithJamuel: You should be able set the outbound CallerID and channel variables (perhaps with _ inheritance) before calling app_originate
19:04.27mjordanor what jsmith suggested
19:04.29Jamuelbecause I couldn't see how to get channel variables set on that channel
19:04.30jsmithSet(CALLERID(num)=5551212)
19:04.42mjordanJamuel: channel variable inheritance does that automagically :-)
19:04.43JamuelI tried the underscores and they were ignored
19:04.46jsmithOriginate(blah,blah,blah)
19:05.02Jamuelyeah—that's what I imagined should work
19:05.35Jamuelbut looking at app_originate I see the call to ast_pbx_outgoing_app set all those params to NULL
19:05.52Jamuelor ast_pbx_outgoing_exten
19:06.04mjordanah, that's right. Inheritance doesn't apply to Originate.
19:06.17mjordanEither way, I still wouldn't modify the dialplan application.
19:06.52mjordanI'd either add a pre-dial gosub to the Originate application, or I'd just Originate to an extension and set the information there using SHARED variables or something similar
19:07.00mjordanThe second doesn't require any code modifications
19:07.11Jamuelso that was the question:  a.) background on why no inheritance on Originate and b.) why it might be bad to modify the dialplan app
19:07.36mjordanWhat happens when I want to set CDR information on the channel?
19:07.45mjordanOr when I want to set some other random piece of metadata?
19:07.49mjordanIt's a never ending problem.
19:08.11mjordanPre-dial handlers are the appropriate way to take care of that - as soon as the channel is created, a GoSub is called and you can set whatever you want on the channel
19:08.26mjordanbut again, because this is Originate, it's not a very useful solution. You can simply Originate directly to the dialplan and take care of it there.
19:08.44Jamuelbut predial handlers aren't supported in 1.8, right?
19:08.53mjordannope, but neither is what you're describing
19:10.40mjordanand history for inheritance: http://lists.digium.com/pipermail/asterisk-users/2011-April/261217.html
19:10.48Jamuelsure—but I wrote my patch—not that I expected it to be accepted in 1.8 but whether or not there would be a tear in the fabric of space-time if I did it because it seemed too obvious an oversight for it to have been omitted otherwise
19:11.54mjordanIf it gets the job done for you that's fine, but as I said, you can do this in the dialplan already.
19:12.01Jamuelthanks for that link—apparently your Google is better than mine :)
19:12.07Jamuel(or memory)
19:12.16mjordanIt jogged something :-)
19:12.26Jamuelcool—thanks for the insight—and your time!
19:14.52mjordanno problem! In general, we're trying hard to keep dialplan applications from turning into Dial
19:15.03*** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net)
19:15.04*** mode/#asterisk-dev [+o oej] by ChanServ
19:15.07mjordanso if there's ways to do it in the dialplan without passing things as arguments to the application, we try to find that way
19:48.45*** join/#asterisk-dev bulkorok (~Benjamin@gw1.pinguin.ag)
20:01.10*** part/#asterisk-dev t_dot_zilla (~vipkilla@unaffiliated/t-dot-zilla/x-2830497)
20:31.42*** join/#asterisk-dev oej (~Adium@h87-96-134-129.dynamic.se.alltele.net)
20:31.43*** mode/#asterisk-dev [+o oej] by ChanServ
20:51.50*** part/#asterisk-dev bulkorok (~Benjamin@gw1.pinguin.ag)
20:59.37*** join/#asterisk-dev Blashyrkh (~Blashyrkh@178-191-187-0.adsl.highway.telekom.at)
20:59.52Blashyrkhi get a strange error when compiling 11.2 on raspbian
20:59.54Blashyrkhhttp://pastebin.com/ifc7LWK6
21:00.05Blashyrkhi dont try to do a make -j
21:03.32*** join/#asterisk-dev [TK]D-Fender (~chatzilla@64.235.216.2)
21:14.26*** join/#asterisk-dev drmessano (~nonya@pdpc/supporter/active/drmessano)
21:14.26*** join/#asterisk-dev pnlarsson (~niklas@fw1.gml.g.icnet.infracom.se)
21:14.26*** join/#asterisk-dev tzanger (andrew@wallace.mixdown.ca)
21:15.14*** join/#asterisk-dev serafie (~erin@nat/digium/x-jodajmvevqmlnoer)
21:57.29*** join/#asterisk-dev felipe_ (~felipe@unaffiliated/felipe)
22:20.24*** join/#asterisk-dev roderickm (~roderickm@67.63.143.254)
22:37.12*** join/#asterisk-dev Pullphinger (~Pullphing@c-24-13-69-42.hsd1.il.comcast.net)
22:44.56*** join/#asterisk-dev protocoldoug (~doug@unaffiliated/protocoldoug)
23:03.52*** join/#asterisk-dev Blashyrkh (~Blashyrkh@178-191-187-0.adsl.highway.telekom.at)
23:08.14*** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-voqyjaqpfhgrzaqc)
23:33.03*** join/#asterisk-dev calidosinho (~santiago@190.146.210.101)
23:34.43*** join/#asterisk-dev sruffell (~sruffell@asterisk/the-kernel-guy/sruffell)
23:34.43*** mode/#asterisk-dev [+o sruffell] by ChanServ
23:51.12*** join/#asterisk-dev thecardsmith (~doug@unaffiliated/protocoldoug)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.