We are playing around with moving to a VAL based MOH source. Everything seems to be running fine except for one small inconvenience. Whenever we break MOH in a vector for an announcement or a staffed skill check and then return to "wait hearing music", the music is restarted. Is there any way for the MOH to be looped and the caller just to hear whatever part of the loop is playing during the time they are waiting?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Music On Hold during vector wait step
- Thread starter gordopa1
- Start date
- Thread starter
- #2
Are you sure your music extension's announcement type is set to "integ-mus"? Sounds like you have it defined as "integrated".
change announcement 890204 Page 1 of 1
ANNOUNCEMENTS/AUDIO SOURCES
Extension: 89.02.04 COR: 1
Annc Name: mohloop TN: 1
Type: integ-mus Queue? b
Group/Board: 001V9
Protected? n Rate: 64
-CL
change announcement 890204 Page 1 of 1
ANNOUNCEMENTS/AUDIO SOURCES
Extension: 89.02.04 COR: 1
Annc Name: mohloop TN: 1
Type: integ-mus Queue? b
Group/Board: 001V9
Protected? n Rate: 64
-CL
- Thread starter
- #4
AvayaTier3
Technical User
All G700 Media Gateways in the system can be assigned as VAL sources, for a
maximum of 250 G700 VAL sources in a large S8700 Series media server
configuration also with up to 10 TN2501 VAL boards, providing an ultimate
capacity of 260 sources for the Avaya S8700 Series servers. TN2501 has 31
playback ports (with 60 minutes of storage capacity) and each G700 VAL
source has 15 playback ports (with 20 minutes storage capacity). Initially each
caller that is to hear a non-barge-in announcement on that source is connected
to an available port until each port has one caller connected. Initially 31
callers can be hearing an announcement from a single
TN2501 board (15 with a G700 VAL source). The same announcement can be playing
from multiple ports, each starting at a different time. Once all ports are busy
playing announcements, subsequent callers that are to hear an announcement
residing on that board/source are queued for that source.
Communication Manager queue size over all integrated announcement
sources is 4,000 callers (S8700 Series/S8300 media servers). When a port becomes
available, all callers (up to 1,000) waiting in the queue for a specific
announcement on that source are connected to the available port to hear the
announcement play from the beginning on a first-in, first-out basis.
At any given time you can have as many as 1,000 callers hearing the same
announcement on a given port of a board/source, yielding a (theoretical,
system-wide) capacity of 31,000 callers connected to a VAL board (or 15,000
callers connected to a G700 Media Gateway virtual VAL source).
Factor in barge-in announcements which continuously play from a single port
(that can have as many as 1,000 callers connected at the same), and this
provides a very, very large capacity for playing announcements.
The measurements announcements commands can be used to monitor the system and
help determine burst conditions, allowing for better load balancing of the
traffic.
Barge-in announcements
The system usually connects multiple callers to the beginning of an
announcement, regardless of announcement type. However, you can also administer
auxiliary trunk announcements, DS1 announcements, and integrated announcements
to connect callers to hear a message that is already in progress. This
capability is called "barge-in."
Barge-in operation
When you administer barge-in by setting the Q field to b, only one port plays
the announcement at any one time. When the system routes a call to that
announcement, the call immediately connects to the port and the caller hears the
announcement as it is playing.
Most administrators administer barge-in announcements to repeat continually
while callers are connected to the port. In this way, the caller listens until
the system plays the entire announcement.
Non-barge-in operation
If an announcement port is available when a call arrives, the system connects
the call to the announcement starting from the beginning.
If an announcement port is not available and the announcement is administered
with no as the queue option, the call does not enter the queue for the
announcement and the caller hears busy or other feedback, depending upon how the
announcement was accessed.
Setting up continuous-play announcements
You can set up announcements to continuously repeat while callers are connected
to the announcement, so that a caller can listen until the system plays the
entire announcement. With a "barge-in" queue, you do not need a separate port
for each announcement.
For example, you can set up an Automatic Wakeup announcement to repeat, and use
a barge-in queue. When guests pick up the telephone to hear an announcement at a
particular time, they use only one port. The message repeats on that port until
the last guest goes off-hook and the message ends.
To set up a continuous-play announcement:
1. Type change announcements. Press Enter.
The system displays the Announcements/Audio Sources screen
2. In the Q field, type b on the same line as the extension for the
announcement.
3. Leave the name that is in the Name field, or enter a new description for the
announcement.
4. Press Enter to save your changes.
Interactions for Announcements
This section provides information about how the Announcements feature interacts
with other features on the system. Use this information to ensure that you
receive the maximum benefits of Announcements in any feature configuration.
If you use an integrated, multiple-integrated, or external type of announcement
for Automatic Wakeup, you can also administer the announcement to repeat and to
allow "barge-in" as a queue type. The benefit of repeating announcements and
"barge-in" queues is that you do not need a separate port for each wakeup
announcement. When guests go off-hook to receive an announcement at a particular
time, the guests use only one port. The message repeats on the port until the
last guest goes off-hook, and the message ends.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
maximum of 250 G700 VAL sources in a large S8700 Series media server
configuration also with up to 10 TN2501 VAL boards, providing an ultimate
capacity of 260 sources for the Avaya S8700 Series servers. TN2501 has 31
playback ports (with 60 minutes of storage capacity) and each G700 VAL
source has 15 playback ports (with 20 minutes storage capacity). Initially each
caller that is to hear a non-barge-in announcement on that source is connected
to an available port until each port has one caller connected. Initially 31
callers can be hearing an announcement from a single
TN2501 board (15 with a G700 VAL source). The same announcement can be playing
from multiple ports, each starting at a different time. Once all ports are busy
playing announcements, subsequent callers that are to hear an announcement
residing on that board/source are queued for that source.
Communication Manager queue size over all integrated announcement
sources is 4,000 callers (S8700 Series/S8300 media servers). When a port becomes
available, all callers (up to 1,000) waiting in the queue for a specific
announcement on that source are connected to the available port to hear the
announcement play from the beginning on a first-in, first-out basis.
At any given time you can have as many as 1,000 callers hearing the same
announcement on a given port of a board/source, yielding a (theoretical,
system-wide) capacity of 31,000 callers connected to a VAL board (or 15,000
callers connected to a G700 Media Gateway virtual VAL source).
Factor in barge-in announcements which continuously play from a single port
(that can have as many as 1,000 callers connected at the same), and this
provides a very, very large capacity for playing announcements.
The measurements announcements commands can be used to monitor the system and
help determine burst conditions, allowing for better load balancing of the
traffic.
Barge-in announcements
The system usually connects multiple callers to the beginning of an
announcement, regardless of announcement type. However, you can also administer
auxiliary trunk announcements, DS1 announcements, and integrated announcements
to connect callers to hear a message that is already in progress. This
capability is called "barge-in."
Barge-in operation
When you administer barge-in by setting the Q field to b, only one port plays
the announcement at any one time. When the system routes a call to that
announcement, the call immediately connects to the port and the caller hears the
announcement as it is playing.
Most administrators administer barge-in announcements to repeat continually
while callers are connected to the port. In this way, the caller listens until
the system plays the entire announcement.
Non-barge-in operation
If an announcement port is available when a call arrives, the system connects
the call to the announcement starting from the beginning.
If an announcement port is not available and the announcement is administered
with no as the queue option, the call does not enter the queue for the
announcement and the caller hears busy or other feedback, depending upon how the
announcement was accessed.
Setting up continuous-play announcements
You can set up announcements to continuously repeat while callers are connected
to the announcement, so that a caller can listen until the system plays the
entire announcement. With a "barge-in" queue, you do not need a separate port
for each announcement.
For example, you can set up an Automatic Wakeup announcement to repeat, and use
a barge-in queue. When guests pick up the telephone to hear an announcement at a
particular time, they use only one port. The message repeats on that port until
the last guest goes off-hook and the message ends.
To set up a continuous-play announcement:
1. Type change announcements. Press Enter.
The system displays the Announcements/Audio Sources screen
2. In the Q field, type b on the same line as the extension for the
announcement.
3. Leave the name that is in the Name field, or enter a new description for the
announcement.
4. Press Enter to save your changes.
Interactions for Announcements
This section provides information about how the Announcements feature interacts
with other features on the system. Use this information to ensure that you
receive the maximum benefits of Announcements in any feature configuration.
If you use an integrated, multiple-integrated, or external type of announcement
for Automatic Wakeup, you can also administer the announcement to repeat and to
allow "barge-in" as a queue type. The benefit of repeating announcements and
"barge-in" queues is that you do not need a separate port for each wakeup
announcement. When guests go off-hook to receive an announcement at a particular
time, the guests use only one port. The message repeats on the port until the
last guest goes off-hook, and the message ends.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Status
Similar threads
- Locked
- Question
- Question