3CX Windows app call flow?

[PeterCheng]

Hello sir,

Currently there's one thing confusing me a lot.
For 3CX V16, if both end users are in the local LAN, no recording requirement, and no PBX Delivers Audio.when one user calls the other, my wish is that call signal will go to 3CX server first,
and when the other user picks up the call, the call flow will be end to end without passing through 3CX server.
(If server is at site A, and users are at site B, if user call other user and they are at the same site, the flow does not need to go from site B to site A and then back to site B)
(just keep the call traffic flow in local LAN)

But now we want to use V18 windows app, and it seems that the windows app supports only tunnel mode and all the traffic will go through 3CX?
Like user A <--> 3CX server <--> user B, not user A <--> user B.
In that case, it won't fulfill my requirement.

Is there any workaround or setting which can prevent from such situation?
Thanks.

Peter

 

[VasilisV_3CX]

Hi @PeterCheng,

The new Desktop App works similarly to the Web Client, thus wanting to use it in the way you described can't happen. You can use IP phones for your required communications mentioned above.

 

[PeterCheng]

Hello VasilisV,
Thanks for your reply.
May I know why 3CX decides to remove such function?
If users in local LAN dials internal user who is also in local LAN, using tunnel mode must pass through 3CX server.
From my point of view, this behavior will increase 3CX server's loading and waste the bandwidth usage between user and PBX server.
So I'd like to know its pros and cons to pass traffic through 3CX server , thanks.

Peter

 

[VasilisV_3CX]

Hi @PeterCheng,

May I know why 3CX decides to remove such function?

The Electron software framework which the new Desktop App is built on allows ease of portability, such that porting to MacOS is possible. However we've not 'removed' such a function. The Electron App is not the Windows App and is not deprecated, you can still use it.

However to clarify, if you wish to keep communications peer-to-peer via the Windows Client (not the new Desktop App [Electron App]), you will need to have PBX delivers audio off, recordings off AND both extensions will need to be local to the PBX. In your example you mentioned 2 extensions at site A, and the PBX at site B, this will not create peer-to-peer communications, be careful - both the PBX AND extensions need to be local.

 

[PeterCheng]

Hi @PeterCheng,



The Electron software framework which the new Desktop App is built on allows ease of portability, such that porting to MacOS is possible. However we've not 'removed' such a function. The Electron App is not the Windows App and is not deprecated, you can still use it.

However to clarify, if you wish to keep communications peer-to-peer via the Windows Client (not the new Desktop App [Electron App]), you will need to have PBX delivers audio off, recordings off AND both extensions will need to be local to the PBX. In your example you mentioned 2 extensions at site A, and the PBX at site B, this will not create peer-to-peer communications, be careful - both the PBX AND extensions need to be local.

Hello Vasilis,

Thanks for you reply.
There are another 2 issues for me:
1. I checked the original windows app and it still remains in V16 even I've upgraded server to V18?
I'd like to know if you have to roadmap to keep the original winodws app,upgrade it, or EOL one day?
2. What's the definition for local to the PBX?
If pbx is 192.168.1.1/24 , and if PC/NB's ip is also in 192.168.1.0 /24 ? and the PC refers to as "local" to the PBX?
or if PC/NB's ip is in 192.168.2.0 /24 and they can reach with each other? we can call the PC is local to the PBX?

Thanks.

Peter
Our environment is to use on-premise 3CX server, not in the Internet.

 

[VasilisV_3CX]

Hi @PeterCheng,

1. I checked the original windows app and it still remains in V16 even I've upgraded server to V18?
I'd like to know if you have to roadmap to keep the original winodws app,upgrade it, or EOL one day?

There is no v18 Windows Client at the moment. The latest version is 16.3.0.261 as per https://www.3cx.com/blog/change-log/3cxphone-build-history/

Everything will be EOL one day. However for now there is no deprecation going on so you're free to use it until told otherwise.

2. What's the definition for local to the PBX?
If pbx is 192.168.1.1/24 , and if PC/NB's ip is also in 192.168.1.0 /24 ? and the PC refers to as "local" to the PBX?
or if PC/NB's ip is in 192.168.2.0 /24 and they can reach with each other? we can call the PC is local to the PBX?

If it is in accordance with RFC1918, it's local. In your first example, it's local yes. And in your second example, it's still local. This is because 192.168.0.0 - 192.168.255.255 is included in RFC1918.

Hope this helps!