I have searched up and down and have not found a thread addressing this question. I have seen that 3cx does not support multiple extensions from the same PBX on a phone. this is sort of a reverse of that situation.
Here is the scenario (for employees that service and support multiple sites as contract in house help-desks for site B and C from Site A)
Site A: local PBX @192.168.26.A
Site B: remote PBX @SiteB.ok.3cx.us (3cx provided DDNS)
Site C: remote PBX @SiteC.ok.3cx.us (3cx provided DDNS)
Site A Phones using extension 300-310 locally, (phones are yealinks: T46, T54W, and T53). local extensions work assigned under "Account 1", NAT traversal: Disabled
"Account 2" assigned to Site B extensions, different authID and passwords, etc. this also works but it wants to use STUN and there's only one place to enter a STUN server for the phone in general, not per account. each account can have "NAT traversal" set to disabled or STUN, but the STUN server is set on the "Network" tab under NAT options(globally).
"Account 3" assigned to Site C extensions, also different credentials, etc. This sometimes works but intermittently. also wants to use stun but seems to use STUN server defined for the phone.
STUN server that works for Account 2 is "SiteB.ok.3cx.us" - when i change this to a 3cx server like stun-us.3cx.com or stun2.3cx.com, both account 2 and 3 stop functioning, when i change it back account 2 works but not account 3. when i flash the factory defaults and program from scratch and remove the auto provision URL from the global settings for the phone, everything works well toggling between accounts for outbound and inbound calls (outbound call ID changes, can receive inbound calls with distinctive ring for each PBX, etc). Setups fail sometimes after a week sometimes after a few hours...
Is there an issue with using 3cx STUN servers? DSS functions keys work with the "local" stun server setup (when connected). Site A and B have Sonicwalls (no VPN) but site C has a Linksys. SIP ALG is disabled everywhere and Hairpin NAT is setup at all locations.
Thanks!
Attached: screenshots of Yealink config pages showing status, settings, etc.
Here is the scenario (for employees that service and support multiple sites as contract in house help-desks for site B and C from Site A)
Site A: local PBX @192.168.26.A
Site B: remote PBX @SiteB.ok.3cx.us (3cx provided DDNS)
Site C: remote PBX @SiteC.ok.3cx.us (3cx provided DDNS)
Site A Phones using extension 300-310 locally, (phones are yealinks: T46, T54W, and T53). local extensions work assigned under "Account 1", NAT traversal: Disabled
"Account 2" assigned to Site B extensions, different authID and passwords, etc. this also works but it wants to use STUN and there's only one place to enter a STUN server for the phone in general, not per account. each account can have "NAT traversal" set to disabled or STUN, but the STUN server is set on the "Network" tab under NAT options(globally).
"Account 3" assigned to Site C extensions, also different credentials, etc. This sometimes works but intermittently. also wants to use stun but seems to use STUN server defined for the phone.
STUN server that works for Account 2 is "SiteB.ok.3cx.us" - when i change this to a 3cx server like stun-us.3cx.com or stun2.3cx.com, both account 2 and 3 stop functioning, when i change it back account 2 works but not account 3. when i flash the factory defaults and program from scratch and remove the auto provision URL from the global settings for the phone, everything works well toggling between accounts for outbound and inbound calls (outbound call ID changes, can receive inbound calls with distinctive ring for each PBX, etc). Setups fail sometimes after a week sometimes after a few hours...
Is there an issue with using 3cx STUN servers? DSS functions keys work with the "local" stun server setup (when connected). Site A and B have Sonicwalls (no VPN) but site C has a Linksys. SIP ALG is disabled everywhere and Hairpin NAT is setup at all locations.
Thanks!
Attached: screenshots of Yealink config pages showing status, settings, etc.
