Hi All,
So here we go again. Another interesting issue which I'll have to raise on IPOSS but always worth asking here as well.
9611 re-registration issues after it loses connection to the IP Office.
So the scenario is, we run Partner Hosted Server Edition and Normal Server Edition within our DC's with an MPLS over our own network to the customers site. We had a recent issue on our core network which meant that the main connection and backup connection on site both lost their routing. All handsets on site lost their registration.
When the circuits came back 3 minutes later the handsets started registering but only half of the 500 extensions actually got through to the phone system. We had to get the end user to reboot the handsets in the morning to re-register. This was only on the 9611's. All the SIP devices came back straight away.
Has anyone came up against this at all? Or does anyone know any hidden code we can put into the 46XXsettings to change the registration timeouts?
Thanks Peeps.
So here we go again. Another interesting issue which I'll have to raise on IPOSS but always worth asking here as well.
9611 re-registration issues after it loses connection to the IP Office. So the scenario is, we run Partner Hosted Server Edition and Normal Server Edition within our DC's with an MPLS over our own network to the customers site. We had a recent issue on our core network which meant that the main connection and backup connection on site both lost their routing. All handsets on site lost their registration.
When the circuits came back 3 minutes later the handsets started registering but only half of the 500 extensions actually got through to the phone system. We had to get the end user to reboot the handsets in the morning to re-register. This was only on the 9611's. All the SIP devices came back straight away.
Has anyone came up against this at all? Or does anyone know any hidden code we can put into the 46XXsettings to change the registration timeouts?
Thanks Peeps.