Cheat Sheet (Common / Hidden case scenarios)

FAQs (Frequently Asked questions)

Commenting and Moving a Voicemail from one extension's inbox to other

• Listen to your voicemail on Ext. A, press #6 (it will then give you further options)

Press 1, To move the message to another mailbox. Press 2, To copy the message to another mailbox Press 3, To record a comment to the message Press 4, To mark the message as Urgent Press 5, To mark the message as Private

• Press 3 to record a comment

This tags the VM (Voicemail) with the comment of your choice.

• Press 1 after recording the comment

With this you can now move the message to another extensions mailbox of your choice.

• Hit the extension number of the destination extension (without the prefix 8) and press "#"
• Upon checking the voicemail of the extension the message was moved to, the comment is played first followed by the voicemail as expected.

How to use Translations

1. On the PBX GUI, manually enter the URL in the browser as http://pbxip/reg_translation.htm
2. Turn it on and save it.
3. You would see an icon appear on the right-hand top of the screen on the PBX GUI. Shown below.
4. Now, go to the customize page on admin/domain level (according to your need to make this change on the domain or admin level) and select all options highlighted in the red box in image 1.
5. You can change whatever you want from that drop-down menu in the email settings options.

Navigate to Admin mode ---> Customize --->Template Choose your type and your page.

Click on the language rotator, then choose the email template you would like to change, click on Save.

note

Make sure to go back to /reg_translation.htm and turn off the translation

When you come across, blank/empty text fields on the PBX.

1. Navigate to /reg_translation.htm > Turn the translations on > hit save > Turn it back off > hit save.
2. Go back to the original webpage and now the texts should be visible.

note

This needs to be done, everytime a PBX is upgraded in order to add the new texts / dropdown menu texts needs to be updated too. This step, cannot be avoided.

Apply certificates via the Let's Encrypt / ACME Directory setting

Pre-requisites for this setting to be used to generate the certificate on the PBX.

1. PBX can be hosted on a public IP or behind a NAT on the private IP too. But make sure the ports 80 and 443 are always open and are assigned specefically to the PBX. Port forward your local ports to 80 and 443 if it's behind a NAT / DMZ type network.
2. The PBX should have a valid FQDN (Fully qualified domain name) assigned to it which is reachable via the internet from anywhere. Let's Encrypt says "We don’t publish a list of IP addresses we use to validate, and these IP addresses may change at any time. Please read this."

Next, how to generate a certificate

1. Once the above conditions are met, on the PBX, navigate to /reg_settings.htm > Ctrl + F (or Command + F for mac users) for ACME Directory URL and set it to "Let's Encrypt"

2. Wait for a couple of minutes (maybe less) and you should now see the certificate under /reg_certificate.htm > Certificates tab.

   A. If it was created successfully, now you can log out of the PBX and clear the cache (log back in via incognito mode on Google Chrome) and log back in via https://PBX_URL.com

   B. If it didn't go through, please turn on the admin level logs for Web clients set to level 9 and clear everything else from under /reg_logfile.htm and send us the error logs to vodia.zammad.com (this being a third party system, please create an account if you don't have one already) and we can take a look at it.

   Quick checklist:

• Making sure that your root CA list is update (might have to press the Reset button at the bottom).
• Make sure your license is current, maybe make sure that you are in a recent (Anything above 67 should do).
• Make sure that port 80 is open.
• Make sure that the DNS A address points to your PBX.
• Make sure you are not using DNS for ACME challenge (unless you are using dnsmadeeasy, but even that could be a problem).
• Rename the domain address, then wait a second and rename it back.

note

Please avoid sending us any emails to the support email regarding technical related issues as we don't monitor that email chain anymore

Set ANI (*59)

This feature allows the extensions to dial the star code and change their outbound ANI on the go. Steps are:

1. Make sure that the star code for Set ANI is set, e.g. to *59. This step may be neccessary when upgrading from older versions.
2. Add ANIs to the desired account.
3. Go to Domain → Setting → General Settings → Extensions may use star code to change ANI field and choose from either of those drop down menus:
   1. Only own ANI: User / Extension can enter only it's own DID number (as is) as it's Outbound ANI number.
   2. Any ANI in this Domain: User / Extension can enter any DID number as their own ANI that they can find inside the domain that they're a part of.
   3. Any NANPA ANI: User / Extension can enter any DID number that belong to the NANPA number format on whole of the PBX.
   4. Enter any ANI: User / Extension can enter any DID number that resides on the PBX as their own ANI.
4. Dial e.g. *591234567899 (use your own ANI) and hit send and the audio prompt will confirm that ANI has been set by repeating the number to you, if successful.
5. If it doesn't go through, it will prompt the user with "This number could not be found".
6. Make a call out. This will only work, if your trunk allows random ANIs to go out, or else it wont.

Group permissions required for Redirecting various Accounts

• Navigate inside Domain > Settings > Groups, and make sure the permission "Redirect groups" has been assigned to the extension(s) that has to have the permission to carry this out.
• To forward all auto attendants, hunt groups, and agent groups of the domain, *80 must be used without an argument.
• To forward only a specific account, the account must be specified after the star code.
• To disable this feature, enter a star in place of the call forward number.

Users are unable to sign in, into their user portals (Throws Incorrect password error !)

• Navigate inside Domain > Settings > Groups, and make sure the permissions "User frontend group", "Enable App use", "Enable Frontend" are assigned to the user(s).
• Save the group permission and users should now be able to login into the user web portal from now on.

Giving extensions permissions to record greeting for Auto Attendant

The following permissions / groups setting need to be given, ONLY to all of the users that need to record the audio. manrec manivr