Interworked Jabber 4.7 call crashes VCS

[Support Department]

We already reported this bug to Cisco but were wondering if any ther people ran into the same problem: If you set up a call using Jabber 4.7 and the call is interworked it will crash the VCS if the VCS is not at 7.1 or higher. This doesn't happen every now and then but each and every time we try.

The 'fix' is to upgrade the VCS to 7.1 or higher but it only happens with Jabber 4.7 (so in our opinion a bug) and it will solve the proble for us but not for any other company with a VCS that is not at 7.1 yet. If we 'upgrade' our Jabber clients, call over their VCS and the call is interworked it will crash their VCS.

So we were curious and wanted to know: Anyone else ran into this problem?

[Chad Patterson · Accepted solution]

This is due to Jabber 4.7 presenting the VCS with a 256-bit AES key in SRTP for a traversal call.

CSCua16714

Not sure that many people have run into this issue.

--

Chad Patterson

[monsterdrinker]

Actually we just ran into this yesterday.  We really couldnt believe it when it happened.  Then our phones started ringing with all the calls that were dropped from the VCS.

Wow...

[Martin Koch]

Nathaniel: If you have an older version than X7.1 I would recomend to upgrade anyhow.

Please remember to rate helpful responses and identify helpful or correct answers.

[Support Department]

That will work, but the Jabber client might still crash someone else's VCS. Setting encryption to 'AutoNoSrtp' in the provisioning settings also works and will also protect any other VCS with older firmware.

This is actually a confirmed bug in Jabber 4.7 (according to Cisco support) and should be fixed.