Cisco Expressway RMS licenses for B2B calls

[bejoy.cisco]

Hi Experts,

we have Cisco Expressway setup for B2B calls. we have 6 RMS licenses distributed between Expressway C & E, which makes it 3 on EXP E and 3 on EXP C.

Now I am able to make 3 party conference including the Host. That is myself and 2 other B2B calls in one Video conference. Where as we were looking for 3 party conference excluding the host.

We were under the impression that if we purchase 3 RMS licenses we will get 4 party video conference. That is 3 outside calls excluding the Host.

Can anyone explain how the RMS license works.

Our IPT set up:

CUCM 10.5

SX20 - registered to CUCM

Expressway C - Containing 3 RMS Licenses

Expressway E - Containing 3 RMS Licenses 

Regards

Bejoy

[Manish Gogna · Accepted solution]

Hi Bejoy,

RMS licenses are concurrent, so in your case two RMS licenses (one in each Expressway) per call are required. You may check the following posts related to similar queries

https://supportforums.cisco.com/discussion/12444331/jabber-guest-required-licenses

https://supportforums.cisco.com/discussion/12522961/rms-license-cisco-expressway

https://supportforums.cisco.com/discussion/12240916/expressway-lic-exp-rms-rich-media-session-license-requirements

Manish

- Do rate helpful posts -

[bejoy.cisco]

Hello Manish,

Thanks for the reply.

I understand, for one B2B call I require 2 RMS licenses, each on VCS - C and VCS - E.

But as per the posts you have shared, an internal call must not consume any RMS licenses. That is if I am on a B2B call from and SX20 registered to my CUCM and I am trying to make an internal call to another SX20 registered to the same CUCM. Will this consume another RMS licenses ?

We have 3 RMS licenses on both VCS-E and C. I can have a 3 party conference, but when I try to introduce a 4th party weather it is internal or external, it doesn't work.

Can you please clarify.

Regards

Bejoy

[Manish Gogna]

Hi Bejoy,

I believe this is how it should work, since even the internal parties will be a part of the same conference which has an external participant and it will have the RTP and signaling flowing through the expressway.

Manish

[Frank P · Accepted solution]

B2B calls are between two different organizations and not within your domain

RMS licenses are used for B2B calls, IPv4 to IPv6 calls, SIP-H323 calls, and when the media is routed through the Expressways (for external calls, the media will always traverse the expressways).

[dsobrinho]

Hi Guys,

One doubt about this.

I have Expressway C and E in dual nic static, and video endpoint registered in CUCM. I have applied the License Cisco RMS only in the Expressway E. But after mounths the customer have a problem with B2B after change rule in firewall. The local engineer open a tac case and the engineer  told him that need apply Cisco RMS in both Exp C and E to make and receive video calls to and from external H323 Endpoints video.

Does anybody knows if this is correctly?

Best regards

Daniel

[Patrick Sparkman]

RMS licenses are required only on Expressway-E if running X8.8 and later for these call scenarios:

• B2B
• Jabber Guest
• Microsoft Interoperability Gateway

RMS licenses aren't required for these call scenarios:

• Spark Connectors
• CMR
• MRA (calls between endpoints registered to CUCM)

[dsobrinho]

Thank you for your answers.

Following the Scenario:

The local Customer want to receive external calls from video endpoint H323 to his uri jabber, so in this scenario I have received an alarm from expressway saying that need RMS applied in Exp C.

The version is 8.9.2

[Patrick Sparkman]

I know the license scheme changed with X8.8 when they added endpoint registration to the Expressway to what I mention in my previous reply, that must only apply if the endpoint making the call is registered to the Expressway, and doesn't apply to B2B calls to/from CUCM for example.

[dsobrinho]

Hi Patrick

After open a tac the engineer request us to split the RMS that already have installed in Exp-E and share with Exp-C. Now b2b to external domains H323 and SIP is working fine.

Best regards,

Daniel