AlanS

Can we confirm that Vodia works with QuestBlue V2 of SMS?

I just got my X5U (The solid red one) in. I am going to provision it today and see if I have the same problem too.

Check all routes. IVR, Ring group, Call Queue. Make sure you check the FROM header in those too. Also make sure you turned on CNAM in QuestBlue. Yes, it's an additional fee per month, per number.

Ah yes! Thanks!

ahhh. That's really good. The address book IS the whitelist. Lets get it added! lol.

I saw in ring groups and call queues there is an option to send suspected spam callers to an IVR or another extension. I am going to play around with that. But, this feature by default would be an awesome addition. Ticket worthy?

Got it! QuestBlue sends Caller-ID in From header. In the trunk, set Source for caller-ID information = From

Hello, Are they any special settings with QuestBlue? CNAM is still not coming through. The inbound caller id just show the number calling, not the name + number. thanks

Interesting. I like the idea. Only problem, is under Handling of suspected spam callers, there is no option for Auto Attendant. Work arounds?

Is there a way to forward calls that are not on the whitelist to an IVR? Also for blacklist too.

It was because I was in a call queue!

So, I put my cell as the redirect. Yealink shows "Always forward enabled" but the deskphone still rings. Do I need to include the 1 infront? Ok. The button works correctly. Vodia shows the number on Forward all calls to: my cell But the yealink still rings. The yealink even shows it on Always forward calls Is this because the extension is in a call queue?

I think I found it. I set it to "Redirect" and type in the cell?

In the past, we setup call forward on yealink BLF buttons with the feature code + cell phone and labeled it Forward To Cell. I can't find that anywhere in the button config. Can you please show me the way?

Thanks for the reply! I wanted to use all the features of a call queue for them. Like ringback is MOH instead of ringing. Thanks!

Yea, I was not clear was I haha. The expire time for the QR code.

Hello, Is there an option to ring all extension for call queue or even ring groups? I am not seeing it and I am sure I am missing it somewhere. Thanks!

I can confirm this is indeed not working correctly. This is what's happening. 1. Vodia -> add server -> {name, url} -> yealink rps -> returns 400 {server name already in use} //This is where you should have stopped executing your code. I can't find the POST BODY in the logs, so I don't know what you sent originally. 2. Voida -> add device -> {mac, serverName} -> yealink rps -> returns 400 {server name is undefined} //ServerName is undefined, because it was not created in step one. 3. Repeat 3 more times ha. The original error "server name already in use" is strange. I would have to see what name was being sent. This error happened to me too. But, I have a fresh RPS account with nothing in it. This isn't that big of a deal for me. I remember a couple of years ago, when yealink was changing and deprecating core urls and functions MONTHLY. At the company I did work for. I created my own autop service with the yealink rps. Boy was it a pain. Every month, was some crazy breaking change. I am just adding the servers manually in the RPS until this is fixed. No biggie. The Grandstream RPS is outdated too. It's not working for the new GDMS. But, again, I just do that part manually. I really don't mind. Advice to anyone landing here, just create the server and add the device in RPS Management, and then add the mac to the extension in Vodia and don't forget to open it for provision.

Where are you pulling that log from?

I got it. QR code expired. Where at in the system do I change that? I found it once, but can't seem to find it again. Thanks!

I am getting reports from users on iOS, that when they scan the QR code, it returns with "Scanning Failed" - The code was not found. Any ideas?

I noticed {Output} doesn't send anything to the server except '{output}' in string format lol. How were you able to send the captured digits?

Is this a planned feature for the future? If not, can it be? I have a client that doesn't really have an IVR. I created an auto attendant, that just sends all calls to the main call queue during normal business hours service flag. But I want a message played when they first enter the queue (text to speech).

So, I see I can set it at the trunk layer, which makes total sense. But I am not going to create a trunk for every resi. I am just going to tell him 10 digits are required.

I may programmatically create dial plans for every account during signup, just need the correct plan. Any thoughts?