logs archiveBotHelp.net / Freenode / #2600hz / 2015 / September / 18 / 1
hmmhesays
Does directed call pickup using the replaces header work?
lazedo
hmmhesays: yes
hmmhesays
I must be doing something goofy then I can get it to work using polycom's directed call pickup method legacy and ** along with a callflow to match
That works but making a separate call flow for each group pickup sucks
it seem the CID is displayed wrong on the monitored line also. kfp+ shows up
neurosys
hmmhesays: Polycom?
hmmhesays: vvx?
hmmhesays
neurosys, yeah I see there may be a problem in 5.4?
neurosys
yep
hmmhesays: go back to 5.3 and you'll be ok
hmmhesays
will my cid on the monitored line still be goofy?
neurosys
hmmhesays: well i dunno what your CID is. But my are pretty normal ;)
hmmhesays
I'm getting two notify messages coming in
the first notify is correct the second has identity display of <identity display="bria1">sip:kfp+47feb64df1cb</identity>\n
why it's sending two notify's I do not know
both are state early
it seems there is no reason for this
wtf 5.3.1 still isn't sending out a replaces header
lazedo
hmmhesays: mine is 5.3.0.12074
hmmhesays: make sure you use automata
hmmhesays
I moved back to 5.3.1
I'll go back one more minor rev
I'm on 5.3.0.12074 now and it still is not sending out a replaces header
lazedo, I still must be missing something
][Sipster][
Hi, I need to capture a 800 number and dial a local number instead. It needs to be available to all the accounts.
hmmhesays
pyite
pyite
hmmhesays:
][Sipster][: add it as an offnet route that loops back via your carrier
i dont know another way to do it
hmmhesays
polycom and your fast pickup stuff are frustrating me
voxter, you around?
][Sipster][
pyite: Thanks, will try
pyite
hmmhesays: hmmm
does it not work?
lazedo and k_anderson believe it works :)
lazedo
pyite: im sure it works :) polycom, cisco, gradstream, bria tested here
pyite
hmmhesays: whats the issue?
morning lazedo ;-)
lazedo
morning pyite
hmmhesays
it must be a polycom config issue, I can't get it to send out a replaces header on the new invite
lazedo
hmmhesays: did you set it as automata ?
hmmhesays
lazedo yes and I'm on 5.3.0.12074
lazedo
hmmhesays: there are coule of other settings you need to set directly in configuration
hmmhesays: let me get them for you
hmmhesays
directedcallpickupmethod native
directedcallpickupstring blank
lazedo
hmmhesays: https://gist.github.com/lazedo/9894769f71ce804c3451
hmmhesays
I'll take a look thanks
lazedo, isn't this if your type is resource type is normal attendant.behaviors.display.spontaneousCallAppearances.normal="0"?
alpha-z
hey pyite, offnet route that loops back via carrier... sounds like a mouth full.
pyite
alpha-z: heh ummmm
if you say it really really fast it doesnt sound so bad?
;-)
lazedo
hmmhesays: that one i use for having popup appearing after parking
alpha-z
:D kazoo should implement some kind of dialplan mechanism.. where you can actually tell calls where to go
pyite
alpha-z: thats called a callflow
but he doesnt want to add one to every account
in which case, its an offnet route
lazedo
alpha-z: and dialplan
pyite
:-D
alpha-z
really? a callflow can take internal calls ?
hmmhesays
callflow takes all calls does it not?
alpha-z
whadya know i learn something new every day.
pyite
i must be using different terminology? i dont understand what youre saying
alpha-z
for ex. extension 123 dials 18881234567
pyite
just make a callflow for 123
alpha-z
huh?
pyite
that maps to a device which is a landline for 18881234567
easy enough
then dialing 123 routes to 18881234567
alpha-z
dont i need a callflow for 18881234567
pyite
no
why would you?
device landline == call forwarding essentially
you are just fowrarding the call to a PSTN number or whatever
you can forward to a SIP uri if you want, too
callflow would just be for 123
you would actually NOT want to ever make a callflow for 18881234567 if its not your number or if its in a different account
that would confuse the system
alpha-z
but how do you make a call flow for 1 ext only?
when you click add call flow, the add number applies to the number thats dialed
not the source
pyite
huh?
alpha-z
in kazoo, if you click callflows in hostedpbx, and then click add callflow, the dialog that shows up for call flow it says click to add number, that number is the number that people dial, not the source extension
i'm saying if extension device 123 picks up the phone and dials 18881234567 and he wants that to go to 1111111111
hmmhesays
lazedo, this must have been it voIpProt.SIP.strictReplacesHeader="0"
lazedo
hmmhesays: welcome to fast pickup lane :)
alpha-z
would you not have to create the callflow for 18881234567 in that case? theres no options in callflow to set for source caller, only destination pyite?
hmmhesays
so second question, why does the CID show up on the subscribed line as kfp+XXXXXXXX?
pyite
alpha-z: i dont think thats the scenario were talking about
i thought you said dialing 123 routes to 18881234567"
in that case, youre creating an extension called 123
alpha-z
ya absolutely
pyite
and it maps to a device, which is a landline device that forwards to 18881234567
you do not need to put 18881234567 into a callflow
its part of the device definition for the forwarding only
alpha-z
right,
i guess we were just misunderstanding about which scenario we're talking about :D
pyite
apparently
if you are actually saying you want a real 10-digit number to be re-mapped
« prev 1 2 next »