Jump to content

Recommended Posts

  • Administrators
Posted
Is this also popular? We get this request but mostly from overseas places where DIDs aren't cheap.

The problem with these is fax machines that don't make a tone. Some still exist, or try to do answer detection and don't like hitting an IVR. This then, of course, generates support tickets.

We could potentially implement this but I wonder if the demand is really that high? Also, it would probably only work for IVRs because Faxboxes have nothing to do technically with voicemail boxes so on individual users I don't know how, once you're in a voicemail box and we hear a tone, we'd be able to figure out which faxbox it maps to. Maybe in SmartPBX we could just assume it's the same user and in advanced callflows we could let you manually set a mailbox.
Posted
Most of our clients have dedicated fax lines, but we are discussing a low-cost forwarding service for consultants and freelancers that includes having a single DID with fax detection as a compelling feature.  
  • Administrators
Posted
So based on the interest in this question I asked our team to dig into this. It turns out there is infact call detection already built in, I just didn't know about it ;-)

Luis has documented it. I don't think a single person has tested this so please try it out and feel free to report back your results.

https://github.com/2600hz/kazoo/blob/master/applications/callflow/doc/fax_detect.md

Please note, I think 3 second default is too short. I've put in a ticket to make it 4 or 5. But it should really just work.
Posted
Glad you asked, Karl. In the same boat with you on this - mission today is to finally figure out how to build these callflows out sans portal.  Let me know if you figure it out?  ;)
Posted
@Darren - perhaps this needs to be incorporated as part of a callflow element(s) (those that answer/ listen). I don't think most people on this board are going to write the callflow JSON necessary to configure the two child callflows for fax or voice.  
  • Administrators
Posted
@FASTDEVICE I agree. That said, this feature has a significant impact on call processing (tone detection is expensive). I'd like to see a small number of people try it first before we commit to formally rolling it out to all via an easy-to-use GUI. We can take the feedback from those that tinker with it and make sure it works / is better before rolling it to the masses. So let's consider this a beta test at this point. In the meantime, I'll meet internally with folks to figure out how to add it to the callflow editor.

There are enough people who know JSON and can use Curl that perhaps we just start there (I think you're one of them?)

In parallel, we can work on making it available via the callflow editor via the design team.
Posted
@lazedo - awesome recommendation. I've been playing with Postman for about an hour and easily recreated a collection similar to the developer API in the prior Kazoo UI. Thanks! 
  • 3 weeks later...
  • 1 year later...
Posted

Really nice! Glad to help in any way I can... Unfortunately I'm not very skilled in Erlang, but PHP, Javascript, CSS, HTML5. Bug testing also!
If any interest, please PM me! :)

  • 2 years later...
Posted
On 4/14/2016 at 6:16 PM, FASTDEVICE said:

Sorry it took so long to get back to you on this, but my team was working to deliver our new user portal.

We have tested the fax detect callflow and IT WORKS!

Hello @FASTDEVICE

May i know how you write the callflow for fax detect?

Regards

Naveed

  • 3 years later...
Posted

Hey there, I took a shot at getting this to work on the front end. I was able to create a call flow element using the documentation listed below. I was able to get the call to route to the ON_VOICE side but all faxes failed to detect the fax tone and routed to the voice side. After looking at the backend logs it failed to detect the fax.

×
×
  • Create New...