Monday, December 26, 2016

VRS

VRS Fixed Message 02 General Message Number Input Data 0 = Disable (VRS fixed message will not be played.) 1 = Enable (VRS fixed message will be played.) 0 ~ 100 (0 = No General Message Service) Description Enable (1) or disable (0) the system ability to play the fixed VRS messages (such as You have a message). This item assigns the VRS message number to use for the General Message. Default 0 Related Program 0 03 04 05 06 07 08 VRS No Answer Destination VRS No Answer Time Park and Page Repeat Timer (VRS Msg Resend) Set VRS Message for Private Call Refuse (VRS Msg Private Call) Set VRS Message for Caller ID Refuse (VRS Msg CID) Call Attendant Busy Message 0 ~ 25 (Incoming Ring Group Number) 0 ~ 64800 seconds 0 ~ 64800 seconds 0 = No Message Played 1 ~ 100 = VRS Message 1 ~ 100 101 = VRS Fixed message (Message will only play if PRG 40-10-01 is enabled.) 0 = No Message Played 1 ~ 100 = VRS Message 1 ~ 100 101 = VRS Fixed message (Message will only play if PRG 40-10-01 is enabled.) 0 ~ 100 (0 = No message) This item assigns the transferred Ring Group when the VRS is unanswered after Call Forwarding with Personal Greeting Message. If an extension has Personal Greeting enabled and all VRS ports are busy, a DIL or DISA call to the extension waits this time for a VRS port to become free. If a Park and Page is not picked up during this time, the Paging announcement repeats. This item assigns the VRS Message number to be used as Private Call Refuse. When Fixed message is set, VRS message guidance is: “Your call cannot go through.” This item assigns the VRS Message number to be used as Caller ID Refuse. When Fixed Message is set, VRS message guidance is: “Your call cannot go through.” 0 (No Setting) 0 0 0 0 0

Monday, December 19, 2016

queued call

While  a caller waits for a UCD group  member  to answer (in queue),  several  queued call operations are possible.   These  include the  following. •   No Answer – Member  advancement.  Each UCD  group has a No  Answer  Timer.   You can set this timer to  advance the call from one UCD group member to the next when the ringing  member does not answer  the call  within the  time allotted. •   Overflow  1 Destination programming.  Each  UCD  group has  an overflow 1 timer and destination.   You can set this timer  to determine how long calls  will  remain in queue,  before being routed  to the  overflow 1 destination.  The destination can  be an extension  responsible for handling  calls that  remain in  queue too long, or a voice  announcement device.  You  can use recorded announcement devices  to  play recorded messages  to callers  waiting in queue, for example, “All agents are still  busy  - please continue to hold.”   The system  plays the overflow  1  destination only once.   For high  traffic  scenarios,  you can  use  a  recorded voice announcement UCD group to play the  same  message to multiple callers. •   Overflow  2 Destination programming.  Each  UCD  group has  an overflow 2 timer and destination.   You can set this timer  to determine how long calls  will  remain  in queue, following  the overflow 1 timer, before being routed  to the overflow  2  destination (overflow 1  timer + overflow  1 destination recorded message time + overflow 2  timer.)   The destination can be  an  extension responsible for handling calls that remain in queue too long or a voice announcement device.   You can use  recorded announcement devices to  play  recorded  messages to  callers waiting in queue, for example, “Please continue  to hold to  reserve  your place in  queue.”   For high  traffic scenarios, you can use a recorded voice  announcement UCD  group to play  the same message to multiple callers. •   Overflow Count  programming.  Each UCD group has an overflow  count that is  associated with the  overflow 2 timer.   You can set  this timer to  allow a specific number  of times  that the  system may repeat the  overflow  2 timer.  For each cycle  of  the overflow 2 timer, the  system plays the overflow 2 destination  recording.   If a call  remains in queue so  long that the overflow count counter expires,  the system routes  this  call to the programmed  reroute  destination. •   Reroute Destination programming.   Each  UCD  Group has a reroute  destination.   You can program this  with an  extension number the system uses  to remove  the call from UCD  group queue.   The system  then routes the  call for immediate handling. Other features whose  programming may affect  UCD programming  includes the following. •   CO Line Ring  Assignment •   UCD Reroute  Destination •   UCD Voice Announce Group •   UCD Agent Log On/Log  Off •   Voice Mail -  Digital Integration •   Recorded  Announcement Devices (RADs)

Friday, December 9, 2016

received format

Receive Format Delimiter Dial Code Route Setup of Receive Dial 0 = Address 1 = *  ANI 2 = * *  DNIS 3 = *  ANI * *  Address 4 = 5 = ( *  ANI *  DNIS *  DNIS *  ANI *  = Delimiter Code) 1 ~ 9, 0, #, * 0 = Fixed Route (Item 08) (No Routing) 1 = Routes on Received DNIS or Address Data 2 = Routes on Received ANI Data COS 01 = 0 COS 02 ~ 15 = 0 * * * Use this option to specify the format of the ANI/DNIS data received from the Telco. Make sure your entry is compatible with the service the Telco provides. The character *  indicates a delimiter.If Program 34-01-02 is selected to 2 (MF), this Program works only as 4 = *ANI *DNIS *. This option defines the character Telco uses as a delimiter (see entries 1 ~ 5 in Item 1 above). Valid entries are 0 ~ 9, #, and *. This option specifies the source of the data the system uses to route incoming ANI/DNIS calls. If option  2  is selected, refer to Program 34-09-04