Support

If someone is calling the DID number associated to this extension, then you can receive it as well.

Hi, We suppose you must have already seen some advances in this area via email from our Partner. They would be the best point of contact for your troubleshooting as one of our Developers is working with them.

Are you referring to the App logging in via Google sign in? If yes, what version of the PBX and app are you? And what OS app is it?

You cannot set the ports on the App, it needs to be set on the PBX itself under : /reg_ports.htm and /reg_sipsettings.htm page. Outside the network you can use LTE network which should work fine.

Our PBXs are not configured to be installed on a third party server and work in conjunction with it. For the same exact idea above, we have a product which is combination of PBX + Router = Vodia IO https://vodia.com/products/vodia-io-router-with-pbx/ which you maybe interested in.

If, 1. You have the ACME certificate setting turned on. 2. You are not using any wildcard or external certificates of your own. 3. If your domains have a FQDN name and is accessible on port 80 Then it should always use the ACME certs and auto-renew as long as above conditions are always satisfied.

That usually means that your media is not connected to the web portal for the audio to be routed. Do you have any plugins which are hindering this from happening? Can you give us the login to one of your user portal and we can try to make a call to one of the US numbers?

Your snapshot has a lot of whitespace and not much information on it. Are you using https or http login while using the webRTC?

Alright, what help would you need from us at this point? (not sure if we completely know what you want to achieve this point onwards)

That's good! We asked you to try that yesterday itself. Not sure what happened there. What exactly do you mean? Send a screenshot or some logs maybe to quickly understand this?

Try +1* instead of just +1 and +[2-9]* and 011*

Have you gone through the doc we gave earlier? It has example about how you can setup the DTMF list in it. Please check that and let us know.

Yes, that's what it's supposed to do. Again, we're talking about inbound calls here right? I wasn't referring to dial plans at all. These are just trunk setting which "should" take effect on inbound calls.

Can you paste a snap of Dial plan that you have now? we're sure that the second one that we provided should've worked, as it's also included on our Dial plan doc page.

Yes, please check all the possible capabilities we have with regards to an IVR node here: https://doc.vodia.com/ivrnodes

Is the field "Rewrite global numbers" being set to "Don't rewrite" not helping, inside the trunk settings?

1. Pattern: +1* Replacement: 1* (not sure if this'll work) 2. Pattern: +44* Replacement: 01144*

If you downgrade one of your test server's to version 57.3.13 and "inspect element" for deleting that address book entry, I think that can give you a better picture of the API's as those were the times when we last used it. We won't be able to downgrade our test servers at this point as we're running several tests with it currently unfortunately.

Try "adrbook" instead of "trunks"

Are you referring to this ?

Hi, Which version of the PBX are you on? Have you checked out our new API page https://api.vodia.com/ ?

Pasted the wrong URL. Anyway, should be clearer now.

Also, please upgrade the PBX to 65.0 once again (if you've already updated more than 12 hours ago from Apr 27th, 9:30 AM EST) along with the app and try again.

Inbound caller ID settings headers: https://doc.vodia.com/trunk_custom_headers (you can navigate on the left hand side to look for more settings). And the admin level shows the +1 along with the numbers in the call logs if you want to take a look. Inside the domain, it's the default setting that reformats the number to look like 555-555-1212 by default.

Nothing for browsers as of now. Because we already have the app both for iOS and Mac out.