logs archiveBotHelp.net / Freenode / #2600hz / 2015 / July / 28 / 1
voxter
lazedo: /msg'ed you a pcap - let me know if you want me to get it to you some other way
BB-Aud
voxter/lazedo - just following along, and yeah, seeing the same thing from my side. voicemail after 30 seconds, 5-10 delay on pickup, etc.
voxter
BB-Aud: so, if you do firmware 5.3 (or 5.3.1) and use directedPickupMethod and callParkRetrieveMethod of "native" along with automata BLF keys
BB-Aud
for me <5.4 wouldn't work on the pickup at all - it would just dial the number of the person in park, but other than that, seeing same thing.
lazedo
voxter: the problem is that the ua is using local part of the notify and it should be using the remote because thats the one it should try to replace, it works well on 5.3 and in others (cisco, gradstream,yealink,bria,&)
voxter
as long as you're on the newer kamailio configs with the fast-pickup-role.cfg file, the quick pickup should work
lazedo: it seemed like it was using the wrong part, yeah
lazedo
voxter: bt maybe there is some configuration in your polycom that with 5.4 behaves differently
voxter
there's something different about 5.4 for sure, because the oldschool "buddy watch" presence on polycom (that we know is also not fully supported in kamailio's config today) went from lighting up at least green to getting no status at all
so they've changed BLF dialog behavior in 5.4 significantly
I dont know what the config is to revert it, so ill just stick with 5.3.1
lazedo
voxter: can you profile the cfg for the polycom with the 5.4 formware ?
voxter
lazedo: yeah, ill have to do some comparisons with the default firmware config they ship - i looked in the changelog notes and nothing at all stands out to be related to this
BB-Aud
voxter: will pull up config to be sure, but yeah - native and using automata
voxter
lazedo: do you think if i upgrade to the newer 1.4.7-11 of freeswitch, that we wont have that a-leg pickup issue where the call continues to voicemail?
BB-Aud: i also had to set usesStrictReplacesHeader = 0
er, useSrictReplacesHeader
lazedo
voxter: no, i think not
voxter
lazedo: ok, so would have to recompile or wait for the next release then?
or is it an ecallmgr thing
lazedo
voxter: in your capture , i dont see the invite to place the call in parking slot, so i beliee that your config may be wrong
voxter
lazedo: i would suspect my capture might be incomplete if thats the case. let me see if i can find it. it would be the first interaction to *31
lazedo
voxter: its not there, and refer also not there
voxter
lazedo: i used ngrep to capture it, i can redo it with a better filter
ill redo it right now one sec.
lazedo
voxter: i think its your config , almost sure
voxter got to go now, if you want you may send me your polycom config offrecord (remove any passwords)
neurosys
lazedo: I tested this on the patest yealink firmware for T4x and it also does the same bad behavior
lazedo
neurosys: its your config
voxter
lazedo: uploaded another pcap, i see the refer in it, let me know if you dont. same filename, just re-request it.
neurosys
lazedo: the phone or you mean my cluster?
voxter
lazedo: this is the identical config on 5.4 as 5.3
ReallyNotPatrick
pyite you there?
sappel
Good Morning everyone, anyone alive? :)
Can anyone help me understanding the difference of kazoo, bluebox, kamailio, asterisk and freeswitch?
Is Kazoo acting as a SIP Proxy? Or is it "just" a powerful GUI for kamailio + freeswitch/asterisk?
well, talking about the dedicated cluster scenario
mrgab_
Hi, i have a codec related issue. is it possible to avoid transcoding in this scenario?:
- Alice calls Kazoo offering PMCA, G729. Kazoo play a media in PMCA and then bridge the call to Bob that offer G729
i saw that in this case we have PMCA to G729 transcoding, and i'm wondering if it is possible to re-negotiate codec in a way to use G729. Thanks in advance
neurosys
lazedo: good morning sir
lazedo
neurosys: good morning
neurosys
lazedo: So we never clarified: you think the fast pickup is a cluster config issue on my part or the phones?
lazedo
neurosys: maybe both
neurosys: fast pickup is working great so far, so.., it must be something in your configs, either kamailio or phone or both
neurosys
lazedo: Ok. Im freeswitch-R15B-1.4.7-4 and kamailio-4.2.3-16
lazedo
neurosys: you should upgrage freeswitch version, i believe kazoo-pickup was added in Sep 19
neurosys
lazedo: 10-4 Ill give it a whirl :)
lazedo: welp updated my FS to 1.4.7-11 and it worked flawlessly with yealink and poly 5.3
Gonna update to 5.4 and see if i have the issue voxter is having
lazedo
neurosys: :)
neurosys
lazedo: Interesting. Now i get teh voxter issue with 5.4
lazedo: worked fine with 5.3
lazedo
neurosys: havent tried 5.4 yet, bu it should be some config, maybe a default has changed from 5.3 to 5.4, so if not configured could change behaviour
ThanhPhuc-
hi team!
Precious
anyone here?
mark2600
(Action) waves
Precious
hi mrgap
mrgab_
hi Precious
sappel
Hello again :)
« prev next »