logs archiveBotHelp.net / Freenode / #2600hz / 2015 / September / 18 / 2
pyite
then, yes, you can add that as the number in the callflow
and it will hijack it for that account only
if thats what youre trying to do
alpha-z
right,
pyite
the bottom line is the system will scan the current account for ANY matches first before even attempting an offnet dial
if it finds one, it finds one
it will use it
alpha-z
really?
i know thats the case for extensions
but for phone numbers i recall having to do some strange couch db thing
to change the classification
of the number before it will dial internally
ie if i have did 1234567890, and one of my extensions dialed 1234567890, unless i change the number classification in the doc, it will dial out the provider then come right back in fron provider.
hmmhesays
there is only two references to the kfp+ in kamailio route script
so how does the fast parking work. Do you need a call flow to support that?
and what exactly is fast pickup doing over whatever was done before?
alright my directed call pickup calls are failing after 60 seconds
actually directed call pickup is hanging up right after the amount of time the callflow is set to ring
cf_user:45 (<0.19793.237>) error bridging to user: timeout
alpha-z
sad.. errors are sad.
hmmhesays
other people seem to have this working
alpha-z
have what working?
not quite sure what you're trying to do
hmmhesays
directed call pickup
alpha-z
dunno what that means
hmmhesays
pick up a ringing extension from another endpoint
alpha-z
errr.. so say extension 101 is ringing but 102 is not you wanna pick up 101 from 102?
hmmhesays
correct
kazoo doesn't seem to see the call as answered after the pickup and it times out
alpha-z
sorry dunno how to help you on that, never had the need for that use case
is there any fax frontend for kazoo?
hmmhesays
lazedo, do you have directed call pickup working correctly? The settings you gave me do intercept the call but it drops after
lazedo
hmmhesays: yep
hmmhesays
lazedo, I'm having an issue where the call is hung up after the ring time specified in the callflow
have you ever run into that?
lazedo
what callflow ?
hmmhesays
just an extension that calls a user
a calls b, c intercepts a and the call drops after the ring time specified for b
along with this message in the kazoo logs cf_user:45 (<0.19793.237>) error bridging to user: timeout
lazedo
hmmhesays: whats your setup ? all in one ?
hmmhesays
lazedo, yeah for now
obviously kazoo is not recognizing that the call has been connected elsewhere
lazedo
hmmhesays: cpuld be freeswitch, what version of fs ?
hmmhesays
the version that is packaged with 3.21
This doesn't seem like a freeswitch issue if kazoo is claiming timeout
This has to be a config issue if you've got it working
No this isn't freeswitch 2015-09-18 17:35:44.886941 [INFO] kazoo_node.c:625 exec: uuid_kill(126264NDIwOTZhOGI3YTExZjIzMzlkODNkZjk4YmQ0MmM2MGE)
This is kazoo killing the call because it thinks there is a timeout for sure
alpha-z
my guess is fs did the hijacking and kazoo knows nothing about it,
hmmhesays
kazoo kills the channel
it's in the kazoo logs and the freeswitch logs
« prev 1 2