Sounds like you might have other issues in this case, is this a STUN phone?
Test it on a local 3CX server or use an SBC and let us know if the problem went away.
Factory reset it before provisioning on a V18 system to ensure that the correct parameters are loaded.
Hi John,
It's definitely a STUN issue. Below is what I've come across so far with it which is pretty interesting as it's only with the SIP-T58W model. I even tested with a T58W non-pro and same result. The T58 which we had previous, didn't run across any of these issues so it's only for the T58W.
We don't have a local system at all as everything is hosted int he cloud. So initially I tested with the SBC and all was fine.
Then started to troubleshoot the STUN issue:
1. Default template uses STUN port 5060 to the PBX. Phone registers but then won't show any of the presence information or allow incoming calls. Outbound calls are fine. No audio issues.
2. Use the default template to allow it to provision and grab it's config but then when you manually go into the phone interface, change the STUN to port to 3478, apply and then the phone is fully operational.
3. Created a test template and changed the STUN port on the template to 3478. Factory reset the phone and had it re-apply. Grabs the config but then the phone won't register at all. Manually go into the web interface, change STUN port to 5060, let it register and then change the port back and then all presence information and incoming calls work.
3. Created a test template and disabled STUN for the remote phone. Factory reset, it grabbed the config, registered and showed all presence information and allowed incoming calls. No audio issues whatsoever and it's acting as it should.
Something odd for this model for sure.
