PBX Info :: Your Free PBX, PABX and Telephone Information Resource - View Single Post - Splitting a Superloop Across Network Groups
View Single Post
Old 02-27-2004, 09:21 AM   #8 (permalink)
iceman
Junior Member

Activity Longevity
0/20 20/20
Today Posts
0/0 ssssssss7
Location: Keflavik Iceland
Rep Power: 0iceman is on a distinguished road
Send a message via ICQ to iceman
Call Forward Button

If I understand you correctly your main problem right now is MOH and not being able to get MOH cross groups ?


Well if that is your problem then look at this.

Music Broadcast feature expands existing Music functionality. This
feature provides the following enhancements:

• Broadcast Capabilities
• Incremental Software Management limit
• Traffic Study Option
Broadcast Capabilities

Existing Conference-based Music features require that each Music trunk be
assigned to a Music route and to a Conference loop. Incoming callers are
bridged into a listen-only conference and provided with music while on call
hold or call waiting in an Automatic Call Distribution (ACD) environment.
The existing Conference-based Music features support intra-group music
only. Therefore, each network group must be provided with its own Music
trunk.
The Music Broadcast feature allows the Meridian 1 system to broadcast
music to several parties at one time via a single Music Broadcast trunk port.
This feature supports Music on Hold (MOH). Music is now delivered via X11
software; hence, Conference hardware is not required. It is no longer
necessary to share Conference resources with Conference features, such as
Conference and Group Call. Music Broadcast supports both intra-group and
inter-group music. Therefore, a Music trunk in each network group is not
required.


Feature packaging

Music Broadcast (MUSBRD) is package 328. The following packages are
also required to provide Music Broadcast capability:
• Music (MUS) package 44
• Recorded Announcement (RAN) package 7
To provide Music Broadcast capability to Enhanced Music (EMUS) features,
the Enhanced Music (EMUS) package 119 is also required.


Feature implementation
Task summary list

The following is a summary of the tasks in this section:
1 LD 16 – Change an existing non-broadcasting Music route to a
broadcasting Music route.
2 LD 16 – Enable Conference-based Music route.
3 LD 14 – Configure Conference-based Music trunks.

It is a lenghtly answer but I did not type it all "cut&past " is my method when I can.


I know this may not help because you might be missing packages but if you got them this is by far the easies way of fixing your problem.

:wink:
iceman is offline   sendpm.gif Reply With Quote