During the deployment of a slave CCE appliance when it came to the last step I received an error message: We failed to run Publish-CCAppliance.
I waited around 5 minutes and ran the step again and it completed successfully and the appliance started handling calls, I was unable to see what the Management service was doing or why the automated process wasn’t able to handle it but I’d thought I would share and reassure people that running it again worked.
During a recent Sonus Cloud Link deployment integrating Skype for Business Online with Cisco Call Manager I ran into an issue with certain calls failing. As the customer were piloting the system we were not yet removing users existing Cisco extension but rather forwarding it to their Skype number.
If Cisco users called the Skype number directly it would work but if they called the forwarded extension it would fail, strange.
So first step was to look at the Sonus logs to see if I could spot anything, on the working call everything looked normal
The only difference with the failing call was the addition of the Diversion header entry.
Now I’d found a difference it was time to see if I could change the forwarded calls header to be the same as the working call. Since we were using the Skype Cloud Connector Edition we couldn’t make any changes on the Skype side as they’d be lost following any update.
Luckily we were using a Sonus to route calls between the two, so I created a Message Manipulation Rule under Message Rule Tables
I then created a header rule
Which then had an action of Remove for the header name of Diversion, I didn’t add any conditional access expression.
After creating the rule I added it as an Outbound Message Manipulation entry on the Skype CCE signalling group
After which forwarded calls worked as expected. I’m not sure why the Skype CCE or Skype Cloud PBX did not like the diversion header but the customer was happy with the result.
Having just completed my first highly available Sonus Cloud Link I just thought I would mention an error message I came across when installing the second appliance.
The Sonus Deployer tool showed a very nice red error message saying the Powershell module is not ready
This was also shown in the underlying PowerShell window
I had seen a similar message during the installation of the Skype Online Powershell module when you try to load it without having restarted, however the ASM server had been rebooted and I was able to load Skype for Business Online PowerShell module and connect to the tenant.
If you read all of the notices and guides you will see mention that the length of time it takes to deploy the second appliance is dependent on the connectivity and speed of the first, which led me to check the first appliance.
I then discovered that the Primary appliance actually had been configured as standalone! It was then a case of redeploying the CCE configuration, this time ensuring the HA Master option remained selected and then afterwards the second appliance was able to progress.
Lesson of this story, ensure you get the configuration correct on the Master appliance and make sure it is saved!