Understanding MRG and MRGL

[wilson_1234_2]

  Sorry for the basi question:

I am looking at our config in the Media Resource Group configuration, in that page there is a box that shows the "Devices for this Group" and it shows the "Available Media Resources".

It looks like the Available Media Resources are gathered from the menu items listed above Media Resource Group listed on the configuration page.

Is this correct?

When looking at some of those items, like "Annunciator" for example, there is no option to create a new one. Where do those items get created?

Also, how does a MOH server get created?

[Jaime Valencia]

What shows in the available resources are MTPs, MOHs, ANNs and XCODERs which haven't been assigned to any MRG.

The SW ANN, MTP and CFB are created via the IPVMS and thus only one instance can exist per service and per server.

You can only create any of those if your first delete them.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[wilson_1234_2]

If they are created by the IPVMS, does the name of the ANN or CFB get generated automatically?

Also, does the number of these get created automatically?

For example per my server, I will have a certain amount of ANNs, CFBs?

And, how do the MOH server get created?

[Jaime Valencia]

Yes, everything related to those media resources related to the IPVMS is created automatically once you start the service.

You get one MOH, one SW CFB, one MTP and one ANN per IPVMS running, you can only run one IPVMS per server.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[wilson_1234_2]

Thanks for the answers Java.

Our current phone system has been upgraded a couple of times, and put on new hardware.

The current ANN, MOH and MTP resources have the IP Address of the original server in their name. These IP addresses were from the original config and are no longer accessabel via IP Address.

Would this be a result of the way the latest server was created, which it must have been backup restored to the new server causing all of the original names (with old IP Addresses) to carry over to the new config.

Does this make sense?

If the above is correct, we about to upgrade to UCS and the same company is going to do the implementation, which is going to be another build new hardware and restore config to new hardware.

Is there any way to control the name on the new builds to something more relevant to avoid confusion?

[Jaime Valencia]

If they're working fine and registered you can just go ahead and change the device name of each media resource.

If the server on which they were, is no longer part of the cluster, you can try to delete them.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[wilson_1234_2]

Thanks Java,

That is the thing, the server on which they were originally created no longer exists. The name reflects the old IP Address, but they are registed in the new cluster with the new IP Addressing scheme.

It seems the new server would have it's own IP Address in the name, but apparently when the server gets restored to the new server, there is no need to change the name of the existing resource.

Another question:

Do all physical devices have to have a MRGL assigned to them?

Is it isolated to physical devices only?

[Jaime Valencia]

Once they are created they won't change, that info is retained and that is expected.

If you need media resources, then you need assign a MRGL to devices, and that applies to any kind of device.

I strongly recommend you to review the media resources chapter from the SRND.

EDIT: UNLESS you do not assign any media resource to a MRG and then they are in the default MRG which is like the partition, it's at the bottom of the list even if you don't see it. Then you don't necessarily need to assign a MRGL, but that's very poor design.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

[BalajiSivaraj49175]

MRG using in the phones gateway conference bridges MTP transcoder between different device on using the location region where this can be used in DSP to pockets the digitized at the voice by samples followed between the devices using RTP and ISDN calls like digitized signal

[BalajiSivaraj49175]

MRG and MRGL used in the different devices like phones hunt group hunt list call queue hold the calls in the phone. where this MRG are used to for compressing the calls using the codec. Playing the prompt on hold. Interactive voice Hunt group and hunt list

[BalajiSivaraj49175]

Communications Manager functionality requires the use of media resources. Communications Manager includes media resources such as:

Annunciators
Interactive Voice Response (IVR)
Media Termination Points (MTP)
Transcoders
Trusted Relay Points
Conference Bridges
Music On Hold/Video on Hold

Features of the IPVMS

[BalajiSivaraj49175]

Trusted relay points uses the signaling calls sampled converted in digitised to IP IP to digitised convertion sampling are information ported using the logic ports commuication by the differant protocols

TRP requirement for individual calls by setting the Use Trusted Relay Point field to On for the following configuration windows:

Phone Configuration

Gateway Configuration

Voicemail Port Configuration

Trunk Configuration

CTI Route Point Configuration

Common Device Configuration

Universal Device Template Configuration

Various media resource configurations (Annunciator, IVR, MTPs, Transcoders, Conference Bridges, Music On Hold)

[BalajiSivaraj49175]

Media Termination Point Required check box and the Use Trusted Relay Point check box for an endpoint, Communications Manager should allocate an MTP that is also a TRP. If the administrator fails to allocate such an MTP or TRP, the call status appears.