V18 Alpha 5: New Native Desktop App

Status
Not open for further replies.
I have setup a test video meeting in V18 and found that on the new windows app it has only giving the meeting link as the IP address of the phone system instead of the fqdn but on the Web client it has correctly listed the FQDN.
(the outlook .ics calendar entry has listed both)

Is there a setting on my system that I need to update or is this something that is being fixed in the next release?
The system is installed on premise.

Thanks.
Ohh, interesting! Sounds like a small bug lol which would be normal as it's still Alpha!
 
I have setup a test video meeting in V18 and found that on the new windows app it has only giving the meeting link as the IP address of the phone system instead of the fqdn but on the Web client it has correctly listed the FQDN.
(the outlook .ics calendar entry has listed both)

Is there a setting on my system that I need to update or is this something that is being fixed in the next release?
The system is installed on premise.

Thanks.
We suggest to use split DNS configuration.
 
We suggest to use split DNS configuration.
My DNS settings were not really what I was pointing out (I can access the system on the local network from both the fqdn and the IP address). It's more that the new windows client is only giving me a link for the conference of the IP address and not the fqdn address when I go to access the conference from the link given in the new client. Old web client gives the correct fqdn link for the same booked meeting.
 
My DNS settings were not really what I was pointing out (I can access the system in the local network from both the fqdn and the IP address). It's more that the new windows client is only giving me a link for the conference of the IP address and not the fqdn address when I go to access the conference from the link given in the new client. Old web client gives the correct fqdn link for the same booked meeting.
Desktop App is using both IP and FQDN, if the system is configured to use both of them. During app's provisioning, the link with fasted response will be chosen.
 
It works for us. Have you cleared your cache? The webclient changed a lot.
Yes i did clear it right before i sent that example. Any specific incoming settings i need to look out for in 3cx and/or telnyx?
 
Yes i did clear it right before i sent that example. Any specific incoming settings i need to look out for in 3cx and/or telnyx?
The webhook URL is generally the only thing.

I would check in Telnyx, under the Routing tab of the DID, in the Messaging section, it will say if the DID is MMS capable. Please verify and check the A2P or P2P type as well.

Last thing, maybe, just verify your messaging profile and make sure it is configured correctly (no short codes or stuff like that.)
 
Yes we will look at tapi support but really you should contact these app vendors if they plan on updating their app to support something not built in the 90s. It's so simple to do with the tel protocol.
For us TAPI is used in many of our customers' medical locations. TAPI is indeed old, but you can't force these vendors to upgrade, often it's also connected to medical software no longer maintained but connected to very expensive medical devices, so we're stuck with it. So we hope that TAPI will be supported in the new client.
 
Desktop App is using both IP and FQDN, if the system is configured to use both of them. During app's provisioning, the link with fasted response will be chosen.
Interesting. So is there going to be a way to make it display the fqdn in the final release as otherwise this is going to confuse a lot of customers. With the IP address being used then sites will get the security warning come up when they click on the link to go to the conference. This confuses a lot of customers when they get the warning so the fqdn link option needs to be given as well please.
 
Interesting. So is there going to be a way to make it display the fqdn in the final release as otherwise this is going to confuse a lot of customers. With the IP address being used then sites will get the security warning come up when they click on the link to go to the conference. This confuses a lot of customers when they get the warning so the fqdn link option needs to be given as well please.
If you want to ensure that the FQDN is always shown, regardless where the user is located (inside the PBX LAN or outside of it), then the answer has been given already:
We suggest to use split DNS configuration.

Most Firewalls won't allow hairpin traffic on the Public IP, so imagine if there were 2 links there, 1 with the FQDN and one with the IP, where the FQDN won't work and the other with the IP throws a warning. Not good.

So, either LAN IP for internal/local users with the warning (although I think most browser give you the ability to add exclusions/exceptions) or, the proper way of handing this: Split DNS
 
The webhook URL is generally the only thing.

I would check in Telnyx, under the Routing tab of the DID, in the Messaging section, it will say if the DID is MMS capable. Please verify and check the A2P or P2P type as well.

Last thing, maybe, just verify your messaging profile and make sure it is configured correctly (no short codes or stuff like that.)
Thank you for the response. I checked all of those and they check out fine. I reached out to telnyx support and they stated they can see the message and it is sending to 3cx fine. I will have to reach out to 3cx support, but before i do i want to make sure nobody else is having similar issues
 
Thank you for the response. I checked all of those and they check out fine. I reached out to telnyx support and they stated they can see the message and it is sending to 3cx fine. I will have to reach out to 3cx support, but before i do i want to make sure nobody else is having similar issues
Before anything, a quick question, does incoming SMS work OK? Just want to check if the only issue is with incoming MMS messages.
 
Before anything, a quick question, does incoming SMS work OK? Just want to check if the only issue is with incoming MMS messages.
Yes SMS works fine.
 
1625016959792.png

Where did this button/option go in v18? Is it coming back?
 
@Phone systems NZ - It would seem your on premise install does not have a DNS server you can configure. In this case we have to add two FQDNs. However if you have a DNS server then you can easily create a split DNS server configuration, see how here.

@GaSo Yes understood but the old windows client supports TAPI and will be available for quite some time as I mentioned in my reply.....

@cobaltit - will check, should definitely be there!

@Colorian Jabra need to update their drivers/api and they are working on it. Ask them when its ready. As a sidenote our new API will support Yealink and Grandstream headsets which are going to be a lot cheaper and the yealink ones look very good (i have not see the grandstream ones, cant say as yet) In general if you have issues with a headset please contact the headset vendor. Its their headset.
 
@Phone systems NZ - It would seem your on premise install does not have a DNS server you can configure. In this case we have to add two FQDNs. However if you have a DNS server then you can easily create a split DNS server configuration, see how here.
DNS server is configured. a nslookup pbx.example.com returns the IP address of the 3cx server ip address.

If it's working correctly on other systems then that's good as I was just mentioning it incase it was a bug that was missed in the alpha realease of the new windows client. As mentioned the web client for the same booked meeting gives a link using the fqdn.
 
  • Like
Reactions: N_G
  • Like
Reactions: Phone systems NZ
  • Like
Reactions: Evolute IT
Thank you for the response. I checked all of those and they check out fine. I reached out to telnyx support and they stated they can see the message and it is sending to 3cx fine. I will have to reach out to 3cx support, but before i do i want to make sure nobody else is having similar issues
After talking to Nick, we found the solution.

I updated the webhook in telnyx with the one that is in 3cx v18 (i previously had a v16 webhook). There is a small portion that was updated after updating to v18 that i didnt notice before ( the old one has "v1" in it while the new one has "v3" in it).After doing so, i can now receive MMS fine!

Thanks Fred and @

NickD_3CX

 
Does the 3CXDesktopApp.exe have command arguments? For example to initate a outgoing call to a specific number?
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,982
Messages
590,116
Members
164,908
Latest member
FarizQasimov