Fix Forward Cisco Call to Skype for Business Cloud Connector

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

sonus_cisco_fwd_1

The only difference with the failing call was the addition of the Diversion header entry.

sonus_cisco_fwd_2

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

sonus_cisco_fwd_3.png

I then created a header rule

sonus_cisco_fwd_4

Which then had an action of Remove for the header name of Diversion, I didn’t add any conditional access expression.

sonus_cisco_fwd_5

After creating the rule I added it as an Outbound Message Manipulation entry on the Skype CCE signalling group

sonus_cisco_fwd_6

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.

Post to Twitter

Leave a Comment

Your email address will not be published. Required fields are marked *