Moved our 3cx to Google

[Chaz]

I have a couple questions. Our s seems to be working fine.

1. Should I be expecting a static from google. It shows one, but it says dynamic.

2. Any issues with using google with about 20 phones and 3CX stun? I have a customer that we are presenting to this week.

3. On the app, and the windows phone, should the server be our FQDN or the static IP?

4. Last, is there a way to speed up the dialing. Seems a tad slower since we moved it to the cloud.

Thanks,

 

[AWS2P]

1 you probably need to set it static in Google console
2 no idea if you should be fine but STUN is a bad idea for 20phones, 3Cx recommend use of SBC since 2 phones, so your best idea is a SBC or a VPN but in that case phones are local and not in STUN.
3 If your IP is STATIC and FQDN resolve properly , then set with FQDN.
4 what region did you choose during install of google instance? datacenter isn't it too far from you ?

 

[eddv123]

Any issues with using google with about 20 phones and 3CX stun? I have a customer that we are presenting to this week.

Best see this post here (there are several others on the forums also):

https://www.3cx.com/community/threa...andomly-3cx-16-0-5-619-aws.75194/#post-339985

Other issues can include 1 way/no way audio and issues with call transfer/parking/pickup also - all normally related to the firewall.

 

[Lee Cramman]

I have a couple questions. Our s seems to be working fine.

1. Should I be expecting a static from google. It shows one, but it says dynamic.

2. Any issues with using google with about 20 phones and 3CX stun? I have a customer that we are presenting to this week.

3. On the app, and the windows phone, should the server be our FQDN or the static IP?

4. Last, is there a way to speed up the dialing. Seems a tad slower since we moved it to the cloud.

Thanks,

1. You have to set this in Google Compute. You can reserve a static IP and then assign it to your VM. However, you can end up with DNS issues while you wait for the new address to propogate. It might be a better option to promote your ephemeral IP address to static. See https://cloud.google.com/compute/docs/ip-addresses/reserve-static-external-ip-address.

2. Friends don't let friends use STUN. Use an SBC - it will save you a world of effort and pain.

3. FQDN

4. No idea. The region shouldn't make that much difference - a few ms (although you should have still picked the one closest to you!).

 

[Chaz]

Thanks. We are close to selling 20 phones, and the customers insists on 3CX in the cloud. Where will the SBC reside? Most of the users will be working from home. 4-5 at the office.

 

[eddv123]

Where will the SBC reside?

Normally the same site as the phones (if all located within the same local office subnet). Based on your response however it sounds like you want a single phone per home user ? please confirm.

If single phone per home user STUN can be used however beware of issues introduced by home networks - mostly related to provider home routers.

 

[Chaz]

Yes, most will be working from home. We are using stun on ours, but we only have 4 phones on it.

 

[Lee Cramman]

If working from home I would be tempted to push everything through the web app instead of hard phones (it's really rather good!) or use the app on mobile phones.

If there really is no option except for hard phones then you'll just have to give it a go. It can be made to work but expect more install / support headaches than usual.

 

[eddv123]

I would be tempted to push everything through the web app instead of hard phones

I would agree with this if web client and USB headset are available as an option, if you get a local router with provider hard coded settings you may have trouble.

Web client uses Web RTC which has a lot of settings which help bypass such issues.