We performed some fail over testing in order to gain confidence in our new VOIP solution.
The system went into ESS with no issue and all the handsets re-registerd. The system then recovered from ESS with no issues and the handsets re-registered. However, further integrations revealed that we could not make outbound call, our DS1 boards (MM710 modules) were no longer recognised and showing as "no board" in CM when we did a list con all.
We attempted to reseat the boards but this did not resolve the issue. We also reset the gateways and also powered off the gateways but the boards were still not recognised.
To recover we had to seat the modules in different slots and reconfigure. However we left one in its original slot for troubleshooting purposes
We raised a case with our provider who suggested a firmware upgrade to our media gateways. The release notes for the upgrade did state that it would fix an issue with MM710 modules not being recognised following a reset.
We attempted the firmware upgrade last night but the issue still remains. It would appear that while the new firmware prevents the boards from not being recognised but it does not recover the slots in the gateway if the issue has already occurred.
Does anyone have suggestions how we may recover from this scenario?
Interestingly, when we log on to the CLI of the Gateways we can see the module we left in its orginal slot. When we look on CM it is still reporting "no board"
We have the following
2 x S8800 Duplicated Servers, 1 x S8800 ESS
CM 5.2
2 x G450 Media Gateway
Cheers
StuWal
The system went into ESS with no issue and all the handsets re-registerd. The system then recovered from ESS with no issues and the handsets re-registered. However, further integrations revealed that we could not make outbound call, our DS1 boards (MM710 modules) were no longer recognised and showing as "no board" in CM when we did a list con all.
We attempted to reseat the boards but this did not resolve the issue. We also reset the gateways and also powered off the gateways but the boards were still not recognised.
To recover we had to seat the modules in different slots and reconfigure. However we left one in its original slot for troubleshooting purposes
We raised a case with our provider who suggested a firmware upgrade to our media gateways. The release notes for the upgrade did state that it would fix an issue with MM710 modules not being recognised following a reset.
We attempted the firmware upgrade last night but the issue still remains. It would appear that while the new firmware prevents the boards from not being recognised but it does not recover the slots in the gateway if the issue has already occurred.
Does anyone have suggestions how we may recover from this scenario?
Interestingly, when we log on to the CLI of the Gateways we can see the module we left in its orginal slot. When we look on CM it is still reporting "no board"
We have the following
2 x S8800 Duplicated Servers, 1 x S8800 ESS
CM 5.2
2 x G450 Media Gateway
Cheers
StuWal
