Tag / flowroute

by dmacias

Right way to block ANIs using Amazon Connect

In this blog I’ll cover a potential financial issue you might face if you try to ANI block customers and they are calling you through a SIP trunk.

As I continue my journey of getting familiar with Amazon Connect I ran into an interesting and a bit worrisome issue. The use case I was working on was to create a table which blocks or allows specific ANIs to call in. Ultimately, when a blocked caller came in I wanted to just hang up on the call. My original flow looked like this:

image

Pretty straight forward, invoke Lambda, check attribute and if blocked = true, disconnect the call. When calling from my cellphone this worked great. However, when calling from my home phone (using a Flowroute SIP trunk) I got a nice surprise in the logs:

image

What you’re seeing is a partial log of my home phone constantly retrying to connect to Amazon Connect and generating a new call each time. Since there was no prompt play and no ring back heard I assume the network believes there as a connection issue and continues to try and connect. Which means that you could easily incur a huge expense both on your phone provider and on your Amazon AWS bill.

The way to fix this was to play a 1 second of silence prompt before disconnecting the call.

image

~david

by dmacias

X-Lite change the caller ID/Display Number

I had not used X-Lite for over a year and decided to load it up and realized that there’s an upgrade and older version of the software are no longer valid. So I upgraded and noticed that my Flowroute settings didn’t migrate correctly. I went to Flowroute got my credentials and moved them over, but noticed that my caller ID was not the caller ID I wanted. After playing around with it a bit I realized that I had to set my User ID to the caller ID I wanted displayed and moved my username/auth to “"Authorization name”. Now it’s working like it used to.

xlitesettings

~david