Vodia PBX

You can use the star code *59 for that.

Well, when you are using the apps there are a lot of possibilities, including showing the caller-ID, the length of the message and even the transcription. I assume you are talking about a VoIP phone? Many phones are able to update the display during the call, however the question is if users could get confused when they see that number and the change backfires?

Regarding the ringback, newer versions of the PBX support P-Early-Media, which might help with the ringback announcements. This is an option for the trunk setting "Local ringback generation for outbound calls".

Oh sorry I now see what you mean... We "hijacked" the username or account for the URL and the Application secret for the password.

You can select as provider "HTTP GET" which should be what you are looking for. The following variables are available (URL-encoded) in the URL: {password} The password for the account (which was entered in the setup) {body} The text content {from} The senders address {to} The receivers address {from-e164} The senders address in E164-form {to-e164} The receivers address in E164-form As an example, you could use the URL http://12.23.34.56:80/v1/sms/send/?phone={to-e164}&message={body}.

Yes there is. You can use the character F to detect FAX and then redirect to a destination (see https://doc.vodia.com/docs/autoattendants).

The display of the app heavily depends on the ability to fetch the information from the PBX. If that does not happen the app looks like it is stuck. The app stores pretty much only the information to log in. Might be an idea to keep more in the app cache, so that in case of bad connectivity the user does not get confused. In order to troubleshoot this, I would still try to get a trace on SIP or HTTP level to see what is going on.

Was any IP address blocked? Maybe the thresholds are too low if that is the case. Otherwise if you know the IP address of a user turn the SIP logging on for that address and check if you can see the packets coming in and going out.

We will let everyone know when it is released.

Ok on second look it seems that the problem is that telnyx has changed their TLS setup and now don't accept AES-CBC any more (instead must be AES-GCM). This breaks the interoperability with the PBX.

Well its a kind of unusual situation. The call from the cell phone is both a call from a trunk and also a call from an extension. If you call into the queue, that call is seen as a "client" call. If the only agent of the queue is that agent, well then the ACD will not be able to call the agent because that agent is busy on the phone all the time. However if there are other agents logged into the queue, those agents should get the call.

That would be a longer story. Essentially there would be two ways to do this—change the key_menu link and point it to your own server or modify the backend app in the PBX. Because you already have the content, you could just drop it into the tftp directory of the pbx (might have to create it first in the working directory of the PBX) and then chage the link to http://{get host}:{http-port}/tftp/your-file.xm to load it.

Not yet.

If we are talking about the menu key the template set that to use the PBX to render the menu: <dkey_menu perm="RW">url http://{get host}:{http-port}/app/snom/menu</dkey_menu> This menu is rendered on the fly by the PBX.

Is it url: or url=?

The browser does connect through TLS. Do you have that certificate in the PBX CA list?

The TSP is based on 20-year old technology. It's still available for download but we want to keep expectations about this low. As alternative you can use the Windows soft phone and register is for the callto and tel-schemes and make outbound calls that way. We are also working on a Windows Tasktray app that will handle incoming calls and also serve for initiating outbound calls.

Well this all should be working better in the 68 release.

Well right now the light will blink only if the call is ringing an agent. In the Vodia soft phone you (AFAIK) will be able to pick the call out of the queue which is a very easy way to solve the problem. But from the phone the *86 or *87 might be a workaround to get someone out of the ACD, specially when all agents are logged out.

Just tried that here on a snom 765 where it worked as expected. The "Enable call pickup from extension BLF" is not important because it is about a extension BLF not the ACD BLF. You can pick up the call only when it is blinking, which means that the call is actually ringing an agent. Its debatable in certain situations, e.g. when there is no agent logged in and there is no other ringing call. The workaround for now is to use a star code obviously.

Did not work... also tried a few other keys but still no luck. They must have changed their API seems Vodia is not the only one doing such things. [9] 20210802173943: https:metric-api.newrelic.com: Send request (698 bytes) POST /metric/v1 HTTP/1.1 Host: metric-api.newrelic.com Api-Key: XXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXX Content-Type: application/json Accept: application/json Content-Length: 516 {"agent":{"host":"TestServer","pid":"pbxctrl","version":"67.1"},"components":[{"name":"Debug System","guid":"com.vodia.pbx","duration":360,"metrics":{"Component/Traffic/SIP[packets/sec]":0,"Component/Traffic/HTTP[packets/sec]":24,"Component/Load/Media[usage]":[0,120,0,0,0],"Component/PBX/CDR[units]":113,"Component/PBX/Emails[units]":0,"Component/PBX/Uptime[sec]":9,"Component/PBX/Minutes[units]":9,"Component/PBX/Registrations[units]":0,"Component/PBX/Subscriptions[units]":0,"Component/PBX/Calls[units]":0}}]} [9] 20210802173943: Initialize TLS connection [9] 20210802173943: Received 298 bytes HTTP/1.1 403 Forbidden Date: Mon, 02 Aug 2021 21:39:43 GMT Content-Type: text/plain;charset=UTF-8 Content-Length: 2 Connection: keep-alive Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct" Server: cloudflare CF-RAY: 678a75e59839e708-EWR

Let me try to clarify the problem: When calling from the cell phone, this call is the "caller" for the ACD (even though its an account in the system) and there should be an agent (e.g. in a VoIP phone) to pick up the call?

Yes multiple languages are supported, including German, French, Russian, Spanish, Greek and some English accents like UK and AU. The language is the language of the users mailbox. The data is stored along with the meta information about the voicemail in the messages folder, if you want to "dig" it out from there you could rewrite a script from https://doc.vodia.com/docs/shellscripts but it would be better to use the REST API for this purpose.

Its included in the daily 67.1 (test) builds. This should also work in the browser view, if your device supports multiple devices.

If you are changing accounts or the PBX configuration while doing a large backup this might lead to inconsistent data (so—don't do that). However if you are doing a backup without changing the configuration this is by far not as critical. You might miss a voicemail in the backup because the voicemail was written after the backup was started, but you would also miss it if you start the backup afterwards. Stopping the service for backup would be counterproductive. Scheduling backups during less busy times is a very good idea.