"Old School" MOH

[buthead]

Greetings Avaya Guru's
I need your help, but I'm going to provide some backstory, so bear with me. I'm an old Nortel guy who has recently upgraded an 81C to a Rls.7 Avaya. I run a multitenant environment. I've got multiple announcements for multiple tenants, on the VAL board. That's all good. I've got 1 tenant that does not like the fact that announcements always start at the "beginning" when put on hold. Per Avaya, anything on a VAL board, will always start at the beginning of the recording. Per them, I need to use an external music source, tie it to a 711 card and all will be good. I've done that but I cant get the MOH to play. I've built a new analog MOH group and assigned it to the music source, but I hear nothing. I've built the route with an extension and when I dial it, I hear my source, but no MOH. I just can't figure out what I'm doing wrong. My friends at Avaya will help me, but they say it is a billable charge. Nice guys, 50K in maintenance cost and you want to charge me??? Team, I'm in need of help, I have no problem paying for help. Avaya tells me I need a 909 adapter to interface my source to the 711. Really??? a 600 ohm input is what I'm providing, why the 909. Answer...thats what the manual says. I would rather give my money to the great people on this list. Please give me an option.
Respectfully,
Buthead

 

[DAVIDPAYNE]

You may want to post some of your config, like you Music Source, and announcements section for this item. But you are in Multi tenant, is this music source in the correct Tenant, locations, etc.?

 

[phoneguy55]

Setting your MOH announcement to 'integ-mus' should be an option.


integ-mus
The integ-mus (integrated-music) announcement type is the same as the integ-rep type except
that the Q field is set to b to provide a continuous repeating barge-in operation. This type is
typically used to provide music on delay or on hold.
Any announcement that is stored on an announcement source can play through any port on
the announcement source. Any announcement, except those announcements that are
administered for “barge-in,” can play simultaneously through multiple ports. All 16 ports can
play the same announcement at the same time.
You must set the Q field to y on the Announcements/Audio Sources screen for each extension
that you want to queue for integrated announcements. Integrated announcements queue only
when all ports on the announcement source that contains the announcement are busy. The
same queuing pool is used for all announcement sources. The system controls the
announcement queue length for integrated announcements, but you must set the queue length
for analog or aux-trunk announcements.

 

[buthead]

David,
I should have mentioned that the tenant is currently getting treatment off of the VAL. I'm just trying to replace it with an external source. I've built an extension, 1013, but when I change the music source to that, I get nothing. I can call the extension and hear music and ring generator from the card. I tried assigning another port on the card to an analog music group, then assigned the group to the source and still no MOH. I've attached a few screenshots if that helps.

MUSIC SOURCES
Source No. Type Source Description
1: music Type: ext 1097 Arena MOH
2: music Type: ext 1098 Bulls MOH
3: music Type: ext 1012 McDonaugh's MOH

ANNOUNCEMENTS/AUDIO SOURCES
Announcement Num of
Extension Type Name Source Sources
1000 integrated 1000_L01_Att_Vec_Main 001V9 1
1001 integrated 1001_L01_Bulls_Main 001V9 1
1002 integrated 1002_L01_BlackHawks_Main 001V9 1
1010 integrated 1010_L01_PleaseHold_AttVec 001V9 1
1011 integrated 1011_L01_PleaseConHold_Attv 001V9 1
1012 integ-mus Blackhawks_mono 001V9 1
1013 analog-fd LOOP 001V802 1
1096 integ-mus 1096 001V9 1
1097 integ-mus 1097_L01_Arena_MOH 001V9 1
1098 integ-mus 1098_L01_Bulls_MOH 001V9 1

MOH GROUP 1
Group Name: test
MOH SOURCE LOCATION
1: 001V801 16: 31: 46: 61:
2: 17: 32: 47: 62:
3: 18: 33: 48: 63:
4: 19: 34: 49: 64:
5: 20: 35: 50: 65:
ATTENDANT CONSOLE 6
Type: 302 Name: One-X Att Blackhawks
Extension: 2906 Group: 3 Auto Answer: none
Console Type: principal TN: 102 Data Module? n
Port: S00108 COR: 6 Disp Client Redir? n

 

[buthead]

Phoneguy,
That's the way I understood it to work. To me barge in should "drop" you into a RAN at any point. This is my existing MOH. When callers are presented music, it always plays from the beginning of the recording.

Extension: 1012 COR: 90
Annc Name: Blackhawks_mono TN: 1
Annc Type: integ-mus Queue? b
Source: 001V9
Protected? n Rate: 64

 

[PhonesAllDay]

There is a music on hold FAQ:

https://www.tek-tips.com/faqs.cfm?fid=6472

If you need any of that old school MOH equipment I have some I can sell you. Cheap! Cheap!

 

[kyle555]

Hey! No soliciting is allowed on this website. You can only sell solutions to old school music on hold problems if you include old school music on hold!

https://archive.org/details/attentionkmartshoppers

 

[AvayaTier3]

Avaya Aura Communication
Manager Screen Reference
03-602878
Release 5.2
May 2009
Issue 1.0

b(argein) Enter b to set up barge-in if the Type field is integrated, integ-rep or
aux-trunk. When Type is integ-mus, this field defaults to b. Callers are
connected to the announcement at any time while it is playing.
Note: The same non-barge-in announcement can be played through
more than one port (or all ports) of an integrated circuit pack. The initial
request to play an announcement selects an available port on the board
on which the announcement resides. If there are additional requests to
play the announcement while it is playing on another port(s), another port
is selected. If all ports are busy, new requests to play announcements go
to the integrated announcement system queue (Q field must be y).
Otherwise, the request to play is denied, and processing continues
without the caller hearing the announcement. When a port becomes
available, all queued calls (up to the platform "calls connected" limit) are
connected at the same time to hear the announcement play from the
beginning.
A barge-in announcement starts playing when first requested and
continues playing through a port, repeating until there are no more
requests. Call processing simultaneously connects calls to the playing
barge-in announcement. Each call remains connected until the
requesting feature operation removes the call (for example, wait step
times out). Barge-in type announcements never select another port to
play the same announcement once it is playing on a specific port.

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

bsh

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