- Joined
- Jan 28, 2020
- Messages
- 14
- Reaction score
- 6
Hello,
We have been presented with the following scenario on one of the systems we manage:
x. 2015 calls x. 2023 -> straight to voicemail.
x 2023 calls x.2015 -> works as expected.
x.2015 can call all other extensions.
x.2023 can receive calls from all other extensions.
We have inspected outbound rules, call forwarding rules for 2023, exception rules for 2023 with nothing found awry.
Call is terminating with a 480 Temp unavailable message specifying the client lan public IP (All phones are STUN to public interface of phone system) - I cant seem to glean anything else from the logs. The internal phone log itself is not showing the missed call so it's not making it past the 3cx system.
Assumed it was a local outing issue at client sight, but have registered affected extensions to mobile apps offsite and testing yeilds the same results
Where else would there be a routing rule or setting that would cause this?
Any advice greatly appreciated
We have been presented with the following scenario on one of the systems we manage:
x. 2015 calls x. 2023 -> straight to voicemail.
x 2023 calls x.2015 -> works as expected.
x.2015 can call all other extensions.
x.2023 can receive calls from all other extensions.
We have inspected outbound rules, call forwarding rules for 2023, exception rules for 2023 with nothing found awry.
Call is terminating with a 480 Temp unavailable message specifying the client lan public IP (All phones are STUN to public interface of phone system) - I cant seem to glean anything else from the logs. The internal phone log itself is not showing the missed call so it's not making it past the 3cx system.
Assumed it was a local outing issue at client sight, but have registered affected extensions to mobile apps offsite and testing yeilds the same results
Where else would there be a routing rule or setting that would cause this?
Any advice greatly appreciated