Video Conference Server

[58voip]

Hello 3CX Team,

Is the India MCU server the only one in Asia? There were servers in Taiwan, and Singapore previously. Now I always got the MCU server in India.

 

[LeonidasG_3CX]

Are you experiencing issues with the Indian MCUs? If so, what kind of issues? If you could elaborate a bit that would be great.
We haven't had Taiwan or Singapore MCUs in a very long time.

 

[58voip]

Our problem is that the Websoket RTT is 380 ms and the media RTT is 250 ms. It's a long way for us to access the MCU server in India

 

[LeonidasG_3CX]

Yeah that's really high. We'll try adding some Singapore MCUs as well and possibly something near Japan to serve those areas.

 

[LeonidasG_3CX]

@58voip I've gone ahead and spawned a Singapore MCU. Let me know if the RTT has dropped and what it currently is at.

 

[58voip]

We will test from different locations and ISPs to see the performance.

 

[58voip]

We connected to the Singapore MCU across different locations with different ISP last week. It seemed the WebSockt RTT is much worse than connecting to India. It was from around 300ms to 2,000ms. Connecting to the India MCU, both Websockt RTT and media RTT are around 300ms.

Will you consider adding an MCU server in Hong Kong that can serve both East and South East Asia customers?

 

[LeonidasG_3CX]

I've gone ahead and temporarily added as044-hkg.3cx.net
Give it a try and let me know how it compares to the rest.

 

[58voip]

The last 2 times attempts were still reaching out to the server in India. Anyway to force it to connect to the HK MCU server?

 

[LeonidasG_3CX]

It looks like the distance to Bangalore vs Hong Kong is quite similar from where you are.

Create and join several different meetings. The first few may go to India, the last bunch are likely to be routed to Hong Kong.

If you let me know what province you're from, i will try tuning our routing algorithm a bit so you will hit Hong Kong more often.

 

[58voip]

Now we could access the MCU in Hong Kong. The WebSocket RTT from China is 116ms, and from Japan is 52ms. But there is no media in the meeting no matter we started it from China or Japan. Any configuration needs to be set up at the MCU side?

 

[LeonidasG_3CX]

Give it another try.

 

[58voip]

The video and audio worked. The WebSocket and media RTT had been significantly improved. We tested from 2 different locations in China. I attached the screenshots below. We will try to test from other Asia countries tomorrow.

 

[LeonidasG_3CX]

Alright. In the meanwhile i'm going to try adding Osaka, Tokyo and Seoul. Hopefully one of those has similar performance as the one above.

 

[LeonidasG_3CX]

@58voip I've gone ahead and added a Tokyo, Osaka and Seoul MCU. You'll have to open a few meetings to eventually get routed to all of them.

Let me know how they perform for you. Keep in mind that these are temporary, even the Hong Kong one. Once we find which ones work well for you, we're going to run a few tests of our own on them and see which ones we're keeping.

 

[58voip]

@LeonidasG_3CX, we tried this morning. We can access the MCU in Hong Kong, Seoul, and the USA. Below are the screenshots.

 

[58voip]

We can not access the MCU in Tokyo or Osaka. Even if the meeting is initiated from Japan, it always connects to the MCU in Seoul. Tried 6 times in one same web client user. And also tried to initiate the meeting with other 3CX users in different 3CX systems in Japan.

 

[58voip]

BTW, will the changes of adding these temporary MCUs affect the existing 3CX pbx voice performance?

 

[LeonidasG_3CX]

The third image you posted is showing a connection to Osaka. If you saw "United States" instead of "Osaka" then it's likely just a geolocation database issue that you can safely ignore.

It looks like the latency to Seoul & Japan aren't great. We'll keep Hong Kong for now until we can find a decent alternative.

BTW, will the changes of adding these temporary MCUs affect the existing 3CX pbx voice performance?

These servers don't affect your PBX audio quality in any way. They are only used for 3CX Video Conferences. In any case we'll be removing the Japanese and Korean servers as their latency is too high even though you're so close to them.

 

[58voip]

Well noted with thanks.