Appendix E. IPT Design Phase: IPT Requirement Analysis Questionnaire

The purpose of this questionnaire is to help you collect the customer’s information that you need to design the customer’s IP Telephony (IPT) network. You need to collect this information for each site. To obtain the answers to this questionnaire, you can either take it and meet with the customer or e-mail it to the customer and have the customer complete it. Customers usually provide some part of the information requested in this questionnaire in their Request for Proposal (RFP).

After you obtain from the customer all the information requested in this questionnaire, you can start the design process. Refer to Chapter 6, “Design of Call Processing Infrastructure and Applications,” to review the example of how the information collected in this questionnaire for XYZ, Inc., was used in its IPT network design.

The following is an outline of the sections in the IPT Requirement Analysis Questionnaire:

  • IP Telephony Deployment Model

  • Codec Selection

  • Legacy Voice-Mail Integration Requirements

  • Legacy PBX Integration Requirements

  • Sizing the CallManager Cluster

  • Branch Office IPT Requirements

  • Class of Restriction Requirements

  • Call-Routing and Dial Plan Requirements

  • Sizing the PSTN/Gateway Trunks

  • Power Requirements (Per Site/Per Switch Specific)

  • Call Admission Control Considerations

  • Corporate Directory Requirements

  • Conferencing, Transcoding, and MTP Requirements for Central Sites

  • Music on Hold Requirements

Some sections might not be applicable to the network that you are designing, so skip any such sections.

IP Telephony Deployment Model

The type of deployment model that you should choose depends on, among many other factors, your customer’s needs, users, geographical distribution of users and devices, call-processing volume at each location, and disaster-recovery plans.

You have four choices of deployment models, which are numbered for easy reference in this questionnaire:

  1. Single site with centralized call processing

  2. Multisite WAN with centralized call processing

  3. Multisite WAN with distributed call processing

  4. Clustering over the WAN

Use Table E-1 to identify the chosen deployment model.

Table E-1. IP Telephony Deployment Model

No.

Question

Answer

1

What IPT deployment model are you adopting?

□1

□2

□3

□4

(Refer to the previous list for the model name)

2

If you have selected option 4, what is the round-trip time (RTT) between the sites hosting the servers belonging to the same cluster?

RTT             _____ ms

Notes/Comments

The choice of IPT deployment depends on your network architecture and requirements. Refer to the section “IP Telephony Deployment Architectures” in Chapter 1, “Cisco IP Telephony Solution Overview,” to choose the right deployment model.

Codec Selection

The selection of codec affects the amount of bandwidth that needs to be provisioned on the WAN links. Table E-2 provides a list of questions that you need to collect from the customer regarding its codec choice.

Table E-2. Codec Selection for LAN/WAN

No.

Question

Answer

1

What codec do you want to use?

□ LAN (G.711) □LAN (G.729) □LAN (G.723) □LAN (WideBand)

□WAN (G.711) □WAN (G.729) □WAN (G.723) □WAN (WideBand)

2

Do the VoIP calls require compressed RTP when being sent over the WAN?

□Yes

□No

Notes/Comments

You need to collect this information for each site. In case of a centralized call-processing deployment with multiple remote branch sites, you need to identify the type of codec to be used between the central site and each remote site.

Legacy Voice-Mail Integration Requirements

If the integration of CallManager with a legacy voice-mail system is a requirement, provide the information detailed in Table E-3.

Table E-3. Legacy Voice-Mail Integration Requirements

Site Name

Voice-Mail System Type, Version, Ports Configured

Number of Users

Integration Method with CallManager

Is Integration with Existing PBX Required?

Type of Gateway Required from Cisco

      
      
      

Notes/Comments

Some of the major supported integration methods are the following:

  • Skinny Client Control Protocol (SCCP) with Cisco Unity

  • Simplified Message Desk Interface (SMDI)-capable voice-mail system with CallManager through a Media Gateway Control Protocol (MGCP) gateway or with a VG-248

  • Cisco Digital PBX Adapter (DPA) integration for Octel or Nortel Meridian voice mail systems

  • CTI/TSP integration for other systems

After you collect the information about the legacy voice-mail system, you can determine the type of integration required to integrate the voice-mail system with the IPT system.

Legacy PBX Integration Requirements

