One sided audio issues

[vrelk]

I am having issues with a new setup of 3CX I am running at home. I am using a pair of Polycom SPIP 450's and the 3CX app. All of the testing here is on the local network, including the phone running the app, and other than that, all the ports are opened without NAT. I have been working at this so far today, and haven't found anything that helped in my research. Maybe someone here will have an idea.

Phone subnet: 192.168.12.0/24
App subnet: 192.168.1.0/24
3CX IP: 35.xxx.xxx.xxx
The PBX is sitting on a public IP, behind a firewall, but it is a local connection between the phone subnet and PBX without natting.

Phone A    -> External       = No inbound audio on phone A
Phone B    -> External       = No inbound audio on phone B
3CX App    -> External       = Works fine

Phone A    -> Phone B        = Works fine
Phone B    -> Phone A        = Works fine
Phone A    -> App            = Works fine
Phone B    -> App            = Works fine
3CX App    -> Phone A        = Works fine
3CX App    -> Phone B        = Works fine

 

[cobaltit]

SoundPoint IP phones are not supported for any scenario not involving direct (Local LAN) access to 3CX. This means NO NAT between 3CX and the phones.

 

[Saqqara]

Have you tried selecting 'PBX Delivers Audio' under Extensions - Options

 

[vrelk]

You beat me to editing or deleting my initial post. I thought of a possibility last night, and it ended up being correct. I had forgotten to add a static route to the subnet 3CX is running on when I created the subnet for the phones. I didn't think of it at first because the TCP web requests still worked when provisioning.

SoundPoint IP phones are not supported for any scenario not involving direct (Local LAN) access to 3CX. This means NO NAT between 3CX and the phones.

That is good to know because I was going to put set one of these phones up remotely. I will give it a shot anyways, but if it doesn't work I will just go ahead and get a newer phone that cost more than $12 rather than spending a bunch of time troubleshooting it.

Thanks!