Vodia PBX

The ringer topic was a difficult one, it took many iterations to sort of get this woking on all different platforms (hopefully we should have most of the problems solved in 68.0.2). One important point that makes life easier is to tell the browser to allow audio playback for the user portal, so that all those things we do to allow audio at least after one user interaction are not needed. And the other problem is to clear the cache, which is relatively easy with the browser however the apps don't have such a refresh button.

There was a fix for that in 68.0.2 when the first page was not complete and the second fax happened to be on the same call slot.

There are several things here that are mixed up. The fundamental issue is that employees don't like calls outside of "working hours" (whatever that exactly is) or on unrelated topics (e.g. support calls). As for the working hours, there are several things possible today: Service flag: This works well if the employee has more or less fixed hours. The service flag defines when the app and the cell phone gets called (desktop phones get called anyway as they are supposed to be in the office). For example, you could set up 8 AM to 6 PM or maybe 9 AM to 5 PM depending on how tolerant you want to be and you can define what days are holidays. This can be defined per tenant or per extension. DND: When it is difficult to define fixed times, an employee can just use manual do-not-disturb. This can be done (as of 68) for a few minutes, until the end of the day or until the end of time. This method can be combined with the service flag. It's easy to do from the app but its also easy to forget thus the time features. App flags: A little bit more inside the app, the app offers control over which device class gets called. We have currently app (which might be too broad considering that iOS app and PC app are in the same class), VoIP phones and mobile phones (GSM). This is a manual process. iOS 15: Lets not forget that Apple has introduced "focus" where you can define what app can interrupt a user. This is a fantastic feature, because it can use e.g. the geolocation instead of a fixed time schedule. And it is also great because if can mute unwanted apps while working, further reducing the number of interruptions and improving the work life balance. Lets see what Android comes up with, there is already a work profile and a private profile it might be not too hard to enable or disable them similar to what Apple has done. Completely unregistering the phone at the end of the day sounds to me like a misunderstanding of what the use case is. As far as the topics are related, this is largely related to logging in and logging out of a queue. That means largely logging in and logging out of a queue. So far we have seen only few agents using the mobile apps (might be changing), but the PC apps have the login and logout flag in the queue view.

You have to keep in mind that records that have expired are not shown in the list any more. Maybe the _sip._udp record had already expired? That would be totally fine. You can turn the logging for DNS on, maybe that contains another clue. For example, maybe you are talking to the wrong DNS server.

Yes the term "app" is misunderstood by many people. We'll need to figure out how to separate "mobile" from "desktop" or just have that flag really just for that one device.

In the iOS setting, select "Focus", then "Work" (or whatever you want to use). Then there under Apps make sure that the "Phone System" is in the "Allowed Apps".

Then there seems to be a problem with talking to the PBX when deregistering. You can manually delete the app wakeup registration from the tenant portal in the extension, registration tab.

Seems to be working fine in 68. I wonder why your address is _sip._UDP.gw.sip.us and not _sip._udp.gw.sip.us?

Yea there was a glitch that that input field was not treated as user input field... Next version will convert the number properly. In the meantime, you can enter the number as +18189370311.

Hmm strange if the FAX actually went through. Maybe open a ticket and attach the PDF, might contain a clue.

IMHO the only way to do this is to use a SIP trunk between the previous system and the Vodia PBX. That means that features like BLF and call pickup will not be possible between the domains, but at least calls within the company would still be possible.

I think this should be possible. AFAIK you must be on an IP address that belongs to Deutsche Telekom in order to get this working. There is a drop down for Deutsche Telekom in the trunks section that you can use.

At this point I am waiting for Safari 15.0.1

Well at this point "app" is iOS app, Android app, Windows app, browser and one day we might even have a MacOS app. I do believe that the controls on iOS 15 is the better answer to the problem anyway.

Right now you can export only the whole tenant, not a single account.

Maybe you can share the PDF that causes this with support so that we can try to reproduce this.

The version numbering not ideal right now, frankly if we would make a number for every 68.0.1 change we would be at 68.0.100 already. Anyhow we'll make a 68.0.2 soon as the "dust has settled" version for 68.0. As for the PC app, the new app loads most of the code from the PBX anyway, so that the version is almost irrelevant and software updates happen only on the PBX side. Again, the upgrade has a few bumps on that road but we should sail in smooth water when it is all done.

Oh there might be a misunderstanding here... In the registration tab in the tenant web interface you don't only see the registrations that currently have a TCP connection. The list also shows the wakeup token registrations that are sent to Apple to wake the app up. They don't have an expiry value and they show as "APP". You can even power the phone off and this one will still show, it does not consume any battery on the phone. Again, if you want to want to stop the PBX from calling the app, you can either switch off that flat in my post above, you can completely unregister from that same page. And in iOS 15, you can also now set your profile e.g. "private" where the Vodia app gets blocked, e.g. when you are home. Many SIP soft phones have the problem that there is no such thing as wakeup in "classical" SIP. This is clearly a major disadvantage/showstopper. The Vodia phone does not have that limitation. The PBX uses the push service from Apple to wake the app up. The PBX also does that for Android, though this is a different mechanism.

Thats a longer topic... You can generally control what should be in the SIP headers (see https://doc.vodia.com/docs/trunk-custom-headers). You might want to use the {ani-cnam} variable to replace the CNAM of the account that sponsored the ANI (see https://doc.vodia.com/docs/trunk-ani).

For the app, it is absolutely a feature that calls still come in after you have closed the app. Every VoIP app does that. If you want to log out, you can click on the account name at the top of the app and select "unregister account". That deletes the registration on the PBX. If you just don't want to receive calls on the app, on the same screen you can also disable "call the app".

Please check if the pbxctrl.dat has made it. If not, you can manually download it from the link in the http://portal.vodia.com/downloads/pbx/version-68.0.xml XML file. You can actually download all files (for the right OS) manually if needed. Also make sure the the files have the right permissions, e.g. in Linux the execute permission.

You can also take a look at https://doc.vodia.com/docs/click2dial (the pbxcall element) if you have control over the web server.

Now that 68 is out of the door its time to look into the topic. The new GDMS is much better structured. Our worry is that we need a co-existance—rumor has it that older devices are not going to work with the new platform, is that true?

Monday morning would be 0:00/mon.

The browser is easier to control the app. At least we are able to clear the cache and make sure that everything is up to date. We are changing that in the Windows app as well, but its not so straightforward. The email that the PBX sends out should be the confirmation on what as been sent. Are you saying what the FAX receiver has is different from what's in the confirmation email?