If integration of CallManager with a legacy PBX system is a requirement, obtain the information detailed in Table E-4. Table E-4 shows some sample data that will help you to understand the type of information that needs to be gathered.

Table E-4. Legacy PBX Integration Requirements

Site Name

PBX Type/Software version

IPT Transformation—Integration/Full Migration?

IPT Users/PBX Users

Integration Trunk Type/Number of Trunks

Type of Gateway Required from Cisco/Software Version for Integration

Detroit

Definity

Integration

200 (IPT)/100 (PBX)

T1-PRI/1

WS-X-6608-T1/PCG00000

New York

Siemens

Full Migration

300 (IPT)/0 (PBX)

Not Applicable

Not Applicable

Notes/Comments

You can use the information collected from Table C-1 in Appendix C, “IPT Planning Phase: Telecom Infrastructure Analysis Questionnaire,” to fill out part of Table E-4. After you have the PBX details for each site, you can decide on the voice gateway model and the appropriate software version required on the voice gateway for successful integration. In case of integration with an IPT system, the existing trunks currently terminating on the PBX will be divided between the PBX and the voice gateway according to the user split ratio to preserve busy hour call attempts (BHCA).

For example, in Table E-4, for the Detroit site, the Definity PBX system needs to be integrated with the IPT system. Out of 300 users, 200 users will be migrated to the IPT system, and 100 users will be retained on the PBX system. Currently, the PBX has three T1-PRI trunks interfacing the PSTN. To preserve BHCA, during integration, two trunks will be moved to the voice gateway interfacing the PSTN.

You need to determine the approximate call volume between the users on the IPT system and the users remaining on the PBX system. This information is useful to size the trunks required between the PBX system and the voice gateway. The sample Detroit site information provided in Table E-4 uses one PRI trunk.

Sizing the CallManager Cluster

CallManager servers can be grouped together to form a cluster. A cluster can contain a maximum of eight CallManager servers doing the call processing. There can be other servers in the cluster to perform dedicated functions, such as a Publisher server that hosts a read/write database, a dedicated TFTP/DHCP server, a dedicated Music on Hold (MoH) server, and so forth. The publisher database is used as a single point of administration for the cluster configuration changes and to produce Call Detail Records (CDRs). The TFTP server facilitates the download of configuration files, device loads (operating code), and ring types.

The information in Table E-5 needs to be collected on a per-site basis to determine the number of clusters, the number of CallManager servers per cluster, and the type of hardware platform required per cluster.

Table E-5. CallManager Clustering Requirements

Site Name

IP Phones with Model Numbers

Voice-Mail Ports

TAPI/JTAPI Interfaces

Voice Gateways Include the Model and Number of DS0s

Conferencing, Transcoding, MTP, MoH Resources

      
      
      
      

Notes/Comments

A CallManager cluster consists of two or more CallManager servers. The number of devices that can be supported by a single CallManager server depends on the quantity of device types that need to be registered, such as IP Phones and gateways. To correctly size the CallManager cluster, you need to collect the information given in Table E-5 and follow the CallManager cluster-sizing guidelines given in Cisco IP Telephony Solution Reference Network Design (SRND) at http://www.cisco.com/go/srnd to decide on the hardware platform and number of servers in the cluster.

Branch Office IPT Requirements

When connecting regional offices (branch office) to the main site, Survivable Remote Site Telephony (SRST) or Cisco CallManager Express (CCME) features are used. Use Table E-6 to collect the information needed to determine whether SRST and Cisco CCME should be implemented. Table E-6 is applicable for CallManager deployment models 2, 3, or 4 (refer to Table E-1 for model definitions).

Table E-6. Requirements for SRST/CCME

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

                   
                   
                   
  1. Branch Office Name, Address

  2. Member of CallManager Cluster

  3. Bandwidth from the Hub, Type of Link (FR/Leased/ATM), Current Link Utilization

  4. Number of IP Phones Planned

  5. Number of IP Phones with Single Line Appearance

  6. Number of IP Phones with Multiple Line Appearances

  7. Current Branch Router Model, Memory, IOS Version

  8. Codec, G.711, G.729, G.723, and WideBand

  9. Direct Inward Dial (DID) or Calling Line ID (CLID) Requirements

  10. Supplementary Services Requirements

  11. Gateway Protocol, MGCP, or H.323

  12. Gateway Trunk Type, Number of Trunks

  13. Does This Branch Require Conferencing, Transcoding, MoH Resources? If Yes, Specify the Location of the Resources (Local/Remote)

  14. Number of Analog Ports Required

  15. Class of Restriction Requirements

  16. BHCA Across the WAN Links

  17. Number of Voice Mail Boxes

  18. Centralized/Local Voice Mail

  19. Recommended Branch Hardware, Software Upgrades

