PP

NOPE. YOU WILL NEED A MUSIC SOURCE IN NETWORK 0 LOOPS 0-15 AND ONE IN NETWORK 1 LOOPS 16-31

hhallett

Thanks, but this much I am already aware of.

I want to be able to add a universal trunk card to network group 2, but to do so I need a PE shelf in Group 2. That's why I'm hoping I can do it by splitting a superloop in the way I described.

I just need to know if this can actually be done and, if so, how to do it without giving myself more headaches.

gei_spot

You will not be able to do that, because of the way the cables (switch tails) are config'd. Unless someone eles has done this B4, I'd say that you may be putting in some OT to balance the switch. A quik fix would be move a ALC/DLC out of the group that you need to put the trk card in. Try and find one that doesn't have a lot of phones prog on it, that way you are not moving all 16 TNs

slagburn

I think the title of this thread is throwing people off, it should say 'Splitting an IPE shelf across Network Groups' since the shelf is splitting and not the superloop.


From what I saw on the original MOH thread the only thing that is on group 1 of his switch are T-1s, I didn't see any place to move a card from / to that would've fixed anything.

To the original questions...

1) I've been told no by more than one person however I can't find any documentation in engineering manuals to support this. I would think that if it were a problem it would be documented somewhere in the IPE segmentation documents but if it is I couldn't find it. This morning I was able to split a controller between network groups in software without any hang ups however I didn't have enough cables to fully test it.

SUPL SUPT SLOT XPEC0 XPEC1
008 STD LEFT 01 0 1 -- - -
056 STD LEFT 01 2 3 -- - -


2) I don't really know the right way to do it since the last one I took part in ended up getting corrupted from the several 1000 sets we moved. (Not my idea) Some things to consider are if you are using a telemanagment system that relies heavily on TN information to assign a BAC i.e. Avotus. When we manually moved the stations to new TNs the BACs never updated and we lost a lot of billing info while someone had to manually modify the BAC database. I'm not familiar with any of the other management systems but I do know that it's important to keep that aspect in mind. If I had to do it again I would let the telemanagement folks do an order to out the sets and rebuild them back on the new TNs.

gei_spot

[quote="slagburn"] I think the title of this thread is throwing people off, it should say 'Splitting an IPE shelf across Network Groups' since the shelf is splitting and not the superloop.

Good catch Slag... really didn't read the original post. Have been having some issuse at the office and haven't had time to dig into the forum yet I think that will work, but still he's not going to get away without some serious OT




2) I don't really know the right way to do it since the last one I took part in ended up getting corrupted from the several 1000 sets we moved. (Not my idea) Some things to consider are if you are using a telemanagment system that relies heavily on TN information to assign a BAC i.e. Avotus. When we manually moved the stations to new TNs the BACs never updated and we lost a lot of billing info while someone had to manually modify the BAC database. I'm not familiar with any of the other management systems but I do know that it's important to keep that aspect in mind. If I had to do it again I would let the telemanagement folks do an order to out the sets and rebuild them back on the new TNs.

Sorry you had to go through this.. sounds like it was the making of a

[b]BAAAD week

slagburn

lol NMP... Not My Problem.

The two senior techs who moved the 1000+ phones got to deal with the fall out. I was just the cable swinger jumper guy... of course those two techs both told me on numerous occasions not to move a lot of sets at once before this happend.

iceman

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:

fizzywig

slagburn,

I have all the packages required for MusBrd, I have 20 conn not in use. I have one music route and are currently using enhanced music I would like to turn on MusBrd. I thought I understood the NTP to say that for every music conn I can broadcast to 64 callers at a time. So, with 20 conn I should be able to broadcast to 1280 callers at the same time, right? Or is it in relation to the # of conn I have, being 20 I can bradcast to 20 callers?

I have recieved different answeres on the subjuct and hope you can clarify for me. Sorry I'm sure it is not an easy question.

Clear as mud....