logs archiveBotHelp.net / Freenode / #2600hz / 2015 / July / 27 / 1
voxter
lazedo: http://notepad.cc/briepalsi47 My notes, some logs, some packet captures, if you wouldn't mind taking a look?
ZeroCool
Whats up
Does anyone chat on this ?
What are you all doing sigh
This is boring guys are you all involved in some kind of pm conspiracy
😞
lazedo
voxter: it does work on 5.3, why are you saying there was a bug in 5.3 firmware ?
sam_____
hi
i like to use a web interface for freeswitch can anyone suggest good one
][Sipster][
sam_____: if Kazoo is too much for what you want to do, you can look at #fusionpbx
lucasb_
Morning folks! Have a question regarding Crossbar API - is there a method that allows one to validate a current/existing API token?
I've looked at user_auth which appears to only allow a PUT for creating a new session and token_auth that appears to be used to DELETE a token/session
voxter
lazedo: Did you see the notes i linked to? That part of the config doesn't appear to be acting as expected for parked call pickup?
lazedo
voxter: hey man, i do remember everything working for you, what have you done ? it still works for me on 5.3 firmware
lucasb_
I should rephrase, I am talking about Authentication Tokens, not the static API tockens
lazedo
voxter: check the kamailio logs, you should have something like fast pickup found redirecting
voxter
lazedo: haha - when we worked on this before, we were working on directed pickup, and that still works perfectly! The issue seems to be with parked calls. I found the place in the kamailio config that I would expect it to succeed at
lazedo: when i do just a regular directed pickup for a regular call - everything is perfect. works 100%
lazedo
voxter: direct cal pickup and park act the same way
voxter
lazedo: its just when i park a call, then go to pick it back up again, the place it does a kazoo_query seems to fail, but I dont understand why the "if" is failing
lazedo: here are my logs/notes: http://notepad.cc/briepalsi47
lazedo
voxter: if it does a kazoo_query youre not using fast pickup
voxter
lazedo: https://github.com/2600hz/kazoo-configs/blob/master/kamailio/fast-pickup-role.cfg#L39
isnt this the code that executes when it sees a Replaces header?
oh, I see, the block above it looks for sip:kfp+
so, once I upgraded to 5.4 the sip:kfp stuff went away and it just started dialing *31 again
but i upgraded to 5.4 BEFORE updating to this fast-pickup-role config.
maybe I should downgrade and retry
lazedo
voxter: exactly, then something is wrong in 5.4 or misconfigured. did you set it to automata ?
voxter
cause this is the code its executing now, and its certainly "failing" - it takes upwards of 30 seconds to find + pick up the call now, cause this "replaces call-id" retries like 4 times
neurosys
voxter: Is this a Soundpoint or VVX?
lazedo
voxter: dont rush on downgrading, check your phone configuration
voxter
lazedo: yep, its automata. Let me downgrade to 5.3 here and see what I can get it to do
lazedo
voxter: and make sure you have automata
voxter
lazedo: other guys in here have mentioned that as of 5.4, polycom changed something in their firmware
it is automata, for sure
neurosys
voxter: All my VVXs on 5.3 and 5.4 have no issues. no crazy config :(
voxter
lazedo: it used to dial sip:kfp+blahblah, and now it dials *31 - somethign to do with polycom changing their park pickup code.
OK, well I have a vvx on 5.3, a vvx on 5.4, and an ip 650 on 4.0.9
I'll go re try them all after the tweaks i did to upgrade kamailio to this latest config on the weekend and see what hapepns.
neurosys: on 5.4, whats currently happening, is it "Works" but it takes 10-40 seconds to actually connect you to the caller on pickup, cause its timing out doing kazoo_query's
neurosys: any chance you could do a park/pickup on one of your 5.4 phones and show me your kamailio log for that call?
neurosys
voxter: sure gimmie a few
voxter
thanks dude, really appreciate it!
I still wouldnt expect the kazoo query to fail on line 39 of that file, if 5.4 wasnt sending that in the To: any more.....
lazedo
voxter: ttyl, conf call
voxter
lazedo: sounds good. i'll let you know where i get! thx!
OK so the ip650 on this config is working, it looks like
saratogga
anyone from 2600hz around?
JR^2
saratogga: yes?
saratogga
I want to start offering local businesses with a hosted PBX product. Basically a more boutique version of a PBX provider vs. them going with a large vendor such as RingCentral. Is this essentially what I can do with 2600hz?
JR^2
yes
if you have more questions, you can contact sales@2600hz.com which will answer all of them better than I can
saratogga
Is it the case that basically it's fully open source but I can have you guys run it on a managed basis w/ hosting and all of that?
Otherwise someone can just go and host it themselves?
JR^2
yep exactly
saratogga
Do you offer automatic phone provisioning?
JR^2
on supported models yes
saratogga
Where can I see screenshots of what the end product looks like for the business end-user? ie. their administration portal and employee access pages?
neurosys
voxter: ok... doing this now. pasteie i a few moments..
voxter
neurosys: so for me, on 5.4, it doesnt attempt to send sip:kfp+bababa in the To: anymore, it sends *31 - which makes it execute diffrerently than the other phones
neurosys: awesome! thanks~!
neurosys
voxter: check PM ;)
mc_
saratogga: if you contact sales, they can set you up with a demo account, do dog and pony show, etc
would be easiest if you just want to sell it
i think youtube may have some videos with the UI being shown too
voxter
lazedo: so, im not exactly sure what it is between polycom 5.3 and 5.4 firmware - if you're using parkedCallRetrieveMethod (or directedPickupMethod) of "native", which tells it to send the Replaces header - on firmware prior to 5.4, it actually sends sip:kfp+UUID in the "To:" header. In 5.4, it sends "*31" - the kamailio code that looks for ~ru containing sip:kfp+ at the beginning DOES work. However, since the vvx in 5.4+ doesnt send sip:kfp+ any more
(maybe changeable in config?) that code doesnt execute, and instead it executes the block i linked to in github, line 39. And, it fails.
saratogga
mc_: thanks, yes, I think I'll just contact them and get the process started
voxter
it eventually still works - but only after it does some kazoo queries a few times and eventually fails and just passes on to dialplan pickup
it just results in a long delay for the pickup
lazedo
voxter: there must some config in 5.4 to still send the kfp, maybe its sending in replaces header ? can you get a sip trace of what 5.4 seds to kamailio ?
voxter: try to read the changes from 5.3 to 5.4 maybe theres a clue there
voxter: the delay is because of the query, you can comment that section
voxter
lazedo: yeah, took a look but nothing stood out for pickup or dialog... just comparing against 5.3 first to see what the difference is in the invites
lazedo: now, if i commented that out, wouldn't that affect regular directed call pickups? or should those send kfp+ too? I'll do a couple tests here to see.
neurosys
voxter: Its like its grabbing teh wrong ID, no?
voxter
neurosys: you're trying it now too?
lazedo: any idea why that query is failing in the first place? based on the query+response i see, it doesnt actually *look* like its failing, but... it is
neurosys
voxter: yep on 5.4
voxter
neurosys: so, what part is getting stuck for you?
the pickup?
neurosys
voxter: yep
voxter
neurosys: gotcha.. and on the screen, do you see it sending *31 or sip:kfp+blbhalbh
neurosys
voxter: trying to verify now - but looks like its grabbing the wrong CID
it shows *31
also in the logs
voxter
gotcha
neurosys
voxter: from what I see... the fast pickup has the right CID but it connects incorrectly
voxter
neurosys: right, so, on 5.3 its sending the sip:kfp stuff properly
on 5.4 the invite is sending *31 instead
when that happens, what you're probably seeing is what i was seeing...
the "replaces call-id" log repeats itself a couple times
then it finally times out on those queries, and just goes staight to dialplan pickup, and works
like lazedo was saying, they've modified default behavior somehow in 5.4 - i also notice that the "old" buddy watch BLF doesnt work on 5.4 at all any more either.
neurosys
voxter: yeah
voxter
so its clearly changed the way dialogs are handled
neurosys
voxter: wait when you park you dont see the BLF blink?
voxter
you can downgrade to 5.3 and it works, or someone will have to dig into the changes and new config in 5.4 and figure out what to change to make it behave the '5.3 way'
neurosys: it blinks
1 2 next »