Jabber Guest Deployment

[t00829109]

In the Jabber Guest deployment Guide it has the following statment

You cannot use the same Cisco Expressway-C and Cisco Expressway-E pair or

cluster for both Cisco Jabber Guest and Expressway for Mobile and Remote Access.

Does this mean that Jabber Guest requires a dedicated Expressway or VCS pair?

[Paul O'Dwyer]

That's correct. For this current release (Guest 10.0 and Expressway x8.2) Jabber Guest CANNOT be run on the same pair as Jabber MRA. There is technically some conflicts that occur amongst certain resources in the expressway, such as TURN. The co-existence of the features on the same expressway pair is under evaluation on the expressway backlog

Regards,

Paul

[twilson217]

How about this scenario? A customer requires Jabber Guest and B2B calls with video endpoints registered on CUCM, but they do not require MRA. Can Jabber Guest and B2B calls exist on the same Expressway C/E pair?

[Marcelo Morais]

Hi,

Jabber Guest 10.5 (C2B) restrictions is in the simultaneous use with 'Expressway for MRA'.

There is no restriction on using with a B2B (available since CUCM 9.1) deployment.

Hope this helps.

[Christian Holst]

to consolidate rich media licenses it makes sense to combine B2B and Jabber guest on the same pair.

I guess you have scenarios where you would like to "reserve" rich media licenses for either B2B or jabber guest and in that case put B2B with MRA.

I would recommend:

Cluster A: MRA

Cluster B: B2B and Jabber guest (this cluster would have all the rich media licenses)

And then lets hope Cisco will archive consolidation of all 3 functions onto the same cluster soon

Total 16 cores and 32GB Ram just for Expressway with HA is a bit too much !

[Brian Carscadden]

This is the way to go. We've deployed using this design and (as of now) it is the best approach.