Vodia PBX

Call queue agents can be agents in a call queue... I know its sounds trivial, but there is indeed not much more to it.

We are making good progress on version 69 to fully support video on the apps, including stuff like changing horizontal and vertical orientation. While Windows, MacOS, browser and Android should be fine now, iOS is still on the todo list but we are getting closer.

For manual registration, there is the SIP password. It works with the extension number. You also need to make sure that you have the right tenant name in the Request URI (unless you use the name "localhost" for the tenant), e.g. REGISTER sip:30@tenant.com SIP/2.0 where 30 would be the extension name and tenant.com the name of the tenant. The authentication name then is the same 30, and you may choose a different outbound proxy e.g. the IP address of the PBX as long as the phone find the PBX.

There is no setting for this. You could change the HTML template and just take the icon out. The point about the information is to see who accessed the recording. It is sensitive information who listened to recordings. Why would you want to hide that information?

I think the problem is limited to app registrations for mobile apps. They are kind of random, for example after receiving a call the connection is still active for a few seconds and it makes no sense to count them as registration. However registrations for PC based apps IMHO do count — it should not matter if someone works from home with Internet perfectly okay when the office has an Internet outage. Anyhow we'll adjust that mobile app dangling registration in the next release (69.0.4).

SSH is not the problem for sure. It all comes down to the REST API. There are tickets that are two years old, so I take it we are talking about an older version of the PBX? The conclusion in the ticket was that the PBX did not have file system access during the start up of the PBX and was granted later, when it already created a new default configuration with the default password. If you are still running the version, either make sure that the PBX process has file system access from the beginning or upgrade to a later version, where the PBX process verifies that is has file system access before creating a new configuration.

Pending really just means that there are other requests that are not finished yet. I would turn on the logging for the web client to see any clue, like the wrong password or a firewall issue. There is no limit on how many requests are pending (they take only small amount of memory), but obviously this is something that eventually need to resolve. You can also always login to the Yealink management console and see if anything has reached the server.

It is less about the agents but more about the queues. The queues are about the caller experience and the reporting. It is not a dramatic price difference, and it helps keeping the other prices stable while many other cloud services are currently significantly increasing prices.

The login problems that we saw in the first 69 version should be all resolved now. If you did customize the welcome.htm page, you need to revert this page. There is a page called raw login.htm (less stylish) the you can use to login, and then do the customization from the web interface.

Are you on 68.0.3 or maybe 69.0.3? Maybe better to open a new topic... Can you navigate with the browser to the PBX over HTTPS and see the "green" safety sign?

This is obviously something that needs to be addressed. I would check if the pbx.xml file time stamp gets updated when you save the super admin password. If not, maybe there is a problem with the permission writing the file. Or sometimes there is a competing second PBX running on the same port and it gets random which one get the HTTP/HTTPS port.

68.0.28 is a good version, and there is no rush moving to 69 unless you need to have one of the new features. We are making every few days new builds for 69, and we have internally started to use 69 on some servers for production.

The only version which is still there is pbxctrl-debian64-63.0.7. There is really no other version for Debian. The 63.0.5 binary is available for Win32, IOP (Raspberry Pi), and MacOS (Darwin) if that is any help.

In such cases, try to turn the log levels up, there should be some hint in those messages.

Well at this point this is more like a roadmap thing, it will happen step by step.

We are changing the way to manage MAC addresses because of the IPEI addition. Plus it always made sense to manage devices independently from extensions. If there are a lot of extensions, it turns out its with the current 69.0.3 a little bit clumsy to access a single MAC quickly, we'll have to come up with something better.

Agreed. SMS has grown over the years inside the PBX, some things are hard to understand today. We need to eventually restructure the SMS similar to the trunk. This might be something on the list for version 70. When an inbound SMS cannot be delivered to anyone, this is a little bit like a missed call. Agents need to be registered with an app to receive the message. Someone should be aware about it — in the case of a queue the manager is the one. If there is no manager, well then the only thing the PBX does it to generate a log entry about that.

Hmm it looks okay to me... Maybe a problem with some strange/invisible characters?

Hmm it's still not 100 % clear. There are a lot of displays involved! First of all, presenting caller-ID on a SIP trunk is a tricky and endless topic because every trunk provider has their own way (e.g. spoofing caller-ID). You might be only able to present numbers that are owned by you on the PSTN. Presenting caller-ID on the VoIP device is easier. However, for example if you dial *00xxx, it is a feature that you will not see the actual cell phone number. Also the question is what version you are using.

Sounds to me like the ANI is used for authentication? How can a ANI be alphanumerical. I tried to put that name here, it worked... Which version? Which page? Which field?

Did you anything in "Address for pulling MMS content" (in /reg_messages.htm)? There you should put https://phonesystem.mydomain.com.

Hmm did you manually register the W70B or did you use the provisioning from the PBX?!

We have release version 1.22. It its a little bit clumsy but in the settings you can now see and change the service flags.

Please update one more time to 68.0.28 there was a glitch checking the default SMS value.

Did you enter a system name (System name in /reg_settings.htm)? Then this text should be automatically be prepended to the email subject. We all have that problem that there are so many addressed being blocked .