Notes/Comments

Information collected using Table E-6 is helpful in making the following determinations:

  • If a given branch site is being transformed as a standalone site using the CCME feature, that site will not be a part of the Cisco CallManager cluster. Hence, in Table E-6, for such sites, the second column is not applicable.

  • Collecting the information about current router hardware and software details is helpful in determining whether new hardware or software is required based on the number of phones connected in the branch site.

  • The choice of codec and the location of conferencing endpoints affect the amount of bandwidth required on the WAN links and the DSP resources required on the router.

  • BHCA affects the WAN bandwidth requirements.

  • The analog ports are typically used in branch sites to connect fax machines. These analog ports can also be used as backup lines to route calls to the PSTN if a primary connection fails.

Class of Restriction Requirements

Table E-7 gives typical class of restriction (CoR) definitions commonly deployed in telephony networks. You need to collect your choice of CoRs for the IP Phones.

Table E-7. Class of Restriction Requirements

Service Level

Allows Calls To

1 (Lobby phones)

All IP Phones; 911 and other services such as 411, 611, local calls (7- or 10-digit dialing based on the site); toll-free numbers; voice mail; block 900 numbers; access to all other customer locations; access to toll calls from other locations

2 (Employee phones)

Level 1 access; plus long-distance calls

3 (Executives phone)

Level 2 access; plus international calling

Notes/Comments

The CoR feature is enabled by configuring partitions and calling search spaces (CSSs) in CallManager. By configuring different levels of CSS for the IP Phones or for the directory numbers, you can provide different levels of access to the PSTN from IP Phones.

Call-Routing and Dial Plan Requirements

Gathering call-routing and dial plan requirements is an important step in the IPT design phase. The requirements collected here dictate how to plan for route patterns, partitions, route groups, and route list designs in CallManager.

The first step is to gather the information on the existing numbering plan, as shown in Tables E-8 through E-10. If you have collected this information earlier, you can use that information; otherwise, gather this information before starting the dial plan design on the CallManager.

Table E-8. Existing Numbering Plan

Site Name

On-Net Site Access Code

No. of Digits in Station Numbering Plan

DID Ranges

Station Directory Numbering Ranges

Telephony Feature Pilot Numbers

Site-Level DID

No. of CoRs Required

        
        
        

Table E-9. Dial Plan Requirements

No.

Question

Answer

1

Are there any conflicts with current legacy numbering ranges? If yes, identify them and work on the dial plan to resolve them.

□Yes

□No

2

Do you have any conflicts of dialing plans with other locations?

When you are migrating from a distributed PBX or key system (A key system is a multiline phone system with basic features such as conferencing, transfer, or intercom. You can think of the key system as a scaled down version of the PBX system.) deployment to a centralized IPT deployment, you need to identify how many digits are used in each site for local dialing. If there is a conflict in the numbering plans between the sites, you should consider increasing the number of digits required to avoid the overlapped numbering ranges.

□Yes

□No

3

Do you want to retain the existing dialing behavior?

□Yes

□No

4

Is digit translation needed? (Example: Prefix digits, discard digits, append digits, changing the calling party/called party number and so on.)

□Yes

□No

Specify:

5

Do you have a toll-free number requirement?

□Yes

□No

Specify:

Table E-10. Call-Routing Requirements for Site 1

No.

Type of Calls

Call-Routing Preferences, in Order of Priority

1

Local

  1. Local gateway

  2. Central site gateway via IP WAN

Emergency

Local gateways only

Long distance

  1. Local gateway

  2. Central site gateway via IP WAN

International

  1. Central site gateway via IP WAN

  2. Local gateway

  3. Remote site 2 gateways

Toll bypass

  1. Central site gateway via IP WAN

  2. Site 2 gateways

  3. Local gateway

To international offices

  1. Central site gateway via IP WAN

  2. Local gateway

