AlanS

Yes. I hate soap. I now have a fully working example with IVR nodes and a Node.js server now... A few notes... Returning XML does absolutely nothing, the docs have no example of returning JSON... but returning a single text string of the destination works. This could work, as long as you have an IVR Node for every positive and negative scenario.

Is that sns correct? xmlns:sns="http://soap.com/pbx" and xmlns:sns="http://www.vodia.com/soap/pbx" do not resolve

Oh, I am not advertising Sipharmony. I am advertising Stoplight. And we allow BYOC and BYOD.

https://sipharmony.stoplight.io Use stoplight. It's free and you can have internal api docs too. If you need a hand, just reach out. I know the vodia api and websocket more than anyone now.

let this flow chart explain visually. I am getting tired of hunting down service flags. Please add redirection TO service flags! I understand the need for reusability, but adding redirection direction would keep us from playing "find the redirection"!

Everything you need is in Network tab of console

Indeed they do. It would be much faster if redirection could be set ON the service flag. It is much much easier if we could set redirection in the service flag, for simple redirections only. In freebpx or netsapiens, this would be a call flow toggle.

@hamster lay down the law! haha. Get this added

Thread resurrection. If you have anyone on your team that can fullstack. Vodia is fully api driven. You can catch all api calls in the web console. If you need a solutions expert, I know a lot of good and honest developers in India that use my same stack. We recreated the webapp to our own liking and "customer facing simplicity". Customers can see when service flags are active in realtime now. app.sipharmony.com This login is the same credentials Vodia sends out in the email too. Makes everything easier and my life a lot easier too. Vodia is powerful and THE MOST CUSTOMIZABLE white label pbx you will ever find. We've tried them all.

Has anyone every thought of adding redirection TO service flags? I find that we have to make a double effort with multiple IVR's or dummy ring groups to get around this. In Freepbx, this would be considered a Call Flow Control Toggle. We can assign a DID to a service flag, but as you know, that's a dead end.

Is this still a thing?

If there is a way to bring back PIDF into the sip headers, that would be awesome. 90% of my customers simply do not care about apps. All they care for is a dial tone with an IVR lol. They all use physical phones.

VI does the same thing with locations. They have to be verified. If they are not, then PDIF is ignored. To confirm, PDIF in the invite is now scrapped? I need to know, so I can spend an afternoon updating all accounts with their e911 address in VI.

We ran a PCAP, and there was no location information sent during the invite.

Voip Innovations 100% supports PIDF-LO https://voipinnovations.atlassian.net/wiki/spaces/VIW/pages/1986330625/E911+Dynamic+Location+Routing

I only found out about this, because we got smacked with an unregistered 911 fee today. Even with this enabled and the location filled out.

I enabled this on the trunk and have locations set. I called 933 for testing and ran a pcap, but no PIDF headers were sent. Was this because they only send with 911?

What did you turn on to see that log entry? Google Speech to text isn't working at all for me.

Hello gents, I am following this guide for a customer of mine, but I halted cause I need more information from you guys. https://doc.vodia.com/docs/googlecontacts So I need to do the setps "Obtain Client ID and Client Secret" for every domain on the pbx that wants to integrate with Google? Or do I just do it once. Thanks!

So, two agents try to answer the same call. (Agent A and Agent B). Does this mean that one of the agents gets the call and the other gets the error? Or does the call drop and both agents get the error?

With the magic power of Hamlet, he was able to show me the errors of my ways. I 100% failed to understand how permissions work.

I've tried *981004 *98 1004 *98 *1004 *98*1004 Does let me record a greeting, but it's not applied to the IVR 1004. I don't know what it's applied to.

I am trying to demo calling in and setting the IVR message, but it just keeps saying "This feature is unavailable" At first, the user was not part of any user permission group. So I created that and added them to it. Still get "This feature is unavailable". Then I noticed the users account was set to "App Only". Fixed that, still getting "This feature is unavailable". Then, I noticed the user did not have a PIN, So I set that. Then I called into the IVR with *986012, Now it says "Please enter your code". I enter the PIN, and then I get hit with "This feature is unavailable". How in the world do we set the IVR message for Override default (*986012) Thanks.

We get them too. If you've done any mobile dev before, once you send the push update with the correct meta, it's no longer in the developers hands. It changes hands so much. ISP, Carrier, Android, Apple, Samsung.. it's endless. TLS and APP KEYS (for Apple) was supposed to solve this. And apple is very picky with meta. I just have all basically all this in a canned response for service tickets lol. Example, mine always rings, but I'll get some random alert of an SMS from a couple hours ago, 50 messages late ha.

I can confirm that we can text out using V2, but incoming texts do not work. Any new DID provisioned with QuestBlue are automatically set to V2.