Vodia PBX

Seems there is a update for that in the pipeline https://www.getdroidtips.com/moto-g8-power-lite-android-10-update-confirmed/ that might solve the problem?

The *77 has to be a new call, with the call that is being transferred being on hold. DTMF does not help. We have the ## key when the call is supposed to come from a cell phone. That might be a trick for getting this done. One way could be to set up a trunk that is associated with the phone and then use a caller-ID like "softphone123" which is set as the cell phone number of the account that you actually want to use. Then the caller would have the possibility to hold the call with ## and then hear the options like transfer call, bridge calls or conference calls. Maybe we'll just add a setting to the extension that makes the PBX listen for the ## in order to better handle such devices.

If the phone is on SIP/TCP or TLS this would be indeed very strange because then there should be no packet loss. I would check the logs of the phone for any hint about the incoming call and maybe there is some message that explains why it does not accept the call.

You need to make sure that you have the right permission, e.g. use sudo in Linux.

I tried this here—worked. Try to rename the certificates folder to certificates2, restart the PBX service and see if that cleared it up? That would have been a "hard" reset of the trusted Root CA.

I would try to reset the lost of root certificates on your PBX. Maybe you have an old list on your installation (they are not automatically updated with a PBX software. upgrade).

I think the best to open a ticket and attach the code that you are using there right now. We have done other projects and maybe we can fix the code there easily and get this working.

If you want to perform a third party login, there is a special API for that that will also set the necessary headers for the cross origin problem (CORS). This works different from the login for the browser. There is an article on https://doc.vodia.com/third_party on this topic. There is also an example at the bottom of https://doc.vodia.com/click2dial where you can see how the soft phone gets the credentials for a user.

The 5 bytes returned are probably "false". Which means that the request to establish a session failed... If you want to use curl there is an easier way to authenticate the request, just use the -u admin:password option for curl (e.g. curl -u username:password GET -D - http://192.168.1.194:8080/rest/system/log). Then there is no need to set up a session.

Well the login seems to work... I cannot see any REST API calls apart from those coming from the browser. Are you using curl?

Maybe you can post the log with log level 9 for the web server to get a clue what is going on.

Make sure that your default SPAM score for anonymous calls is lower than the rejection threshold. There were some version where those numbers were the same (50), and anonymous calls were rejected by default. These settings are on /reg_recording.htm at the bottom.

... and of course you could have been blacklisted though this should clear up after some time.

If you have turned on filtering for domain names, you must make sure that the hostname in the HTTP request matches either a domain name or the system management address in 66. Apart from that, I would not know what else could have changed.

That requires some more changes. If you like try the 66.0.1 build which should have that included now (assuming the GXV3350 also has 160 buttons). After the upgrade, better reset the file that you modified as it includes the fix already.

Ok that makes sense. We'll make that happen in the next build/release (66.0.1/66.0.2).

We did dix a bug where the PBX would ring an extension although there were no registrations. Maybe it is related to this problem. What is supposed to happen if you have anything registered to the FAX extension? Do you want to receive incoming FAX through the PBX and send out from an ATA?

Wenn der Ländercode der Domäne eingestellt ist, versucht die PBX die Nummern für den Benutzer "lesbar" (oder lesbarer) darzustellen. Die Nummern selbst enthalten aber keine Trennzeichen (z.B. "0041-12345" <sip:+4112345@domain>). Bei einigen Telefonen kann man einstellen ob die Nummer selbst oder der Name dargestellt werden soll. Das wäre eine Möglichkeit dies zu ändern. Die andere Möglichkeit wäre den Ländercode zu löschen. Dann ändert die PBX die Nummern nicht. Es fallen dann aber auch viele andere Funktionen weg, z.B. die Interpretation von Nummern vom SIP Trunk Anbieter.

I would assume the template grandstream-gxv3275.xml. If you modify the pnp_grandstream.xml like this it should pick it up: <file name="grandstream-gxv3275.xml" encoding="xml"> <pattern mac="3">cfg############.xml</pattern> <user-agent>Grandstream.*GXV3[23][578]</user-agent> <prefix>true</prefix> <vendor>Grandstream</vendor> </file>

Ok lets get a PCAP to get to the bottom of this. Maybe just attach it to a ticket.

You can double check with the browser if you see the "green light" (or lock) when you visit the PBX URL. If its green, its a sign that at least the browser understands the certificate. AFAIK the VVX 250 are different code than the original VVX devices, so it could be that their certificate management is different. IMHO the later models must include the X3 root CA that LE uses. If not, does importing it on the phone solve the problem?

Can this system contact the license server (https://license.vodia.com) properly? It looks to me that this is the problem.

We will check what is going on.

That sounds like the "fingerprint" of the PBX has changed. In that case you could manually reset the license through the portal.vodia.com.

I think you are missing the runtime DLL (see https://doc.vodia.com/install_win and https://doc.vodia.com/admin_swupdate). We were trying to get rid of this dependency, but it was a struggle. Maybe the 66 version does not need it any more, it would make the installation and upgrade process for everyone easier.