Notes/Comments

List the DID requirements. DID is a PBX or Centrex feature that permits outside calls to be placed directly to a station line without use of an operator.

Sizing the PSTN/Gateway Trunks

If you are sizing the number of PSTN/gateway trunks for a new deployment or are planning to estimate the number of PSTN/gateway trunks required, use the Erlang-B calculator, as discussed in Chapter 6. The information requested in Table E-11 is required to estimate the number of trunks. In an existing network, you can obtain this information from the statistics available in the PBX.

Table E-11. Sizing the PSTN Trunks

No.

Question

Answer

1

What is the BHCA?

BHCA:

2

What is the AHT?

AHT:

3

What is the BHT?

BHT = (BHCA × AHT / 3600):

4

What is the GoS?

GoS:

Notes/Comments

The following list explains the terms used in Table E-11:

  • Busy hour call attempts (BHCA)—Number of calls attempted during the busiest interval. This could be any interval, such as the “busy hour,” a half-hour interval, or any other interval.

  • Average handle time (AHT)—The average duration (talk time) of the call.

  • Busy hour traffic (BHT)—Measure of the traffic load during your network’s busiest hour, which represents the maximum traffic load that your network must support.

  • Grade of service (GoS)—The percent of calls that will receive busy tone (no trunks available on gateway/PSTN) during the busy hour (also called percent blockage). A 1-percent blockage means 99 percent of all calls from the PSTN attempted during the interval will have a trunk port available on the gateway/PSTN to reach the user.

Power Requirements (Per Site/Per Switch Specific)

This section describes the questions that the customer needs to answer related to its network’s power infrastructure. This information is important to select the correct types of switches deployed in the IPT network and to design a highly available IPT network. Tables E-12 and E-13 help you to determine your strategy in providing power to IP Phones and whether the closet switches require additional power to provide the inline power to IP Phones.

Table E-12. Power Requirements

No.

Question

Answer

1

How do you want to provide the power to the IP Phones?

□Inline

□Local power

□External power panel

2

If you are using the inline power option, provide the information requested in Table E-13.

 

Table E-13. Evaluating Inline Power Requirements

No.

Site Name, Bldg., Floor

Switch Model, Number of Power Supplies, Wattage, Power Type

Phones Types, Count

Backup Power Available? Yes/No

1

Site 1, Bldg. J, 3rd Floor

Cat 6506, 2 power supplies, 2200W, AC

7960, 50

7940, 10

7935, 5

 

2

    
     
     

Call Admission Control Considerations

While designing the IPT network, you need to collect the traffic patterns to better engineer the traffic flows. The information listed in Table E-14 is needed for call admission control (CAC) and related design considerations for each site.

Table E-14. CAC Design

No.

Question

Answer

1

Has a review been done to analyze the on-net call volume traffic among the sites that are going to be served by the same CallManager cluster?

□Yes

□No

2

Does your IPT deployment follow a hub-and-spoke topology? (Applicable for models 2, 3, 4; refer to Table E-1.)

For the CAC mechanism to function properly, the WAN topology should follow the hub-and-spoke model.

□Yes

□No

3

What type of CAC mechanism will be deployed?

□CallManager locations CAC

□Gatekeeper CAC

4

If deploying gatekeeper CAC, how many CallManager clusters are interconnected via the gatekeeper?

Number of clusters

______________________________

5

What is the estimated number of calls per second (CPS) that the gatekeeper needs to process?

This determines the gatekeeper hardware to be deployed.

CPS

______________________________

6

What is the number of gatekeepers required in the network and gatekeeper network design? (Identify the requirements for the directory gatekeeper.)

Number of Gatekeepers

______________________________

7

Which type of gatekeeper deployment will be used?

□HSRP

□Cluster

Table E-15 lists the on-net call requirements and call volumes from remote sites to central sites.

Table E-15. CAC Bandwidth Values for WAN Links

No.

On-Net Call Path

On-Net Calls Allowed

1

Central site – Site 1

Voice

□G.729 □G.711 □G.723 □Other _______

Number of calls ___

  

Fax

 
   

□ G.711

   

□ Other _______ Number of calls ___

  

MoH

□G.729 □G.711

   

□ Other _______

   

Number of calls ___

  

RTP compression?

□Yes □No

  

