Has anyone else come across this running a recent version of 4.4.0? When I say recent, I'm referring to update #15, as that's the latest we're running in production. I didn't see anything in the release notes for update #16 that would indicate that this was something that was fixed, though.
Basically, the server seems to simply stop responding to registration requests. AFAICT, sipXproxy loses its connection to sipregistrar on tcp port 5070 and needs to be restarted in order to re-establish this. This has happened to us on multiple servers running 4.4.0 update #15 with Polycom phones running 3.2.6/4.3.1 as remote workers. -- _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
