High latency remote worker

[SeanusT]

Hi,

I am planning to deploy 3CX in our office in the UK.
I have a remote worker based in Singapore. The latency between the UK and Singapore is around 230ms.

I use Twilio for my SIP trunks using either their DE or IE endpoint.
For my Singapore worker though the call is having to flow through the UK even if they are calling Singapore, adding a lot of delay to the calls.

Is there a way for the remote worker to use the Twilio SIP trunk endpoint in Singapore whilst still being connected to my UK 3CX PBX?
Or will I have to install a cloud 3CX in Singapore - AWS, Azure, whatever - and then bridge it back to UK?

Thanks,

 

[AWS2P]

Do you have lot of phones in Singapore?
Of course your idea to host cloud PBX near Singapore make sense and bridge only for internal calls

 

[SeanusT]

It's just one worker we've got in Singapore so i'm not overly keen on having to run a separate PBX just for them.

I think it's the only way to achieve what I want though?

 

[JohnS_3CX]

Hi SeanusT

If you bridge Singapore with UK, the distance will still remain the same. That person will not benefit if he calls out via the trunk that is based in the UK.

You might want to have two PBX instances (one per region) with their own trunk that is closer to the people using it.

The bridge will only help with internal calls between offices

 

[SeanusT]

Thanks John, yep I'm aware of that, I was just saying that to maintain their ability to call back to the UK office extensions, the two proposed instances would need to be bridged.

Each PBX would have separate trunk configs to enable the user in Singapore to not suffer delays when calling Singapore numbers.

I was hoping that there was a way to achieve delay-free calls for the Singapore user without multiple PBX's but I imagine we're confirming that isn't possible?

Thanks

 

[JohnS_3CX]

The roundtrip is too long so I guess not. You could possibly/maybe get a local number in Singapore and forward UK calls to that number so you can use the carrier's transport link which might be lower latency.

But that would still incur very high call costs and the latency for them might not be much lower than what you have now so I would not consider that a solution (even though it is doable)

 

[AWS2P]

If there"s only one worker and in future won't be more so why trying to solve this with 3cx, just pay for a local mobile line in Singapore and use App to stay in touch with 3CX UK .

 

[leejor]

Have you checked to see if there are other ISPs (one end or the other) that do not have the same Latency issues. If the latency is because of the distance, then there may be no way around that, but, if one provider is introducing latency because of their network design/routing, then you might consider a switch, to bypass them.

If you had a single PSTN line in Singapore, you could make use of a device like the Linksys SPA-3102 (no longer made, but still available if you do a search). It can handle both a local line and a 3CX extension, with outgoing calls routed automatically using an internal dial-plan. Incoming PSTN calls can ring the local set, then route to the 3CX extension voicemail after a timeout. I use that setup when I travel, and there is a local PSTN line available.

 

[AWS2P]

And a call from Singapore to Singapore goes around the earth giving us some more carbon

Very often the simplest solution is friendly use and cost less , as we say in french " Pourquoi faire simple quand on peut faire compliqué"

One Worker can be available with 3CX App and be able to call around Singapore with mobile or local land line