Does this site use location CAC or gatekeeper CAC?

□Location CAC □Gatekeeper CAC

  

Total bandwidth that needs to be reserved for this site

 
   

_______ kbps

Notes/Comments

When you are sizing the WAN bandwidth and the CAC, you need to determine the number of calls that traverse the WAN links. You need to take into consideration the fax and MoH streams in addition to voice calls. The choice of codec for each type of call also has an effect on the total bandwidth required on the WAN links.

Corporate Directory Requirements

Two requirements exist when discussing the corporate directory and CallManager:

  • Directory access

  • Directory integration

Table E-16 helps you to gather these requirements and design your customer’s IPT network. After collecting the basic information from Table E-16, if your client’s network is going to include directory access, obtain the information requested in Table E-17. For corporate directory integration, obtain the information requested in Table E-18.

Table E-16. Information About Existing Corporate Directory

No.

Question

Answer

1

If your enterprise has a corporate directory deployed, what type of corporate directory is it?

□AD □Netscape Specify the versions of the directory:

(Example: AD 2000, AD 2003, Netscape 4.x, and so on.)

2

Do you require corporate directory access from IP Phones or integration of CallManager with the corporate directory?

□Access

□Integration

3

Do you have full redundancy for your directory?

□Yes

□No

Table E-17. Directory Access Requirements

No.

Question

Answer

1

Do you have a server on which to install the Cisco IP Phone Services SDK?

□Yes

□No

2

What are the configuration details of the IP Phone service server on which the SDK is installed?

OS version:

Service pack level:

DNS name:

 

The Cisco IP Phone Services SDK runs only on a Microsoft Windows 2000 or 2003 platform and uses ASP (Active Server Pages) scripts. If you plan to use any OS other than these, you have to develop your own scripts.

IP Addr.:

3

What URL needs to be configured on the CallManager to provide the directory access to the IP Phones?

URL

Example:

http://<IP address of IP Phone services server>/ldapsearch/ldapsearch.asp

 

This depends on how you have configured the virtual directories on the IIS on the IP Phone service server.

 

4

What is the DNS name/IP address of the corporate directory server that IP Phones can access to get the directory list?

DNS name/IP address:

5

What is the username and password required to access the directory for lookup?

Username Password

  

Example: Cn=diruser, ou=users,dc=Cisco,dc=com

6

What is the user search base?

User search base:

  

Example: ou=users, dc=Cisco,dc=com

Table E-18. Directory Integration Requirements

No.

Question

Answer

1

Who are the contacts in your corporate directory team?

Name: Role: Phone: E-mail:

Name: Role: Phone: E-mail:

Name: Role: Phone: E-mail:

2

How many CallManager clusters exist in your network?

Number of CallManager Clusters:

3

Do all the CallManager clusters run the same version of CallManager, or do they run different versions? If different, list them.

CallManager Versions:

4

Are any other Cisco telephony applications deployed or planned to be deployed in the network?

CCC CER PA CRS Unity

Version: Version: Version: Version: Version:

5

Do any other applications currently use your directory?

App. 1: App. 2: App. 3: App. 4:

Details:

6

The following type of information needs to be obtained from the directory team for the existing directory architecture. The questions to ask depend on the directory being used. For example, if AD is deployed, you need to ask the following regarding the AD architecture:

What is the number of forests?

What is the number of domains?

Where are domains located?

Do you have multiple sites?

Do you have multiple name spaces?

What are the replication latency times?

Do you have users created under multiple OUs or under a single OU?

Attach the architecture diagrams, documents that describe the directory deployment.

7

Does the corporate directory team understand how the CallManager directory integration works? Do they have all the information about schema changes and possible increases in the size of the directory database?

If the answer is no, do not proceed. Go back and clear up all the concerns that the directory team has regarding this whole process.

□Yes

□No

8

Who has the schema master right to modify the schema on the directory?

Name: Role: Phone: E-mail:

9

Do you want to use the account that has schema master permission for CallManager to use, or do you want to give a separate account with only required permissions?

 

10

If you are creating a separate CCMdiruser account, what are the account name, password, and permissions given to this user?

Username (FQDN):

Password:

Permissions:

11

What is the IP address/DNS name of the schema master, and what is the LDAP port number?

IP Address:

LDAP port

12

