Vodia PBX
-
Posts
11,069 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Vodia PBX
-
-
18 hours ago, mskenderian said:
Yea. I have Zabbix to monitors Vodia PBX and the server. I check for SSL fingerprint change when for expire date. I everytime I update the PBX. That’s exactly what happens.
I looked up Zabbix—seems like it would be worth showing how this works with the PBX! For example, fetching
https://pbx/rest/system/config?name=licenseto make sure the license is not expiring. I know of people using Paessler and site24x7, and adding Zabbix would be great.The other point why the certificate is being renewed every time the PBX starts up might have been a glitch with the renewal process for the
sys_adraddress. We'll look into this in the next build. -
10 hours ago, RichardDCG said:
The wallboard is removed from the Windows app menu (never worked anyway) but is still there in the web browser login?
We took it out from the Windows app for now. We'll have some work to do for the Windows app anyway, and then we can see if we can find a full-screen mode for the wallboard for the app that might also solve the issues e.g. when rebooting the PC (we all know the blue screen at the airport and we don't want that
).
-
The way we envisioned the usage is that the user logs in using credentials, passkey or whatever and then navigate to the wallboard, disables the screen saver on the OS, puts it on full-screen. The wallboard has a special way of keeping the session token so that if the PBX would have to restart or the connection gets lost, it would stay on the wallboard. This should work for a long time. This would assume that the underlying PC never shuts down.
Passwords in URL are a bad idea, see e.g. https://www.politico.eu/article/dutch-reporter-hacked-eu-council-interview/ especially when they are visible to a lot of people!
The question is what happens if you reboot the PC underneath, e.g. because it lost power or a software update triggered a restart. ATM it would mean that the user would have to log in again.
-
5 hours ago, mskenderian said:
V69.0.5 every time I update to new build. We get a new cert. Is this the expected behavior?
cert = certificate? Where? A new LE certificate?
-
On 6/23/2023 at 8:58 PM, Scott1234 said:
Yeah but I thought the idea here is to not have to edit the base file, which I am doing and I have removed {parameter yealink-general} from where it sits normally and put it below {post-process-yealink} due to what I have mentioned.
Well, the whole point is to post-process what has been generated. Yes you can think about post-post-processed content
, but IMHO the post-processing does everything you need and there should be no reason to edit the template if you just want to add or override a setting.
-
If you can, include the ^ in the pattern, otherwise you'll get random matches for example when the number 2121205123 would match 1205.
The other question is what pattern is send into the pattern matcher. E.g. does the provider send it in the +-format? It would be great, because then you don't have to worry about the beginning of the number.
ERE are powerful, but for humans hard to understand at times. You could play with the ChatGPT to come up with patterns...
-
16 hours ago, RichardDCG said:
UCM PBX's are ok, Vodia is not. Is there a change in how status is sent?
Do you have a NOTIFY of what the UCM is sending? Maybe we can spot the difference.
-
14 hours ago, RichardDCG said:
How should the phone be setup to be ready for hotdesking? I currently have a Yealink T41P set with ext. 107 registered. Ext. 107 is allocated a hotdesk ext. I cannot logout of the Yealink since I assume there is nothing for the phone to revert to? So will be forever 'registered' to 107.
Yes the phone needs to be registered to the PBX in order to have control over that phone. That is what the hot desking account is for. It might be better to use a name like "hotdesk-107" because nobody is supposed to call this extension or from that extension.
IMHO there must be something else confusing going on, maybe a redirect all or multiple device registrations.
In any way, hot desking makes only sense in specific setups. For a regular office where users have their own phone, there is no need for hot desking and hot desking accounts.
-
After logging into hot desking, please double check in the users account (not the VoIP phone on the hot desk) that there is the hot desking at ... set to the hot desk phone. Same after logging out, then it should be clear.
And in order to avoid confusion (maybe from previous tests) that the VoIP phone itself is not hot desking anywhere else.
-
Looking at https://firmware.grandstream.com/Release_Note_GRP261x_1.0.9.83.pdf I would not see changes between 1.0.7.33 and the next one 1.0.9.22
-
It's at http://portal.vodia.com/downloads/pbx/version-69.0.5.xml keep in mind it is not a release yet.
-
2 hours ago, mskenderian said:
can we get this cert added? or fix this somehow?
Well I assume that Poly(com)/HP interest in providing an updated firmware is limited. If I remember correctly you can import the certificate through the phone web interface? I also remember that over HTTP we would provision the root CA into the phone, but that does not seem to happen?
On a side note, you should also consider making TLS1.2 the minimum version, unless you are using really old equipment.
-
2 hours ago, Vernon said:
Would you happen to have a reference of the full expressions allowed in the matching? It would help to have something up to date to reference.
Extended regular expressions are used in many places, e.g. see https://en.wikibooks.org/wiki/Regular_Expressions/POSIX-Extended_Regular_Expressions for general information. Character classes are sot supported.
-
I think the way you use the square brackets does not work. E.g. instead of
!^([(205|251)]{3}[0-9]*)!100!f!try!^(205|251)[0-9]*!100!f! -
Anyhow, the PBX post-processes the Yealink provisioning files anyway. If there was an enterprise or site-ID, it will be dropped from the file.
-
9 hours ago, DMS said:
Once updated admins and users are unable to login unless using "/rawlogin.htm" and we are unsure how to resolve this. A red gear shows at the top right of the normal login screen after an attempt to log in.
That one seems to be a major pain point. We tried to provide some hints in the release notes, but the main problem seems to be that from older installations the system management DNS address contains leftover garbage which is now actually checked against the URL in the browser. It would be convenient to continue ignoring it, however it is a great way to fend off robots and it also helps generating the right SSL certificate, so we are a little stubborn about it and continue insisting that admins should log in with the right URL.
9 hours ago, DMS said:1) The easy switching between using the web app or desk phone is greatly missed. Maybe changing it to client/phone or app/phone would be better.
We assumed that users don't do this all the time and it now in the settings (preferences). We even had cases where users did not know what button they are pushing and complained that they cannot make calls any more.
9 hours ago, DMS said:2) A way to DND easily from the app or silence it would be great. I hate to use 3CX as an example, but a app/client user could silence the app while their desk phone still rings.
Ok you would have to reject the call first and then click on the account image (top right) and there turn DND on. Three clicks...
9 hours ago, DMS said:3) If user is not provisioned for fax or text messaging maybe remove all references to it in the interface to not confuse the user.
Internal messages are always possible. FAX depends on the SIP trunk provider but I dare to say that it works more or less with all of them today. But we might have to look into text drop downs when there is no SMS provider.
-
12 hours ago, Scott1234 said:
Yep, I program into general prams for that reason, but you guys need to move the general parameter include statement to the end of the Yealink provisioning template so that if we want to make a change to something that exists in the config below where it includes the parameters now it's not overwritten by the base again.
In Yealink provisioning world, the first occurrence of a setting wins. So it should be okay if parameters show up in the Yealink general and then again later in the provisioning file again.
-
On 6/20/2023 at 10:02 PM, RichardDCG said:
My expectation of a hotdesk phone is that it would only have the capacity to accept a *70 code until it is logged in. It should have no config at all until a user logs in. When they logout the phone is 'wiped' again, ready for the new user. But each user should be able to use the phone as a standard desk phone and call other extensions and external number.
100 %. There were some builds where that did not work as it should but that is as it should work.
We are contemplating changing the way it works to reassigning MAC addresses instead of hijacking the registration. This might also help addressing the problem that button profiles need to be linked to devices and not to extensions. However before starting a new adventure, we want to have a release where the hotdesk in is just working as it should.
-
The PBX already supports stereo recording, with each party staying in their own channel. MP4 is a video format, MP3 could make sense but OPUS would be a better choice today. However its a mess what plays on the web browser, and at this point we'd rather not touch it. That being said maybe it's time to ditch the GSM codec as recording format. And going forward we will have to feed the audio into speech recognition, which further limits our choice for audio formats (uncompressed audio always works).
The permissions are not only all or nothing—you can listen to your own calls but to all calls one with the permission.
I agree recording multiple tracks is a waste of recordings and confusing. A possible way out would be to keep track of the involved users in the recording in the metadata, and allow the playback only if there is either only that one extension involved or the extension has permission to listen to all recordings.
-
If you are using automatic provisioning, assign the MAC of the device to two extensions.
-
Thanks, great suggestions. We'll add an enterprise and site ID parameter to the next version and also provide the tone country for a better local experience so you don't have to do that.
We recommend to use the Yealink General parameter so that you don't have to customize (and freeze) the yealink_common template.
-
Cloud storage including EC2/S3 is powerful. We are just scratching the surface. For example, we could add additional tags that can be used in search—then there is no need to include those tags in the WAV itself.
The way it works right now that the recording is held in memory until it is uploaded. I doubt that we can hold recordings for the whole day, this would obviously exceed memory capacity. But an outage of EC2/S3 for the whole day would be quite an event, and there might be bigger problems that the PBX losing recordings.
I was not even aware about S3 being a standard
but if that's the case it should be relatively easy to send the recording a different direction.
-
13 hours ago, Brett Davey said:
One of the regular pieces of feedback we are receiving when people are first testing 69.0.4 is that it looks like a sheet of white paper as compared to 68.0.30.
Is there any ability to at least add a graphic into the centre of the screen to be visually more appealing. This will be the first thing that our customers would comment on after a change to 69.0.4 would be made?
This is a very good point. We do have the plan to fill up the Home Screen with gadgets over time, but that has not happened yet and it indeed looks empty. This would explain why people have the feeling it is not finished. We had the same problem with the chat screen, where we put a background wallpaper like most chat tools do today anyway. As a quick-fix, we'll use that same background also on the Home Screen. Putting something like the welcome screen image there IMHO would be too heavy. Putting something there like the call history is helping only when the user has started using the user front end, which might be too late for the first impression.
13 hours ago, Brett Davey said:In addition can you please advise when the end user documentation will be updated for the 69.0.4 softphone?
We have started working on that.
-
2 hours ago, RichardDCG said:
the main issue with the hotdesk ext. license is that I can ONLY dial an emergency number, no other numbers. I cant dial other extensions, nor can I dial any external numbers. In Australia, I can dial 000 ... thats it. At the moment I can get great audio quality but only when I am talking to emergency services!
IMHO that's okay, maybe even a feature. Someone grabbing a desk in the morning would otherwise easily forget to login (or don't care), and then assigning the records to that user will be impossible. And people would call that person back on the hot desk extension, just to find out that the next day that person has changed the number—again!
Codec negotiation
in Call Treatment
Posted
The main problem is that many implementations don't properly support the offer/answer model and are not able to handle multiple codecs in a single stream. For example when a device "advertises" that is supports G711A, G711U and G729A that means that it is okay to send either of those codecs, and switch between them any time without re-negotiation. And its totally okay to have different send and receive codecs. Unfortunately the reality is far from that, especially on trunk side.
We have added several settings to deal with the situation, e.g. answer only with one codec ("present to be stupid") to an offer from a SIP trunk and have "symmetrical" codecs, so that sending and receiving are using the same codec. IMHO when it comes to problems on the trunk side, it is usually the best to just fix the trunk to G711U or G711A depending on the country and not leave any other choice to the trunk. Those "dumb" trunks transcode to G711 sooner or later anyway, so that the quality is actually the best if that codec is used in the first place and leave transcoding to the PBX. If you are using a trunk from the drop down, this might have been already setup and you don't have to tinker with the many settings.
On the VoIP phone side it's usually not as bad. For the VoIP phones in a nutshell the phones should propose whatever they have, but the PBX makes the decision what codec to use. You can still fix the codec on an extension if you are using a phone that does not support RFC-compliant SDP codec negotiation.