[00:29] habakuk (n=chatzill@c-24-6-224-243.hsd1.ca.comcast.net) joined #openser. [00:34] Nix (n=Nix@81.213.125.220) left irc: Read error: 60 (Operation timed out) [00:35] Nix (n=Nix@81.213.125.220) joined #openser. [00:36] hohum (n=dcorbe@mercury.sunrocket.com) left irc: "This computer has gone to sleep" [00:45] Zhad (n=tom@cpc1-sout6-0-0-cust691.sotn.cable.ntl.com) left irc: "[BX] Time wasted: 7 millenia 8 centuries 3 decades 2 years 10 months" [01:19] Nix (n=Nix@81.213.125.220) left irc: Remote closed the connection [01:24] Nix (n=Nix@81.213.125.220) joined #openser. [01:28] Nix (n=Nix@81.213.125.220) left irc: Client Quit [01:31] hohum (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) joined #openser. [01:32] hohum (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) left irc: Read error: 104 (Connection reset by peer) [01:32] hohum (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) joined #openser. [01:33] dcorbe_ (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) joined #openser. [01:34] hohum (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) left irc: Read error: 104 (Connection reset by peer) [01:35] Nix (n=Nix@81.213.125.220) joined #openser. [01:59] Nick change: dcorbe_ -> hohum [02:05] a (i=kw7uir45@gateway/web/cgi-irc/irc.net/x-c923b9e6ddc68716) joined #openser. [02:05] a (i=kw7uir45@gateway/web/cgi-irc/irc.net/x-c923b9e6ddc68716) left irc: Client Quit [02:30] Nix (n=Nix@81.213.125.220) left irc: Remote closed the connection [02:31] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) joined #openser. [02:34] Hello, I'm trying to decide if I should use SER or openser for carrier use. any sugestions ? [02:35] ttyS1, I would say openser is a better choice because it seems to have a lot more activity and more features than ser [02:36] habakuk: thanks [02:36] ttyS1: what application are you tring to find a solution for? [02:37] lies! [02:37] what are the features difference? [02:37] that's not a very honest comparison [02:38] ttyS1: it all depends on exactly what functionaliy you require [02:38] we use SER 99.x in production...have for maybe a year [02:38] hohum: obviously you have strong opinions, but thats been my observation [02:39] we had over 1,000 call setups per second during the last presidential election - SER just hummed right along [02:39] habakuk: there are plenty of reasons to use SER over OpenSER and vice versa [02:41] hohum: ok whats the most compelling reason to use ser over openser? [02:42] 'cos it makes a rock solid registrar server, and as you yourself have pointed out the SER code base tends not to change much which means I can always expect that functionality to not be broken from release-to-release [02:44] is functionality often broken from release to release in openSER? [02:44] no, but why upgrade for the sake of upgrading when I don't require the feature sets? [02:45] so there's no actual problem with using openSER as a registrar server then [02:45] hohum: ok I can see that. I actually use SER, I've been using it over a year. but looking at some of the new features recently added to openser, make it pretty compelling. such as the dialog. I mean how cool is it to get tabs on current active calls ? [02:45] I never said there was, I just believe SER to be more GA than OpenSER [02:46] hohum: ok great. any evidence to back that up? i.e. instability, etc in openser? [02:46] like when it comes down to it I may end up migrating to OpenSER, but I would lab OpenSER releases longer, stress test them more, etc based soley on the fact that the code changes more [02:47] NormB_ (n=NormB@24.115.56.68) joined #openser. [02:47] I mainly want to use it to accept high volume of sip calls, keep CDRs and then forward to pstn gateways [02:47] habakuk: explain the dialogue? [02:48] habakuk: my "evidence" to back that up is the frequency of releases.... I'm dealing with hundreds of thousands of registrations and I tend to air on the side of caution [02:48] people don't like it when their phone service goes down [02:48] I'm not saying that OpenSER is unstable [02:49] ttyS1: to give you an idea, within VMWARE on my laptop I can get 270 CPS comfortably doing just what you are trying to do. ( obviously on a decent machine you should be able to do much better) [02:49] stability isn't the only factor that goes into making a particular code train a "GA" release [02:49] hohum: I understand what you are saying: ) no customers do not like that, and you have a valid point [02:50] JT, check out the dialog module in the openser docs [02:51] let me ask this [02:51] habakuk: that sounds pretty good [02:52] ttyS1: thats with only doing DB writes for cdrs [02:54] habakuk: right so then I can connect a billing server directly to openser ? [02:54] ttyS1: directly to mysql [02:54] yeap [02:55] is this something I can do with asterisk or is there something better to use as a billing platform ? [02:57] incidentially I'm writing a B2BUA in C which I won't put a single customer on until I've thrown every possible scenario at it to make sure its fast, stable, no memory leaks, obscure bugs, cases where it cores, etc [02:58] ttyS1: take a look at the acc module, its pretty good and accurate [03:00] habakuk: not necessarily accurate [03:00] what happens if you never receive a BYE? [03:00] how do you know when the call actually completed? [03:00] jerjer, thats where sst module comes in [03:01] hmm [03:01] it always looks like the openser learning curve is so steep [03:01] where if asterisk a toolbox to make a pbx [03:02] openser is a bunch of raw materials to make a proxy server and maybe more? [03:02] hohum: agreed. thats important. sipp comes in handy though [03:03] JT: not much more than a proxy server, but its a proxy server that can do just about everything a proxy server should do and some things that it shouldn't do as well :) [03:05] sst module sounds interesting, but seems it may lower how far one can scale [03:05] habakuk: is there a way I can do H323 as well ? [03:05] ttyS1: not with a SIP Express Router :) [03:06] one could convert H.323 into SIP, then run thru OpenSER [03:06] JerJer: actually the one issue I'm not sure on is how the acc module handles things like blind transfers, transfers, etc. supposedly there is support for it.. but I haven't tested it [03:07] I wish someone would release an open source H.323<->SIP converter [03:07] hohum: there is [03:07] JerJer: is there something that handles as much volume as openser on h323 ? [03:07] part of the vovida sip stack [03:07] yeah [03:07] been there for years [03:07] well [03:07] siptoh323 i believe [03:07] Vovida's sip stack blows [03:07] that's why I'm writing my own B2BUA instead of using theirs [03:08] none of that code is really maintained very well at all [03:08] sip2h323 [03:08] hohum: heh and the sip2h323 is even worse [03:08] the best product on the market for that is nextone [03:08] haha [03:08] but its $$ [03:08] hah how much is a nexton ? [03:09] 40-50K [03:09] i'm sure one could write something using OPAL [03:09] like 60k base hardware for a redundant pair of MSXes and 500 ports [03:09] hohum: sure, but i find it strange that to use openser as a proxy server, it looks like you need to deal with a lot of low level stuff like all the various sip messages, before you can get off the ground [03:09] JT: not really [03:09] you just need to implement handlers for 3 methods [03:10] well 2 [03:11] ser is very hands off in how it deals with each sip method [03:11] but a nexton doesn't act as a pstn gateway does it ? [03:11] so if its not in ser.cfg / openser.cfg then it doesn't get dealt with [03:11] INVITE, REGISTER and if you want a registrar built into your proxy you need to do some nat traversal config, RTP Proxy and you need to let SER know where to find your users database [03:11] ttys1: no you still need to buy a TDM gateway for that [03:12] hohum: a forget it then I'll stick with openser :) [03:12] SBCs don't make very good registrars either [03:12] hohum: which sipstack are you using for you b2bua? [03:13] hohum: agreed, SER is probably the best for that ( registrar) [03:13] habakuk: we wrote one from scratch because we couldn't find a sane non-GPLd stack out there anywhere [03:13] didn't care for resiprocate huh? [03:13] resiprocate isn't built for speed, they even say so in the documentation [03:14] and we weren't really crazy about doing this in C++ either [03:14] true. I wrote a simple registrar with it. I could do 200-300CPS [03:15] but its pretty easy to use [03:15] as many fucked up implementations of SIP that exist out there we figured it'd be easy to find one written in C to start with [03:15] our requirements were simple [03:15] 1) Written in C [03:15] 2) Non-GPL [03:16] our goal is to be able to process 1000CPS without media anchoring [03:16] modest goal [03:17] if we could do that our business case would fly because it wouldn't be too terribly expensive to operate a business [03:17] that's 1000 CPS on commodity hardware [03:18] that's doing full Digest auth on 1000 INVITES per second [03:18] ya know the GPL only applies if you make changes and distrubute those changes [03:18] most people don't realize that you can absolutely run a business running GPL code and never give a thing back, just as long as you don't modify the code [03:18] JerJet: that's precisely what we want to do [03:19] I know that GPL only covers distribution and not use [03:19] modify the code? [03:19] JerJer: modify, then sell [03:19] if its GPL already and you can give back and still sell [03:19] well [03:20] we elected to go with a 3 clause BSD license because you can't really sell network operators on GPL [03:20] you can sell on gpl [03:20] carriers are kind of frightened by OSS [03:20] you just must release source [03:20] even more so by the GPL [03:21] JT: if you make changes - If you use someone elses GPL code all you have to say is "We run Asterisk" [03:21] and you are GPL compliant [03:21] JerJer: of course [03:21] perhaps Asterisk v1.2 is more correct [03:21] distributing zero changes equates to zero distribution [03:21] yep [03:21] Jadestorm (n=Jadestor@cpe-024-163-106-248.nc.res.rr.com) joined #openser. [03:22] but informing that you run GPL code is part of the compliance [03:22] BusyBox is a prime example... DVD players and all kinds of other products run BusyBox but most companies never state that anywhere [03:22] JerJer: and that's the major source of complaints from carriers who want to resell our products [03:23] I had a VC firm specifically say "no GPL" [03:23] then that is a old school vc firm [03:23] hohum: well I think what you want to do is certainly doable. I have a friend of mine that did that same thing. he claims he can handle 3000+ cps with auth, his own stack with b2bua [03:23] this is the license we decided to go with [03:24] http://rafb.net/p/VXIi0r33.html [03:24] habakuk: I know its doable, we'll be done in a few more months :) [03:27] so can openser still not act as a calling card platform, combined with sems or similar? [03:27] ser could feed calls into some application server that does calling card shit [03:28] JT: you need a b2bua of some sort to do calling cards because you specifically need answer supervision [03:28] but ser itself is not suited for doing calling cards [03:28] ok [03:28] let me reask what i'm really trying to ask [03:28] typically the job of a soft switch [03:28] how does openser handles redudndancy and scalability ? [03:28] can ser enforce killing a call? [03:28] JT: no :) [03:28] if it has rtpproxy or mediaproxy? [03:29] ser doesn't even know the concept of a call [03:29] still can't tear it down? [03:29] SER is not capable of doing any sort of answer supervision [03:29] hum [03:29] again, you need a B2BUA for that [03:29] what does it know then? [03:29] just how to copy sip packets? [03:29] ser is just a state engine for processing SIP messages [03:29] JT: it knows "take a message in, do some stuff to it, send a message out" [03:30] you can think of ser as a FIFO with a few controls [03:30] habakuk: do you have problems with answer supervision on your setup ? [03:31] as far as redundancy and scalability goes [03:31] ttyS1: one can configure openser to be as redunandant or as scalable as you want [03:31] if you're operating in stateless mode, you ought to be able to use CARP or some other layer 2 fail over protocol to make the boxes redundant [03:32] you can use the dispatcher mode to spread out the processing [03:32] if you're operating a stateful proxy there's no redunancy [03:32] another scenario, let's say you have: UA > OpenSER+rtpproxy > SIP Wholesaler [03:32] can it handle that? [03:32] or you can use various HA techniques with multiple identical configurations of OpenSer [03:32] because there's no way currently to sync state between 2 SER boxes [03:32] where you have different sip wholesalers [03:32] and it needs to accurately bill [03:32] hohum: sure there is, use the same database [03:32] and then use HA [03:33] JerJer: how does that work for call setup? [03:33] when I'm doing stateful processing of INVITEs [03:33] you are only talking to a single machine at any given time [03:34] so then you need a separete redundant hardware raid ? [03:34] why hardware raid? [03:35] that's up to you [03:35] I'd just thow a bunch of appliance servers in a stack [03:35] we use software raid with sata drives [03:35] raid is not a HA strategy [03:35] and make them redundant/load balanced with OpenBSD and CARP [03:35] it is a HA failover prevention mechanism [03:35] hohum: how can you keep the database the same on both servers ? [03:35] you don't need RAID on a proxy server [03:35] ttyS1: I wouldn't put the data on the same machine as the proxy server [03:35] I would set up a dedicated MySQL cluster for that [03:36] the question of raid is a little irrelevant [03:36] i generally recommend it [03:36] however [03:36] it's clear that sip hates me because i'm an xmpp person ;) there's no other good explanation for the behavior i keep seeing hehehehe [03:37] hohum: that's right [03:37] spend the money on the hardware where it needs to be spent [03:37] in your DBMS [03:37] *not* your front-end devices [03:37] in your back-end, not your front-end [03:37] yeah it matters less if you've got 5 of a front end than 1 [03:38] so SST is only for 1.2.X? what a pity [03:39] we run 1.1.1 [03:39] Jadestorm (n=Jadestor@cpe-024-163-106-248.nc.res.rr.com) left irc: Read error: 104 (Connection reset by peer) [03:40] Jadestorm (n=Jadestor@cpe-024-163-106-248.nc.res.rr.com) joined #openser. [03:40] ok, does this [03:41] : http://pastebin.ca/364316 imply that the server won't answer as just vorpalcloud.org perchance? [03:41] Jadestorm: if i follow what you are after, you are correct [03:42] i had to put the server name in /etc/hosts or openser would not deal with my dns name [03:42] hrm hold on let me see if that magically solves all my problems ;D [03:42] are you getting too many hops ? [03:42] ts going to rain tonight :( [03:43] naw i'm typically getting request timeout [03:43] so the 4 inches of ice that have been covering the ground here for the last week is going to turn into 6 inches of ice [03:43] (i don't know if you recall, but we were talking last night) [03:44] NormB_ (n=NormB@24.115.56.68) left irc: "Leaving" [03:44] hansi (n=chatzill@58.71.34.138) joined #openser. [03:46] hello. is anyone here using 1.2 development version? i noticed that the current development version is no longer sending 4 zero bytes keep alives for clients behind nat. did i miss something here? [03:55] so what can I use to reliably pass lots of sip calls and have acurate call supervision ? [03:55] hansi: there was a change in flags [03:56] yes osas. there is. instead of setflag, we use setbflags right? [03:56] check the docs and make sure that you are using right [03:56] no, usrloc flags [03:57] ttyS1: define call supervision [03:59] osas: make sure I don't have idle calls that log wrong cdrs [04:00] you can't with openser 1.1.x [04:01] you can do something in 1.2 if one of the SIP UA involved in the call is supporting SST [04:01] you will need to grep in the logs for dialog timeouts [04:02] and match them against the acc EDRs [04:02] osas: in migration docs, under usrloc, it shows to use nat_bflag for branch/contact NAT flags. [04:03] wow jerjer, that more or less seems to have done it. i mean i'm running into some other issues at the moment but having added the one alias to /etc/hosts has made me actually able to log into my openser server [04:03] i'm still trying to get it so i can communicate back and forth between clients, but working on that ;D [04:04] hansi: check also this: http://www.openser.org/docs/modules/1.2.x/registrar.html#AEN123 [04:05] osas: I'm planing to use 1.2 with sst, so I have to grep all timeouts from the logs and match them with the acc CDRs every time ? [04:05] sort of ... [04:05] one sec [04:07] hey osas, thanks! il take a look at it. does it make a difference if im using mediaproxy natping instead of nathelper? [04:08] I don't know ... in 1.2 [04:08] both used to work ok in 1.1.x :-) [04:08] ttyS1: I'm back [04:08] osas: welcome back [04:09] ttyS1: If you want to detect the end of the call, you have several options: [04:09] 1. you can use mediaproxy to do accounting [04:09] 2. you can use the SST module to detect failures in call termination [04:10] if you want to use the SST module, you need a SIP UA that undertands SST [04:10] this is how the SST module works [04:10] the SST module will enforce the in call reINVITE ping [04:11] the reINVITE will be done by one of the participants in the call (not by the SST module itself) [04:11] so be aware on this restriction [04:11] hum [04:11] most of the time you should have proper accounting (with the acc module) [04:12] you will need to check for dialog timeouts only for missing call end EDRs [04:12] here's what I would do: [04:12] - log all the SST/dialog failures in a special file (syslog configuration) [04:13] osas: i cannot get accounting to work on mediaproxy [04:13] - make sure that you have all the information to match a timeout against a call-started EDR [04:14] and make sure that you can get all the logs in the same file [04:14] if you are not able to get all the info that you need, open bugs [04:14] and now it's the good time to do it b/c 1.2 will be released soon [04:15] JerJer: afaik, for mediaproxy accounting you need to buy a licecnce from AG [04:15] nothing of the sort is discussed in the media proxy script [04:16] and the author of that shitty code told me to ask how to make it work on the OpenSER mailing list [04:16] tths!: if you have issues with the SST module, just post your questions on the list [04:16] osas: ok, thanks a lot [04:16] s/tths!/ttyS1/ [04:16] np [04:17] JerJer: I think it is stated on some INSTALL file. or README ... [04:17] can't remember exactly ... [04:17] osas: if that bullshit is the case, that motivates me even more to write my own media proxy application in C [04:17] why write a new one [04:17] i have read everything i can find about the media proxy script from ag and it mentions nothing about a license [04:17] enhance rtpproxy ;-) [04:18] beacuse media proxy python is shit [04:20] JerJer: yeah, there's nothing about the licence in the INSTALL file ... [04:21] Adrian Georgescu told me specifically, "Best way [to get accounting working on mediaproxy] is to send this to the openser mailing list" [04:21] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) left irc: Read error: 104 (Connection reset by peer) [04:21] do you have mediaproxy installed? [04:21] EVEN after I offered to pay him [04:21] yes very much so [04:22] one sec [04:22] if you open the accounting.py module you will notice that the mysql shit is commented out [04:22] same with radius [04:22] once you uncomment the mysql module loads, but then it never fires any sql command [04:23] ok. lets say i'm connecting to openser from gaim 2.0beta6. i'm connecting to two accounts that have each other in their contact lists (in gaim). they can't see each other online nor can they apparently get messages through to each other. is there something i have to tell openser to be able to do "simple"? [04:25] JerJer: how about radius? [04:25] hell no [04:25] do you have mediaproxy.iniproperly configured? [04:25] believe so [04:25] why not? :-) [04:25] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) joined #openser. [04:25] it is way better with radius [04:26] not gonna happen [04:26] with CDRTools it will create CDRs instead of EDRs [04:26] i will write my own shit if it comes down to only using radius [04:27] once it is setup. it works pretty well [04:28] if it can work with radius, I can make it work without radius [04:28] radius simply adds another layer of potential failure [04:28] Have you checked the Note at the end of the INSTALL file? [04:28] JerJer: not at all [04:28] yep mysql python shit is installed [04:28] you can cetralize several servers to log into one single db [04:29] and if you do't get a reply from the radius acc server, openser will not let the call to go through [04:29] http://pastebin.ca/364378 [04:29] you can have a redundant billing engine wit a redundant db and you are good to go [04:30] but in the end, it is a matter of taste ;-) [04:30] again, if radius can do it, i can do it without radius [04:30] (nothing personal to others, but i agree with jerjer, radius is a paininthebutt) ;) [04:30] gotta go now ... [04:30] Action: osas likes radius [04:30] Action: osas wanna go diameter now ... [04:30] wait until it bites you one day [04:30] but that's a long story ... :-) [04:31] have a good one guys ... [04:31] granted it may be the implementation where i work, but i spend far too much time helping folk debug their radius crap that's "clearly all my ldap service's fault" when of course it's not [04:31] take care osas! [04:31] osas: later [04:31] k [04:31] there's a lot to be said for not coming to me by saying "you changed something that broke our stuff" (uh, no i didn't) [04:32] all I can tell you is that once is setup ... is rock solid ... [04:32] sorry venting i'll shut up now ;) [04:32] based on my experience [04:32] gnite qll [04:32] all [04:35] any ideas about what might be causing the issues i'm seeing in that pastebin? like what exactly does: SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM). [04:35] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) left irc: Read error: 104 (Connection reset by peer) [04:35] mean [04:35] it sounds like the server didn't know how to route the packet from storm@vorpalcloud to gimlet@vorpalcloud [04:36] wait a sec this is odd [04:36] is gimlet registered and are you looking up the location ? [04:36] it's out_uri is @192.168.174.1 [04:36] i wonder where that came from [04:36] gimlet and storm were both added using openserctl add gimlet pass email [04:37] storm and gimlet can't see each other online .. .they are both logged in from the same gaim 2 client at the same time [04:37] so i tried sending messages to each other without being able to see each other [04:37] wow that was a crap english sentence [04:38] i'm sorry to keep bothering you... i'm sure you've got better things to do than to sit here and help me troubleshoot my crap. [04:39] osas: i saw this in the migration notes: modparam("usrloc","nat_bflag",3) [04:40] so im assuming to use this instead of modparam("registrar", "sip_natping_flag", 7) [04:40] i'm totally confused as to where it's getting out_uri=sip:storm@192.168.174.1:5060 from [04:40] but as i sniff the sip packets, i can no longer see the keep alives openser used to send to keep firewall pin holes open.. :( [04:41] Jadestorm: are you re-writing anything ? [04:41] re-writing? [04:41] oh bother it's coming from vmware's little nat thing [04:41] so it should be harmless i guess but still [04:42] jerjer: i'm not sure what i would be rewriting (don't know the context) [04:42] sip packets? a client? [04:44] something has to be munging the uri into 192.168.174.1 [04:44] does a network device have an ALG? [04:45] osas: got it working. :) got to poke openser a bit! [04:47] i'm sorry i really don't know what you are asking =( (what's an ALG?) openser wise i'm using the default/stock openser.cfg, modified slightly according to the docs to use mysql support. network wise i'm not doing anything to the internal packets (only do firewall rules and such to stuff coming into the network device that takes me to the rest of the world) i believe what's munging the uri is vmware's nat stuff (just like paral [04:47] it was easy for me to kill the 'fake network devices' under os x and linux not sure how to do that under windows [04:48] habakuk (n=chatzill@c-24-6-224-243.hsd1.ca.comcast.net) left irc: "Chatzilla 0.9.77 [Firefox 1.5.0.9/2006120612]" [04:49] aha found out how to disable (duh.. it's windows.. look in the network connections panel ... sigh ;) ) [04:53] Jadestorm: its possible to use openser as an ALG. ;) [04:53] Ali.G? ;) [04:54] yep! [04:54] Jadestorm: textops module. [04:54] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) joined #openser. [04:54] ohhhhhh [05:08] so back to my general question =) [05:08] is there an extension or something above and beyond sip support that the server itself needs to be capable of to handle clients wanting to do SIMPLE communication? [05:24] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) left irc: Read error: 104 (Connection reset by peer) [05:25] Jadestorm (n=Jadestor@cpe-024-163-106-248.nc.res.rr.com) left irc: [05:37] variable_office (n=variable@cerberus.iswan.net) joined #openser. [05:37] can openser run php scripts to help with routing? [05:54] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) joined #openser. [06:23] hansi (n=chatzill@58.71.34.138) left irc: "Chatzilla 0.9.77 [Firefox 2.0.0.1/2006120814]" [06:25] hansi (n=chatzill@58.71.34.137) joined #openser. [07:01] variable_office: no [07:01] but you will have perl in 1.2 [07:01] ttyS1 (n=ttys1@ool-45786a28.dyn.optonline.net) left irc: [07:01] osas: any bright ideas on why media proxy refuses to do database accounting? [07:02] no [07:02] loverly [07:02] my idea (right now) is to go to bed :p [07:03] check for logs ... [07:03] nothing in logs [07:03] nothing in strace [07:03] well .. post to the list [07:03] you will get an answer [07:04] acehunky (n=chat_jok@59.184.52.66) joined #openser. [07:04] i doubt it [07:04] I don't think that you are the only oone trying to get acc working with medoiaproxy [07:04] ppl are pretty responsive on the list [07:04] i'm moving forward with writing my own mediaproxy application in C [07:04] give it a try [07:05] see you tomorrow guys ... [07:08] does any one know how to create hunt list in openser ? [07:22] hunt list? [07:26] CrazyTux (n=CrazyTux@64.95.219.140) got netsplit. [07:26] JerJer (n=PhatJ@pdpc/supporter/bronze/jerjer) got netsplit. [07:26] kavit (n=kavit@ppp244-74.static.internode.on.net) got netsplit. [07:26] bobhonka (n=markus@markus.netzquadrat.de) got netsplit. [07:26] acehunky (n=chat_jok@59.184.52.66) got netsplit. [07:26] hansi (n=chatzill@58.71.34.137) got netsplit. [07:26] Defraz (n=t0tal@24-116-152-177.cpe.cableone.net) got netsplit. [07:26] _Bilbo_ (n=bastian@mail.collax.com) got netsplit. [07:26] brettnem (n=brettnem@72.29.102.158) got netsplit. [07:26] osas (n=nnnnnnnn@CABLE-72-53-75-252.cia.com) got netsplit. [07:26] Eimann (i=eimann@chaconne.etherkiller.de) got netsplit. [07:26] _Vile (n=vile@bc182112.bendcable.com) got netsplit. [07:26] rpm (n=russell@66.119.170.34) got netsplit. [07:26] qdk (n=qdk@90.184.3.249) got netsplit. [07:26] cableroy (n=cableroy@noc.mtulink.no) got netsplit. [07:27] acehunky (n=chat_jok@59.184.52.66) returned to #openser. [07:27] hansi (n=chatzill@58.71.34.137) returned to #openser. [07:27] Defraz (n=t0tal@24-116-152-177.cpe.cableone.net) returned to #openser. [07:27] CrazyTux (n=CrazyTux@64.95.219.140) returned to #openser. [07:27] qdk (n=qdk@90.184.3.249) returned to #openser. [07:27] _Bilbo_ (n=bastian@mail.collax.com) returned to #openser. [07:27] JerJer (n=PhatJ@pdpc/supporter/bronze/jerjer) returned to #openser. [07:27] kavit (n=kavit@ppp244-74.static.internode.on.net) returned to #openser. [07:27] bobhonka (n=markus@markus.netzquadrat.de) returned to #openser. [07:27] Eimann (i=eimann@chaconne.etherkiller.de) returned to #openser. [07:27] cableroy (n=cableroy@noc.mtulink.no) returned to #openser. [07:27] brettnem (n=brettnem@72.29.102.158) returned to #openser. [07:27] osas (n=nnnnnnnn@CABLE-72-53-75-252.cia.com) returned to #openser. [07:27] _Vile (n=vile@bc182112.bendcable.com) returned to #openser. [07:27] rpm (n=russell@66.119.170.34) returned to #openser. [07:33] acehunky: eeek [07:38] i use asterisk for that sort of logic [07:39] take note of the promiscredir sip configuration setting :) [07:39] something like that [08:17] acehunky (n=chat_jok@59.184.52.66) left irc: Read error: 110 (Connection timed out) [09:08] CunningPike (n=CunningP@204.239.8.149) left irc: "And so, to bed" [09:09] qdk (n=qdk@90.184.3.249) left irc: Read error: 145 (Connection timed out) [09:15] henning (n=henning@et-1-5.gw-nat.bs.ka.oneandone.net) joined #openser. [09:38] qdk (n=qdk@193.164.155.19) joined #openser. [09:40] henning (n=henning@et-1-5.gw-nat.bs.ka.oneandone.net) left irc: Remote closed the connection [09:48] henning_ (n=henning@et-1-5.gw-nat.bs.ka.oneandone.net) joined #openser. [10:22] osas: perl??????? wow nice! [10:31] <_Bilbo_> :) [11:24] hansi (n=chatzill@58.71.34.137) left irc: Remote closed the connection [11:25] roffel (n=rolf@82.196.214.14) left irc: Read error: 110 (Connection timed out) [11:35] L|NUX (n=linux@unaffiliated/lnux/x-10290) joined #openser. [12:03] baron_ (n=kvirc@port-212-202-252-157.static.qsc.de) joined #openser. [12:07] _Vile (n=vile@bc182112.bendcable.com) left irc: Read error: 110 (Connection timed out) [12:38] DanB (n=danbogos@87.139.12.167) joined #openser. [12:38] Hello! [12:39] Hi DanB [12:40] Hey L-info! [12:42] qdk (n=qdk@193.164.155.19) left irc: Read error: 113 (No route to host) [12:50] hi all [13:07] qdk (n=qdk@90.184.3.249) joined #openser. [13:30] apardo (n=apardo@87.217.144.130) joined #openser. [13:36] miconda (n=daniel@81.180.83.75) joined #openser. [14:06] _Vile (n=vile@bc182112.bendcable.com) joined #openser. [14:24] L|NUX (n=linux@unaffiliated/lnux/x-10290) left irc: [14:48] hohum (n=dcorbe@c-71-62-76-68.hsd1.va.comcast.net) left irc: "This computer has gone to sleep" [15:16] apardo_ (n=apardo@87.217.144.34) joined #openser. [15:16] Jadestorm (n=daniel@ghidora.unity.ncsu.edu) joined #openser. [15:17] apardo (n=apardo@87.217.144.130) left irc: Nick collision from services. [15:17] Nick change: apardo_ -> apardo [15:36] cableroy (n=cableroy@noc.mtulink.no) left irc: Read error: 131 (Connection reset by peer) [16:00] hohum (n=dcorbe@mercury.sunrocket.com) joined #openser. [16:34] hello [16:35] Nick change: bobhonka -> mmarkus [16:48] L|NUX (n=linux@unaffiliated/lnux/x-10290) joined #openser. [16:49] henning_ (n=henning@et-1-5.gw-nat.bs.ka.oneandone.net) left irc: Remote closed the connection [16:55] hello [17:10] quite here today ;) [17:12] yup [17:12] there was some activity a few hours ago :-) [17:16] people hunting bugs in 1.2.0 .. that's all .. :-) [17:22] hohum (n=dcorbe@mercury.sunrocket.com) left irc: Client Quit [17:23] hohum (n=dcorbe@mercury.sunrocket.com) joined #openser. [17:26] lemme ask y'all something [17:26] when you installed openser the first time.. did it just work dandy for you, no problems what-so-ever? [17:26] or did you have to do a lot of fiddling? [17:30] apardo (n=apardo@87.217.144.34) left irc: Remote closed the connection [17:32] it all depends on what you want to do and how much reading have you done before :-) [17:33] and also your experience with SIP matters [17:34] but to use it as a registrar and route call between subscribers, that should work out if the box [17:34] s/if/of/ [17:34] i mean all i'm trying to do is set up something that i can use sip/simple clients with [17:34] like that i can connect to from gaim 2 and/or adium x just fine [17:35] then you need to play with the config [17:35] variable_office (n=variable@cerberus.iswan.net) left irc: [17:35] and do some reading [17:35] this is new in 1.2 [17:36] is it? so the server itself -does- need to "actually support simple"? [17:36] i couldn't get an answer as to whether all was required is a sip server or you had to have a sip server that was capable of simple [17:36] I'm not sure (never tried it) [17:36] search the docs [17:36] the 1.2 section under modules [17:36] and post your questions to the list [17:37] variable_office (n=variable@cerberus.iswan.net) joined #openser. [17:37] hrm ok [17:37] you need simple support in the sip server [17:41] shroomy (i=antilove@zolo.freelsd.net) joined #openser. [18:51] Defraz (n=t0tal@24-116-152-177.cpe.cableone.net) left irc: "Trillian (http://www.ceruleanstudios.com" [18:54] Nick change: DanB -> DannyB [18:55] DannyB (n=danbogos@87.139.12.167) left irc: "Client exited" [18:55] CunningPike (n=CunningP@dhcp-10-234.district.north-van.bc.ca) joined #openser. [19:08] cmax (n=osas@milo.blarg.net) left irc: Read error: 110 (Connection timed out) [19:31] miconda (n=daniel@81.180.83.75) left #openser. [20:58] L|NUX (n=linux@unaffiliated/lnux/x-10290) left irc: "Leaving" [21:11] L|NUX (n=linux@unaffiliated/lnux/x-10290) joined #openser. [21:18] L|NUX (n=linux@unaffiliated/lnux/x-10290) left irc: [21:19] apardo (n=apardo@87.217.144.34) joined #openser. [21:20] Defraz_ (n=t0tal@fw.centrisys.com) joined #openser. [22:36] dwery (n=dwery@nslu2-linux/dwery) left #openser. [22:43] Defraz_ (n=t0tal@fw.centrisys.com) left irc: Read error: 54 (Connection reset by peer) [22:45] Nix (n=Nix@81.213.125.220) joined #openser. [22:47] osas: i had to run off but thanks, that's what i needed to hear to steer me in the right path ;) [22:59] Jadestorm (n=daniel@ghidora.unity.ncsu.edu) left irc: [23:04] cmax (n=osas@milo.blarg.net) joined #openser. [23:13] apardo (n=apardo@87.217.144.34) left irc: Remote closed the connection [23:14] Defraz_ (n=t0tal@fw.centrisys.com) joined #openser. [00:00] --- Wed Feb 21 2007