logs archiveBotHelp.net / Freenode / #2600hz / 2015 / August / 14 / 2
voxter
so if you show up on udp 5060 and dont get handled by nathelper via nat_uac_test(3) , it would skip cached creds
lazedo: is the new work all happening in private for now?
lazedo
voxter: no, you can watch branch vNext in kazoo-configs
voxter
oh, dang, i missed that
can i run these against 4.2.3 or should i upgrade to newer kamailio? and do i need to be on 3.21+?
lazedo
voxter: run our kamailio 4.3.1-3 from latest
voxter
i would love to know more about pusher :)
this antiflood stuff looks awesome too
lazedo
voxter: as for kazoo, i always run master, so i wouldnt know
voxter
lazedo: haha, ok :)
its time to upgrade to 3.21 anyways, because we need to submit like 50 pulls before kazoocon
did a whole ton of work in acdc and konami
lazedo
voxter: way to go :)ยด
voxter
i think konami still needs some more attention, but it solved a bunch of edge cases we hit
lazedo
voxter: make sure we have time to review them and merged them, were also making a lot of work for kazoocon
voxter
lazedo: yeah i hope to have it all done next week
im sure it will take a couple back-and-forths
lazedo
voxter: thats the spirit
voxter: vNext kamailio wqill handle pretty easily 8000 regs/sec on sh*tty hardware (mine)
voxter
we've also implemented some stuff thats really specific to us - maybe we can offer it back in as a specific option.. for instance, our provisioner uses vmbox pin and user pin to do hotdesking
so we have an option that makes it so when you change your user pin, it auto-changes your vm pin for you (and vice versa) so they always stay in sync
lazedo
voxter: without caching creds
voxter
lazedo: nice!!
lazedo
voxter: :) thats cool the vm pin
voxter
lazedo: the reason it handled fewer regs without caching is cause it went through to whapps and bigcouch
i know that handles better with more than 2 registrar's
(Whapps)
lazedo
voxter: you now have the option to increase the number of registrar listeners on registrar app
voxter
lazedo: sweet, karl was saying that was coming last week at cluecon
that will be a big help
lazedo
voxter: so that one whapp running registrar can dispatch a lot more messages
voxter
lazedo: do you guys offer your spec files for building rpms?
lazedo: we want to get into releasing our own rpm's for patches that havent made it back upstream yet, but it would be a huge timesaver if i could just recompile + rpmbuild with the same spec files you guys start from
lazedo
voxter: kazoo , kazoo-config are simple, just mention the files to install
j4m3s
(Action) waves at voxter
btracht00
if 1 of my 3 DBs goes down (drive crash...whatever) if i replace it with new server will bigcouch rebuild dbs?
no need to manually rebuild anything on new server as long as it was part of the original cluster, correct?
just put bigcouch on and go...
mc_: if 1 of my 3 DBs goes down (drive crash...whatever) if i replace it with new server will bigcouch rebuild dbs?
just put bigcouch on and go...
mc_
btracht00: yup, as long as it has the same hostname as the failed node
when it starts up, the other nodes will reach out to it and populate its disk with the dbs it should be storing
btracht00
if new account is created while node is down will it create the new db or only the existing ones when it went down
mc_
btracht00: it will still be "Created" on the down down (if its supposed to)
when the down node comes up, its peers will tell it about the new db
it all depends on your n and w params in that case
btracht00
mc_: thanks. all default q r w n
voxter
lazedo: were you saying ysterday that in the kamailio vNext configs, you've already done the 302's outside of having to pass through to kazoo? or is that still pending on the roadmap?
lazedo
voxter: i think its there, yes
voxter
lazedo: Im trying to backport the 302 stuff you did in vnext to my current configs - it looks like you had already done what i was basically trying to accomplish! :) the only thing is, it currently seems to fail when actually trying to dispatch. I see two of these just after the 'pass' logline:
ERROR: tm [t_lookup.c:1126]: t_check_msg(): ERROR: INVITE reply cannot be parsed
then it removes the redirect mapping and fails
I lied, it seems ot be working. that was me screwing with which freeswitch server was active
for the record, it appears as though all I had to do was manually apply this patch:
https://github.com/2600hz/kazoo-configs/commit/8f130edcb427765f58e888dedba8430ce7a944e8
« prev 1 2 next »