Where do you want the Cisco directory tree to be created in your directory structure? (This is referred to as the Cisco Configuration DN in CallManager.)

Example:

OU=CISCOCCM_DIT,dc=Cisco,dc=com

13

CallManager requires that a few user accounts be created in the directory for its operations. What is the user creation base?

Example:

ou=users, dc=Cisco,dc=com

Directory Access Requirements

Meet with the corporate directory team to obtain the information requested in Table E-17. Directory access refers to when a user presses the Directory button on the IP Phone, the LDAP queries are sent to an external server hosting the Directory Lookup service and then forwarded to the corporate directory server.

Notes/Comments

Directory access is simple compared to directory integration. Refer to Chapter 8, “Implementation,” for instructions on implementing directory access on IP Phones using Microsoft Active Directory as the corporate directory.

Directory Integration

Integrating the CallManager with an external corporate directory such as Microsoft AD or Netscape Directory Server stores all the CallManager-related information in the corporate directory rather than in the CallManager default DC directory. Collect the information requested in Table E-18 to understand the requirements of CallManager integration with an existing corporate directory.

Notes/Comments

When you are proposing CallManager directory integration with a corporate directory, you must inform the corporate directory team about the schema changes that will be done on the corporate directory and address all of their questions and concerns before moving forward with directory integration.

Conferencing, Transcoding, and MTP Requirements for Central Sites

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.

Table E-19. Conference, Transcoding, and MTP 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?

□Yes

□No

List of codecs:

4

Do you plan to deploy applications such as CRS and Unity in the network?

□Yes

□No

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?

□Central

□Remote

□Distributed

6

Do you want to use the conferencing, transcoding, and MTP resources on the CallManager servers that are part of the cluster?

□Yes

□No

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?

□Yes

□No

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?

□Hardware

□Software

□Both

Fill in table E-20 with details.

9

Do you have any non–Cisco H.323 endpoints that do not support Empty capabilities set?

Yes

No

Specify the endpoints and their locations:

Notes/Comments

List the site-wide requirements for conferencing, transcoding, and MTP. To assist you, Table E-20 shows examples of the XYZ, Inc. network requirements.

Table E-20. XYZ Conferencing, Transcoding, and MoH 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

Music on Hold Requirements

Collect the information requested in Table E-21 to determine the MoH requirements for the planned IPT network.

Table E-21. MoH Requirements

No.

Question

Answer

1

What is the total number of IP Phones deployed in the cluster?

Number of IP Phones:

2

Is a dedicated MoH server or a collocated MoH server required?

This depends on the size of the network.

□Collocated

□Dedicated

3

Do you plan to use a fixed audio source?

Using a fixed audio source allows the stream to be played from CD.

□Yes

□No

Name of the server on which the sound card will be installed:

4

How many streams do you plan to use?

This is the number of different audio files.

Number of streams:

5

How important is redundancy for the MoH server?

If the MoH server fails, users hear tones instead of music.

□Redundancy

□No redundancy

6

Do you have a multisite deployment model? If yes, do you want MoH to be streamed from the central site?

□Yes □No

□Yes □No

7

Do you have multiple codecs configured in your network (for example, G711 for LAN or G729 for WAN)?

□Yes

□No

List the codecs used:

8

Is multicast enabled and supported on your network? If not, do you plan to support multicast on your network in the future?

□Yes

□No

9

Is there any requirement to play certain music for a particular group and different music for others?

For example, marketing might require a particular stream to be played to callers during the hold, engineering might require a different stream, and so on. If you have such requirements, you can configure different audio sources for these groups.

□Yes

□No

Specify the number of different groups that require different streams:

10

Do you want MoH to be streamed to all the sites? If not, list which sites need MoH, which sites use a local MoH feature on the routers, and which sites use the Tone on Hold feature.

Provide the attachment.

11

Do you want to enable the multicast MoH on the MoH server? If yes, list the range of multicast group addresses that can be used by the MoH server to assign it to the audio streams.

Ensure that these addresses are unique and not already in use in the network.

□Yes

□No

Range of multicast addresses:

Notes/Comments

MoH, as the name implies, provides music to callers when they are put on hold. There are various ways you can provide MoH to users. The information gathered by using Table E-21 will assist you in determining the organizational needs in providing MoH and assist you in designing the MoH services in the IPT network.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset