IRC log for #asterisk-bugs on 20070925

01:07.27*** join/#asterisk-bugs wunderkin (n=wunderki@ip72-223-86-126.ph.ph.cox.net)
01:51.08*** join/#asterisk-bugs fakhir (n=Fakhir@unaffiliated/fakhir)
02:26.00*** join/#asterisk-bugs dlynes (n=dlynes@d154-20-9-152.bchsia.telus.net)
02:27.38*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
02:27.38*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
03:01.13*** join/#asterisk-bugs Pagautas (n=bigman@83.171.14.250) [NETSPLIT VICTIM]
03:32.30*** join/#asterisk-bugs russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla)
03:32.31*** mode/#asterisk-bugs [+o russellb] by ChanServ
04:28.25*** join/#asterisk-bugs Pagautas (n=bigman@83.171.14.250) [NETSPLIT VICTIM]
05:47.04*** join/#asterisk-bugs dlynes_laptop (n=dlynes@d154-20-9-152.bchsia.telus.net)
07:39.36*** join/#asterisk-bugs russellb (n=russell@asterisk/developer-and-stable-maintainer/drumkilla)
07:39.37*** mode/#asterisk-bugs [+o russellb] by ChanServ
07:44.40*** join/#asterisk-bugs Vagabond (i=andrew@pdpc/supporter/active/Vagabond) [NETSPLIT VICTIM]
07:45.11*** join/#asterisk-bugs Corydon76-dig (i=peuce@pdpc/supporter/sustaining/Corydon76-home) [NETSPLIT VICTIM]
07:45.11*** join/#asterisk-bugs Corydon76-vcch (n=tilghman@pdpc/supporter/sustaining/Corydon76-home) [NETSPLIT VICTIM]
07:45.11*** mode/#asterisk-bugs [+oo Corydon76-dig Corydon76-vcch] by irc.freenode.net
08:48.00*** join/#asterisk-bugs mvanbaak (n=mafkees@vanbaak.xs4all.nl)
12:53.43*** join/#asterisk-bugs yoman_ (n=are@89.138.230.25)
13:26.56*** join/#asterisk-bugs d1mas (n=chatzill@host-99.dataart.net)
13:36.36d1masok, repeating here: hello. Question - why asterisk does not create hint when it registers sip/iax realtime friend? If that friend is described by users.conf, the hint is created...
13:37.15filebecause in realtime without caching it is not kept in memory, and presently that is required for hints to work
13:38.00d1masrtcache is on. Asterisk creates NoOp priority 1 but does not create hinr
13:38.02d1mashint
13:38.20file1.4?
13:38.23d1masyes
13:38.32filecall-limit set?
13:38.38filelimitonpeer set?
13:38.57d1masno, no.
13:39.06filethat would be why
13:39.47fileCorydon76-dig: firewalled!
13:40.09d1mashmmm... I will check. But it is just a bit strange - for users.conf everything worked without these parameters. after all. Anyway, thanks, will check
13:40.16Corydon76-digI'll just have to relay via someone inside the firewall...
13:41.39*** join/#asterisk-bugs jsmith (n=jsmith@wsip-70-184-124-51.ph.ph.cox.net)
13:41.39*** mode/#asterisk-bugs [+o jsmith] by ChanServ
13:47.22d1masfile: at first glance, chan_sip for example does not do any ast_add_extension except for NoOp. So I doubt call limits will help
13:47.51fileoh you mean the literal hint in extensions.conf
13:47.54filethat's up to you
13:50.18d1mashm.. but the hint extension is used to get device status (for SIP SUBSCRIBEs for example). If it is missing, status can not be read. Right?
13:51.14filea SIP phone attempting to subscribe for it can't, but it can be read internally
13:52.49d1masnot sue I understand. How can it be read? ast_get_hint will retun nothing...
13:53.15fileinternally stuff queries via the device, not an extension
13:53.29filethe only time the extension is used is (currently) for a SIP phone subscribing to the status of an extension
13:54.26d1maswhich means SIP subscribes do not work?
13:54.36fileif you don't put a hint in, they do not
13:55.04d1masbut I can't put a hint for extension registered dynamically by sip/iax...
13:55.21filesure you can, it'll just say they aren't available or something
13:55.52d1masthat is the same hint for all extesions? constant?
13:56.01filehuh?
13:57.55d1massorry. Reading AEL docs. looks like I can put single hint for all extensions (like hint _XXXX => {...} ) )but it will be the same. That is it can't be used to really represent device state
13:58.32d1masThe question: if asterisk has notion of device states, why hints are used to handle SIP SUBSCRIBEs ?
13:59.00filebecause people subscribe to an extension, Asterisk has to know what device that extension corresponds to
13:59.13d1masright...
14:00.23*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
14:00.23*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
14:01.56*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
14:01.56*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
14:04.36d1masIs't it a good idea to create a hint in addition to NoOp when registering SIP/IAX realtime peer?
14:04.59d1masok "is it a bad idea" is better question :)
14:09.33*** join/#asterisk-bugs blitzrage (n=Leif@asterisk/documenteur-extraordinaire/blitzrage)
14:09.33*** mode/#asterisk-bugs [+o blitzrage] by ChanServ
14:22.21d1masfile?
14:24.36Corydon76-digRemember that file is a star at Astricon... he's probably been mobbed...
14:24.52d1masoh...
14:25.34blitzrageI'm going to mug him
14:26.00Corydon76-digblitzrage: and tickle him?
14:26.18d1maswell, I do not need him exactly :) He was the person how responded to me initially so that is why I was querying him :)
14:26.40d1masThe question is: Is is a bad idea to automatically create a hint in addition to NoOp when registering SIP/IAX realtime peer?
14:27.05Corydon76-digHow would you know what extension at which to put a device?
14:27.51Corydon76-digSo device SIP/snarglefuss registers.  What hint do you create?
14:28.05d1masthe same extension where NoOp is created :)
14:29.20jsmith-awayNo, what does the hint *point to*
14:30.08d1masSIP/${username} ?
14:30.21Corydon76-digd1mas: "Yes, but that's in regcontext, which is probably not the same as context
14:30.51Corydon76-digSo it won't help you
14:31.13d1masSIP fullcontact ?
14:31.40Corydon76-digand the context that one device is in isn't necessarily the context that other devices are in.  Better to let the admin decide where to put the hint
14:33.12Corydon76-digIt's not the problem of being wrong... it's the problem of being irrelevant...
14:33.42d1masCan admin put a hint in a way that it is specified once but it will automatically "instantiated" for every SIP device registered?
14:34.15Corydon76-digNope... not yet, anyway
14:34.38Corydon76-digI had something like that in mind, but it's far from ready
14:35.08d1maspity :)
14:35.16Corydon76-digM7767
14:35.17MuffinMan[assigned] [Asterisk] Core/Configuration 0007767: [patch] Allow a simple lookup for hint extensions reported by Corydon76  http://bugs.digium.com/view.php?id=7767
14:36.44d1masbtw, if you thinking about "templates", I think it would be a good feature to have an ability to provide dialplan template for each registration. Currently when parsing users.conf two priorities registered for each user. But these are hardcoded. Template would let me to do something else insetad of calling stdexten
14:37.48d1masthe same templating "engine" could be used to generate dialplan for SIP/IAX registrations..
14:38.16Corydon76-digWe have lots of a good ideas floating around out there... the question is, what gets done?
14:39.26d1masi know, i know... it was about "if you are already working on that or thinking of that"
14:40.50Corydon76-digWell, I was thinking about that... about 6 months ago...
14:42.55d1mashm.. thinking of.. alternative. What if allow specifying context in hints? that is SIP/1010@default ?
14:43.21d1masin this case it will be possible to automatically registering hint in addition to NoOp for SIP/IAX peers...
15:00.28*** join/#asterisk-bugs dlynes_laptop (n=dlynes@d154-20-9-152.bchsia.telus.net)
15:00.30*** join/#asterisk-bugs dlynes (n=dlynes@d154-20-9-152.bchsia.telus.net)
15:00.56*** join/#asterisk-bugs dlynes_home (n=dlynes@d154-20-9-152.bchsia.telus.net)
15:13.51*** join/#asterisk-bugs jcmoore (n=jcmoore@unaffiliated/tgrman)
16:17.35*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
16:17.35*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
16:19.32*** topic/#asterisk-bugs by Deeewayne -> Asterisk Bugs Discussion -=- http://bugs.digium.com/ -=- http://asterisk.org/developers/bug-guidelines - Asterisk 1.4.11 has been released (August 21, 2007). -=- If you are not discussing a report already posted to the bugtracker, the discussion probably belongs in #asterisk. -=- Goodbye 1.2. We'll miss you. Maybe. -=- Overall bug count: < (340+20)
16:19.46Qwell_Deeewayne: :(
16:19.58Deeewayne:(
16:28.44jmlsM7706
16:28.45MuffinMan[assigned] [Asterisk] Channels/chan_local 0007706: Redirecting Local channels to Meetme causes a crash when executing "core show channels" reported by BigJimmy  http://bugs.digium.com/view.php?id=7706
16:28.50jmlsheh
16:28.52jmlsgl
16:30.17Deeewaynelol...thanks :-)
16:38.46Corydon76-digDeeewayne: must be pretty empty today
16:39.59DeeewayneIt's me, James, PQ, and some hardwarians
17:27.30*** join/#asterisk-bugs snuff-away (i=snuff@220-253-43-185.VIC.netspace.net.au)
18:17.57d1mashm.. I'm full of questions today... What is the reason in creating empty ast_channel everywhere you need to call pbx_substitute_variables_helper instead of letting it accept NULL channel ?
18:22.36*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
18:22.36*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
18:23.42*** join/#asterisk-bugs yoman_ (n=are@89.138.230.25)
18:31.43jcmooreM9305
18:31.45MuffinMan[confirmed] [Asterisk] Channels/chan_sip/Transfers 0009305: [patch] REINVITE before 200ok causes a call to be ended reported by atca_pres  http://bugs.digium.com/view.php?id=9305
18:32.29jcmooreSince everyone's together at Astricon, could we get some folks to look over the patch in that bug, it seems to fix things for me and it'd be nice to get it committed into 1.4/trunk ASAP
18:34.41jcmooreon a related note, if there is a SIP call where RTP was setup directly between A and B and A hangs up, should Asterisk be sending a re-INVITE to B before sending a BYE to B?
18:35.34jcmooreIt seems that whenever the bridge is broken Asterisk should just send a BYE to B straightaway instead of first reinviting the media back to Asterisk and then sending a BYE to B
18:56.43d1mascorydon76: I had some thoughts about context & hints. What is the problem in automatically registering hint in the same context where Noop is put (that is regcontext)? Yes,regcontext can be different from context and yes, other devices can be in other regcontexts. So what? when users.conf is parsed, hint is always put to the same context as a call to stdexten but everybody happy...
19:14.28*** join/#asterisk-bugs yoman_ (n=are@89.138.230.25)
19:16.18d1maswhy to care about contexts at all?
19:31.07*** join/#asterisk-bugs snuff-away (i=snuff@220-253-5-92.VIC.netspace.net.au)
20:15.44*** join/#asterisk-bugs jsmith (n=jsmith@65.116.224.30)
20:15.44*** mode/#asterisk-bugs [+o jsmith] by ChanServ
20:19.12*** join/#asterisk-bugs miguel3239 (n=elguerom@ns1.nashuacs.com)
21:50.28*** join/#asterisk-bugs codefreeze (n=steve_mu@65.116.224.30)
23:04.09*** join/#asterisk-bugs Qwell_ (n=north@pdpc/sponsor/digium/Qwell)
23:04.09*** mode/#asterisk-bugs [+o Qwell_] by ChanServ
23:50.28*** join/#asterisk-bugs Corydon76-dig (i=indigo@pdpc/supporter/sustaining/Corydon76-home)
23:50.28*** mode/#asterisk-bugs [+o Corydon76-dig] by ChanServ

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