Diff MOH for phones, based on network region it sits in.

[tweege]

have seen several posts in regards to this issue, but not anything concrete. avayas docs dont seem to address it directly either.

is it possible to load an announcement file onto a media gateway that is then used for MOH for any phones within the same network region as that GW?

i can get the announcement loaded on the the GW, and programmed into the CM. i can add the GW module V9 as a source in a cm audio group. i cannot seem to make an entry in the CM MOH group for the announcement in the GW. it wants gateway(1-250):module(V1-V9):circuit(01-31); i get the gateway and module entries, but where does the circuit entry come from? i thought it would be the id for the announcement in the GW, but it looks to be 101...too many digits.

or, am i chasing my tail around and this isnt even possible?

using cm 5.2.1 with g250 and g350 media gateways.

thanks!

 

[Wanebo]

I don't believe t would be east to achieve using NR's. The preferred way to do it would be to have them as different tenants.

 

[ZeroZeroOne]

I think you want the Music Source, not MOH Group. You can enter the extension of the Announcement. MOH Analog groups are for external devices at connect via an analog port.

change music-sources                                            Page   1 of  17
                                   MUSIC SOURCES

      Source No.   Type   Source                           Description

          1:       music  Type: ext   80399                MOH
          2:       none
          3:       none

 

[AvayaTier3]

Locally Sourced Announcements and Music

The Locally Sourced Announcement and Music feature is based on the concept of
audio source groups. This feature allows announcement and music sources to be
located on any or all of the Voice Announcement with LAN (VAL) circuit packs or
on virtual VALs (v VAL) in a media gateway. The VAL or v VAL circuit packs are
assigned to an audio group. The audio group is then assigned to an announcement
or audio extension as a group sourced location. When an incoming call requires
an announcement or music-on-hold, the audio source that is closest to the
incoming call trunk plays the file that is assigned to the announcement
extension.

For more information, see the feature description on "Locally Sourced
Announcements and Music."
Administering Avaya Aura Communication Manager

03-300509
Issue 5.0
Release 5.2
May 2009


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AvayaTier3]

Different music for different PNs:
Two sites, PN1 Main Server location and PN2 ESS / LSP Server
On Site A "change system-parameters features"
Music/Tone on Hold: music Type: group 1

change moh-analog-group 1                                       Page   1 of   4
                                  MOH GROUP 1
                          Group Name: Music-on-Hold
MOH SOURCE LOCATION
  1: 01C0806     16:             31:             46:             61:
  2: 02A0805     17:             32:             47:             62:

--------------------------------------------------------------------------------
PN1 users hear the music from 01C0806
PN2 users hear the music from 02A0805 (the nearest music source).
================================================================================
Audio groups can be mixed.

Same boards or different boards can be used in different audio groups.
announcements can be in one group or on one board. The .wav for each should
be copied to the board or boards that the announcement programming points to.

.wav files on boards that are not pointed to by an announcment extension or
group should be removed from the valboard. This makes more room on the valboard
for what is being used.

An audio group that is composed of 4 boards, needs a copy of the .wav
file for each announcement extension on each of the 4 boards.

Audio Group 1         Audio Group 2
01c08                    1c08
01c10                    1c10
02b10
03d08

1232 HR.wav      1c10
1233 open.wav    1c08
1234 greet.wav   G1
1235 hold.wav    G1
1236 holiday.wav G1
1237 agent.wav   G1
1238 music.wav   G2
1239 ad.wav      G2

All 4 of the (G1) .wav files above should be copied to each of the val
boards and 1233 only needs to be copied to 1c08 and 1232 only needs to
be copied to 1c10

The 2 (G2) .wav files above only need to be copied to 1c08 and 1c10
--------------------------------------------------------------------------------
Locally Sourced Announcements and Music
The Locally Sourced Announcement and Music feature is based on the concept of
audio source groups. This feature allows announcement and music sources to be
located on any or all of the Voice Announcement with LAN (VAL) circuit packs or
on virtual VALs (v VAL) in a media gateway. The VAL or v VAL circuit packs are
assigned to an audio group. The audio group is then assigned to an announcement
or audio extension as a group sourced location. When an incoming call requires
an announcement or music-on-hold, the audio source that is closest to the
incoming call trunk plays the file that is assigned to the announcement
extension.

For more information, see the feature description on "Locally Sourced
Announcements and Music."

Administering Avaya Aura Communication Manager
03-300509
Issue 5.0
Release 5.2
May 2009
--------------------------------------------------------------------------------
Detailed description of Locally Sourced Announcements and Music
This section provides a detailed description of the Locally Sourced
Announcements and Music feature. This feature is available with Communication
Manager Release 3.0.

The Locally Sourced Announcement and Music feature differs from the
Announcement feature and the Music-on-Hold feature. The Announcement and
Music-on-Hold features are single-sourced audio while the Locally Sourced
feature is group-sourced audio. Locally Sourced Announcement and Music is based
on groups of audio sources. Audio sources are assigned either to an audio group
or a music-on-hold group.
Audio groups are made up of multiple sources of the same announcement or music.
These audio sources can be located on any or all of the Voice Announcement with
LAN (VAL) TN2501AP boards or on virtual VALs (vVAL) in a media gateway. The VAL
or vVAL boards are assigned to an audio group. The audio group is then assigned
to an announcement or audio extension as a group sourced location.
Announcement or music recordings are saved as wav file types. Each recording
must be saved manually onto the VAL or vVAL boards the same way as
single-sourced announcements using an FTP program or VAL Manager. Each recording
has the same file name within an audio group. The audio group can contain
announcements and music.

A music-on-hold group is a collection of externally connected and continuously
playing music sources. An example of a music-on-hold source is a radio station
connected to a media gateway using an analog station port.
Multiple music-on-hold sources can be used in the same system.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]