- Joined
- Oct 1, 2018
- Messages
- 6
- Reaction score
- 0
Hello,
Last night we upgraded to V16.0.1581 and everything seemed to go fine. After the update, we saw that all out phones firmware was out of date (we have about 30 Yealink T42S's) so we upgraded all the firmware as well. This morning, we are getting user complaints about phone calls being routed to the wrong phone, calls failing. When I look at the "Phones" screen in the 3CX admin dashboard, I see many duplicate registrations. The weird thing is that it seems to only be happening in our AZ office, and not in our NY office.
Again, everything was working fine before. Our configuration is:
Cloud 3CX, hosted on AWS
Remote phones in two offices (NY, AZ), configured by STUN all behind firewalled NAT
I'm no expert, but it seems like it could be a port overlap issue. Is it possible that something changed in the Yealink T42S template where we are now getting port collisions where we weren't before?
Any help is GREATLY appreciated!
Thanks,
Marc
Last night we upgraded to V16.0.1581 and everything seemed to go fine. After the update, we saw that all out phones firmware was out of date (we have about 30 Yealink T42S's) so we upgraded all the firmware as well. This morning, we are getting user complaints about phone calls being routed to the wrong phone, calls failing. When I look at the "Phones" screen in the 3CX admin dashboard, I see many duplicate registrations. The weird thing is that it seems to only be happening in our AZ office, and not in our NY office.
Again, everything was working fine before. Our configuration is:
Cloud 3CX, hosted on AWS
Remote phones in two offices (NY, AZ), configured by STUN all behind firewalled NAT
I'm no expert, but it seems like it could be a port overlap issue. Is it possible that something changed in the Yealink T42S template where we are now getting port collisions where we weren't before?
Any help is GREATLY appreciated!
Thanks,
Marc