Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cdent4

Pages: [1]
1
I have a customer who received a call to a call director mailbox.  Within the auto attendant, they dialed 911, which happens to be a speedcall in the pbx, and the call went to the PSAP with incorrect information.

What I want to do is deny/block the ability for users to dial 911 from an auto attendant, forcing them to hang up and call 911 the proper way.

Customer has SIP trunks into a 9.4 MXE-III controller, and a 9.7 Micollab server with Nupoint.

I assumed it would have something to do with the Nupoint system configuration.  The customer has extension numbers that begin with 9, so I'm thinking I can't just block anything they dial starting with 9.  Here is the Nupoint config:

Activating active configuration config=0 without Stoping TCP/IP
 NUPOINT VOICE SYSTEM CONFIGURATION
 
 Group #1: "Line Group 1"
  Module 1: Lines 0:0 0:1 0:2 0:3 0:4 0:5 0:6 0:7 0:8 0:9 0:10 0:11 0:12
                  0:13 0:14 0:15 0:16 0:17 0:18 0:19
            Voice Recognition Conn: <none>
  Application = [NP RECEPTIONIST]
  NP Call Director Interface
   Dial plan = [5,5,5,5,5,5,5,5,5]
   Administrator mbox # = [99998]
   General Greeting mbox # = []
   Attendant mbox # = [99999]
   Transfer Call Box # = []
   Wait Prompt = [Y]
   Caller multiple messages enabled = [Y]
   KEY_0 for attendant transfer during greeting = [Y]
   Disconnect string = []
   Pre-company name string = []
   Pre-mailbox greeting string = []
   Passcode Length  Min = [4], Max = [10]
   "6" Key Operator Transfer Dial String = []
   "6" Key Operator Transfer pre-Dial String = []
   Start of day = [08:00 AM], End of day = [05:00 PM], Days of Week = [DDDDDNN]
   Passcode trip count = [5],  Passcode trip period = [24]
   Dial-by-name: Last First = [Y], Match Threshold = [3], Exact = [Y]
                 Suppress Number = [N], Single Digit Access = [N]
   Delay Before Answer = [50]
   E-mail Transfer String = []
   Allow Dial an Extension for callers = [Y], users = [Y]
   Analog Networking: Call Setup timeout = [6]
      International Access Code = [], Country code = []
      Area/City code = [], 1plus dialing = []
      Area/City code is dialed with Local Telephone Number = [N]
      Telephone number = [], Loop-back Test Mailbox = []
   Name Greet Quality =
  • , Message Quality =

   Pre-DN = [S+], Post-DN = [+H], Connect = [], Serial = [S+]
   Return = [S+], Return call reject = [++], Reorder Action = [0H]
   PBX dial plan = [5,5,5,5,5,5,5,5,5]
   Offsets = [0,0,0,0,0,0,0,0,0]
   Deleted digits = [0,0,0,0,0,0,0,0,0]
   Timeout for receipt of first DTMF digit (.1 seconds) =

   Greet/Name = [G], PBX console operation = [N]
   Day operator = [0H], Night operator = [0H]
   Attendant extension =

   TDD - Dialtone detect time =

   TDD - Minimum Dialtone Detect Power =

   TDD - Play delay after DTMF detect =

2
I found the problem.  When I create a softphone for a user, it has a flag to "Send Deployment Email" already checked.  In the Micollab Client tab, if the Deployment Profile field was set to anything other than "Do Not Deploy", it would send the duplicate email.  Once I set that field to "Do Not Deploy" I then only got the one email with the correct extension number information.

3
I just started with this new company 2 months ago.  We onboard a lot of new users.  Every time I build a new user, give them a phone (deskphone, softphone, or both), a Micollab client, and a teleworker, when the deployment email goes out, the email address receives 2 emails.  One has the subject line MiCollab Client configuration ext no. xxxxxxx for user Doe, John.  A second email also goes out to them with the subject line MiCollab Client configuration ext no. (none)  for user Doe, John.

It's a minor inconvenience to have to tell the user to please use the authentication key in the email with their extension number in the subject line, but I'd like to get rid of the second unnecessary email for (none) extension number.

Any ideas where this is programmed and why?

4
Anyone else run into this problem?

One of our users will start a chat with another employee in their section.  They will add other employees to the chat as they start their shift.  At some point, and the specific number of people in the chat appears to be irrelevant, they will attempt to add a user, but get an error message (see the attached picture).  The user they attempted to add is actually in the group chat and can send and receive the group chat messages.  But they don't appear on the left side of the window, and the error message appears.  If they close the group chat window and reopen a new window, all of the members will then show up in the chat.

Is there a limit to the number of chats/group chats/members in a group chat on the server?  Is there a timer for allowing users to join a group chat?

We are currently running MiCollab 7.3 and I have not been able to find any notices of fixes in recent releases.


Pages: [1]