COR and Announcements

[lmtb]

CM 6.3
Need to be able to setup remote access so that we can record announcements but don't want to open up access to all Announcements via this route (to prevent users fat fingering and entering the wrong announcement to update).
Been advised that using a dedicated COR should do it.

So if I give the Remote Access Dial In this new COR X and also ensure that the announcements they can update are set as COR X - should it just be a case of changing the calling permissions to NO for everything except COR X in the COR setup.
I'm guessing not as that doesn't work but not sure what I'm missing.

Thanks

 

[AvayaTier3]

COR are used to restrict and allow listening, not recording.

COS with console permissions controls access to "announcement access code" record, play, delete any announcements that are not protected. If you do not want announcements to be changed, protect them.

Announcement session process

To begin an announcement session, the user must dial the administered Feature
Access Code (FAC) followed by the announcement session.

If an announcement session is already in progress, or if a save or restore
command is in progress, then the user hears reorder tone (fast busy) and the
system drops the call.

If the telephone session port to an integrated announcement source is in use,
then the user hears reorder tone followed by silence. This indicates that the
port will be reserved for an announcement session. The user should redial the
FAC and extension every 45 seconds to gain access to the port.

Note: You need to have a telephone or console with a class of service (COS) that
provides console permissions to record announcements.
Multiple telephone sessions are allowed, with one session associated with each
active integrated announcement circuit pack.

Once a telephone user accesses an announcement session, the user can dial 1 to
record an announcement, 2 to play an announcement, or 3 to delete an
announcement. If the announcement source memory is more than 90% full, then the
switch gives stutter dial tone when the user gains access to an announcement
session. Even if the user hears stutter tone, the user can begin speaking to
record the announcement.

Avaya recommends that you use a digital or IP telephone, since these telephones
provide the best quality and functionality.

Tip: Do not use remote telephone connections that route over IGAR (Inter-Gateway
Alternate Routing)-supported facilities. The beginning portion of the recording,
about four or five seconds, is not recorded after hearing the ready tone.

To end the recording:

If you are using a digital telephone, press the pound key (#). You hear a dial
tone again, and you can continue your session.

If you are using an analog telephone, hang up quietly. If your analog telephone
is not connected through lineside DS1, the system might record an electrical
click at the end of the recording. You must redial the Announcement FAC to
continue your session.

If you are using a digital telephone, and you want to listen to the announcement
that you just recorded, dial 2. The recording plays back through the handset.

To listen to the announcement after you hang up, dial the announcement extension
from any telephone or attendant console. The announcement plays through the
handset.

When you directly dial an announcement extension, for which an announcement has
not been recorded, you hear silence instead of a busy tone with the VAL-type
sources, such as the TN2501AP circuit pack or the v VAL source.

Note: You must wait 15 seconds after you record an announcement before you can
dial the extension to hear the announcement replay. During this 15-second
window, you cannot record a new announcement, and no one can play this
announcement. However, you can rerecord the announcement during this 15-second
period. To rerecord the announcement, dial the Announcement FAC, dial the
extension, and then press 1 before the 15-second timer expires.

removing announcements from valboards:

1. change announcement, blank out announcement extension does not remove the
   associated .wav file. This is working as designed.

   If the announcement extension shows Pr "y" this means it is protected and
   cannot be erased, recorded over, or removed from the board and list directory
   board command will show the .wav as protected "y"

2. If the .wav file is not going to be re-used, it can be removed a few
   different ways. NOTE: all will fail if the list directory board command shows
   the .wav file is protected.

   Before using any option below, the change announcement command from the SAT
   must be used to set the Pr "n" so the .wav file is not protected.

   A. Use the Announcement Access Code: and erase the announcement, before
      using change announcement and blanking out the extension. On newer loads
      remove announcement is used for this.
   B. Use Val Manager or ftp to connect to the board and delete the .wav
   C. Use the SAT interface and from the Command: prompt, "remove file board
      02A02 /annc/xxxx.wav"

3. use the .wav file name you want to remove, add a new announcement using this
   name. make sure the protected field is set to "y"

4. change announcements, change the protected field to "n"

5. list directory and make sure the protected "y" has changed to "n" for the
   .wav file you want to remove or change.

6. remove file board 02A02 /annc/5816.wav

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]

 

[lmtb]

Thanks for that, so looks like we've been misinformed.

We need project 'A' to be able to dial in and update their own announcements, but don't want them to be able to update project 'B' announcements in error and vice versa (We're looking at up to 20 difference types of business that would all need to update their own announcements independent of each other).

We'd been advised that we could do it with dedicated COR's but that doesn't appear to be the solution.

Protecting the announcements isn't an option as they do need updating at any point. Ideally we'd wanted the teams to be able to make these changes independent of us having to upload new announcements but doesn't look like it'll be that easy.

Thanks again.

 

[newglide]

Tier3, you said, "If you do not want announcements to be changed, protect them."
dumb question but how can I protect them?
I am also in the process of having users record announcements but don't want them to inadvertently delete the wrong thing.

 

[AvayaTier3]

change announcement 1003                                        Page   1 of   1

                       ANNOUNCEMENTS/AUDIO SOURCES

  Extension: 1003                            COR: 1
  Annc Name: AA_Main_greeting                 TN: 1
  Annc Type: integrated                    Queue? y
Group/Board: 04B15
  Protected? y                              Rate: 64

list directory /annc board 04B15                                Page   1   SPE A

                                LIST DIRECTORY

Board                File/Directory                    Creation       Size  Pro-
Loc                      Name                       Date       Time    Kb   tect
04B15 F:@AA_Main_greeting.wav                     2001/09/11 14:52:16 102    y
04B15 F:@AA_Main_Holiday_OOH_menu.wav             2001/09/16 13:26:10 301    n

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]