Communication Manager (CM) is able to supply music to callers. This is primarily useful when callers are placed on hold, but can also be needed by vectors queueing callers for a specific skill/hunt-group.

There are several ways that CM can source music, but the most popular method now is from an integ-mus announcement (which is a music file saved as a properly encoded wav, stored on an announcement board). See Communication Manager Announcements.

display announcement 3441

                       ANNOUNCEMENTS/AUDIO SOURCES

  Extension: 3441                            COR: 1
  Annc Name: moh_default                      TN: 1
  Annc Type: integ-mus                     Queue? b
Group/Board: G1
  Protected? n                              Rate: 64

I recommend that integ-mus announcements be assigned to an audio-group that includes as many announcement-boards as possible, so that calls do not consume unnecessary WAN/trunking resources simply to obtain music:

display audio-group 1                                           Page   1 of   5
                                AUDIO GROUP 1

                          Group Name: Everywhere

AUDIO SOURCE LOCATION
  1: 003V9    16: 014V9    31:          46:          61:          76:
[...]

After the announcement has been created (and the file has been download onto every relevant announcement board), create a music-source for it:

display music-sources                                           Page   1 of  17
                                   MUSIC SOURCES

      Source No.   Type   Source                           Description

          1:       music  Type: ext   3441                 MOH Default
[...]

As previously mentioned, CM can source music via methods other than integ-mus announcements. When defining your music-source, you can use “ext” for an integ-mus announcement extension, “group” for a moh-analog-group, or “port” for a fully-qualified port number. Using group or port is beyond the scope of this document.

Hold-music is defined on a system basis (if tenant partition is disabled), on a station basis (if tenant partitioning is disabled and special-application 8888 (SA8888) is enabled), or on a tenant basis (if tenant partitioning is enabled). Determine whether tenant partitioning is enabled:

display system-parameters customer-options                      Page   5 of  11
                                OPTIONAL FEATURES
[...]
          Personal Station Access (PSA)? y               Tenant Partitioning? y
[...]

If tenant partitioning is enabled (as is the case for most large CM systems), you administer its music source in tenant configuration:

display tenant 1                                                Page   1 of   4

                           TENANT 1
[...]
             Music Source: 1
[...]

Multiple tenants may use the same music source; you need not define a separate music source for each tenant (but may do so, when the music needs to be different between tenants).

If tenant partitioning is not enabled, you administer the music source via “system-parameters features” (without SA8888) or “station” (with SA8888).

Music source changes take effect beginning with subsequent requests for music - in-progress requests for music will continue to use the old music source until the port is released.