Collect the information requested in Table E-19 to determine the conferencing, transcoding, and MTP requirements for the planned IPT network. These questions will help you to determine the hardware required at the central and remote sites for these media resources and to group these media resources in the CallManager by properly configuring the media resource groups (MRGs) and MRG lists (MRGLs) as per these requirements.
No. | Question | Answer |
---|---|---|
1 | What is the maximum number of participants per conference call? | Max. participants: |
2 | What is the maximum number of conference sessions required? If you have multiple sites, list them in the table form as shown as follows. | Max. sessions: |
3 | Are you deploying multiple codecs in the IPT network? | List of codecs: |
4 | Do you plan to deploy applications such as CRS and Unity in the network? | List the applications and codec configured for these applications: |
5 | Do you plan to provide the conferencing and transcoding resources at each remote site, deploy all the resources at the central site, or use the distributed model? | |
6 | Do you want to use the conferencing, transcoding, and MTP resources on the CallManager servers that are part of the cluster? | Specify the CallManager server names where these features are enabled: |
7 | Do you plan to dedicate a server to provide the media resources in software? | Specify the number of servers and physical locations of the servers: |
8 | Do you plan to deploy hardware media resources rather than use the resources on the CallManager servers or use a dedicated server, or do you want to deploy a combination of both? | Fill in table E-20 with details. |
9 | Do you have any nonCisco H.323 endpoints that do not support Empty capabilities set? | Yes No Specify the endpoints and their locations: |
List the site-wide requirements for conferencing, transcoding, and MTP. To assist you, Table E-20 shows examples of the XYZ, Inc. network requirements.
Site Name | Codec Used | Media Resources Required Hardware or Software | Preference for Accessing These Resources | Hardware at the Site |
---|---|---|---|---|
San Jose | G.711 | Conferencing, transcoding, and MTP required Use hardware Disable the resources on CallManager | All San Jose users use the central site resources | Ad Hoc Conferencing and Transcoding (ACT) port adapter on CMM on 6500 switches |
Seattle | G.711 Local; G.729 on WAN | Conferencing, transcoding, and MTP required Use hardware | Seattle users use local resources first and then the resources at San Jose | DSPs on the NM-HDV modules on the Seattle router |
Dallas | G.711 Local; G.729 on WAN | Conferencing, transcoding, and MTP required Use hardware | Dallas users use San Jose resources | No DSP resources are available for media services on the local router |