CQ Frequently Asked Questions

NimbusVoice

Transfer to VM not working.


This is typically a feature code issue. Say you are transferring to 110's VM you transfer to *110. Go to Admin --> Feature Codes and search (Control-F) for *11. If you are having an issue transferring to 125 then search *12. When you find it, either customize it to change the feature code or disable it if you don't need it.




Calls dropping after 1-2s, one way audio.


Settings --> Asterisk SIP Settings --> Check your WAN IP and LAN IP to verify they are correct. It is very important to also click on the Chan SIP settings tab on this page and check your External IP. This should match what you had on the previous tab.




Remote phone has one way audio


Applications --> Extensions --> Edit the Remote Extension --> Advanced Tab --> Scroll to the Edit Extension Section --> Change NAT Mode to Yes. The remote extension will need to be rebooted after making this change.




Calls to remote phone go directly to VM


If you have already verified that NAT Mode is set to yes in the advanced tab of the extension in question they you are most likely looking at a router issue at the remote site. Your best option is to replace the remote site router with a known VOIP friendly router. If this is not an option then working with the provider of the remote site router to turn SIP AlG might be an option as well.




I don't see a module that is typically available on NimbusVoice


This is most likely a permissions issue. Go to Admin --> Administrators. Click on the small tab on the far right that has horizontal lines. Out will pop the users that have access to NimbusVoice. Select the admin user. The screen will then show you which modules are visible for this user and which are not. Find the module you are looking for on the "Not Visible" side and drag it to the "Visible" side. Save and apply. You will need to log out and log back in, in order to see the change. To log out click on the gear in the upper right hand corner and you'll see log out as an option.




Setting up two (or more) phones to be the same extension - twinning.


To do this you will need to create a PJSIP extension and not a SIP Extension. 1. Creata a PJSIP Extension. 2. Open/Edit the PJSIP Extension. Click on the Advanced Tab. Scroll to the Add Extension section and look for Max Contacts. In this field enter the number of phones you wish to register as this extension. Save and apply. 3. Since PJSIP registers on a different port than SIP(5060) we need to find what port that is. Settings --> Asterisk SIP Settings --> PJSIP settings. Scroll to the bottom and look for Port to List on. Let's just say it says 5300. 4. Log into the web gui of the phones you wish to share an extension. Program them as you would a normal extension. Except where you see port (next to SIP Server) change that from 5060 to 5300 (or whatever port your Nimbus is using for PJSIP, see step 2).




Local phone will not register!


If you are certain you have input the correct extension number, secret and sip server then you may be looking at a phone that has been blacklisted. Admin --> Nimbus System Admin --> Intrusion Detection Check the blacklist at the bottom and you may see the LAN IP of the device in question. If you do then be sure to add your local IP scheme into the whitelist (192.168.1.0/24 for an example). Once you add your local ip scheme you may also want to add your office WAN IP and CQ's WAN IP (97.87.30.82). Press submit. After that processes, press restart. This will clear out your banned list and activate your newly added whitelist. At this time your phone should register.




How do I pick up a call on a phone that is ringing if my phone isn't ringing?


The easiest answer is to dial *8. This is the pickup code, but this does require some programming in the NimbusVoice in order to allow this. Mainly because you want to control who can pickup another person's call. For this example I will program extension 105 and 108 to be able to pickup each other's calls. 1. Applications --> Extensions --> Edit Extension 105 --> Advanced Tab --> Scroll to Edit Extension section --> Call Groups and Pickup Groups. Enter a number or word in each (need to match) 2. Follow the same steps for extension 108. 3. At this point *8 will allow extension 105 to pick up a call ringing on extension 108 and vice versa.




Transfer to VM not playing the right VM message?


I have an unavailable message recorded but when someone gets transferred to my VM box they are hearing a canned busy message. Settings --> Voicemail Admin --> Dialplan Behavior Tab --> Direct Dial Mode Here you can change what message the caller hears when they are transferred directly to your VM box.




How can I change the emergency caller id number for a specific extension?


Applications --> Edit Extension button for extension you wish to change --> Advanced --> Scroll down to Extension Options Settings --> Emergency CID. Input the e911 number you would like for this extension




When callers go to my IVR there is silence and then the Nimbus says it has not received a valid response.


This is because you have not attached the system recording to the IVR. First make the system recording (this is what the caller hears that tells them what buttons to push), then go to Applications --> IVR and in the Announcement field select the system recording that you would like callers to hear.





CQ Phones

Phantom Calls to CQ Phones


Log into the web gui of the phone. Profile --> Advanced Set Anonymous Call Rejection to Yes




Program a button to monitor another extension's VM


The button type will be a BLF and the value will be *98extension#. So if you wanted to monitor extension 110 VM then you would make a BLF key with a value of *98110




How do a I set up distinctive ring tones for external vs internal calls?


Changing Default Ring Tone From within the Clearly Devices module on your PBX navigate to the template you want to change the default ring tone on

Click on the Phone Settings tab from within the template.

Scroll down to the Ringtone option and pick from the drop down of Ring 0-8

Changing Ring Tones from within FreePBX Ring Groups Navigate to the ring group you want to change the ring on Locate the the Alert Info field Select Custom
Set the value to ringX where X is the ring tone you want. i.e. ring1, ring6, etc.
Queues Navigate to the ring group you want to change the ring on Locate the the Alert Info field Select Custom
Set the value to ringX where X is the ring tone you want. i.e. ring1, ring6, etc. Inbound Routes Navigate to the ring group you want to change the ring on Locate the the Alert Info field Select Custom
Set the value to ringX where X is the ring tone you want. i.e. ring1, ring6, etc. Extension to Extension Calls This would fall back to the default ringtone, see the Changing Default Ring Tone section above.




Can I turn off the Missed Call Notification?


Yes - Access your template and set Missed Call Notification to No





Router/Firewall

How do I lock down my port forwarding?


One option is to use source port forwarding. Even with port forwarding, you are still allowing access to the entire world through port 58088 or port 56222 (or whatever ports you chose for http and ssh access). Most routers allow you to input a source. In the picture below ports 58088 and 56222 are open but only to someone coming from a WAN IP of 97.87.30.82 (CQ Simple's WAN IP). You could create a rule that opens these ports both for CQ and your WAN IP




What ports do I need forwarded on my firewall for the Nimbus to function?


Let's start with an on-premise Nimbus: Port 5060 (UDP) will allow for SIP Trunks and remote phones to register Ports 10000-20000 (UDP) will allow for audio to pass. If you are running off POTS lines and no remote phones then you do not need these ports open. Port 80 (TCP) will allow for remote access to your system. We highly advise port translation and source port forwarding. Port 22 (TCP) will allow for remote ssh (root) level access. We highly advise port translation and source port forwarding. CQ is the only one who would access a system via ssh so you should source port forward this for 97.87.30.82 Port 4569 (UDP) allows two Nimbus systems to connect. Port 4445 (TCP) allows for remote NimbusDashboard Access. Port 81 (TCP) allows for remote access to the UCP.





NimbusDashboard

Drag and Drop Transfer Not Functioning


In recent updates to the dashboard the drag and drop feature has been replaced with buttons. Using the blind transfer, attended transfer or transfer to VM buttons are now to appropriate ways to transfer a call on the dashboard.




When I log into my NimbusDashboard Admin I do not see the plugins option on the left?


This is often a permissions issue. Log out of your current NimbusDashboard Admin session. Then attempt to access the NimbusDashboard Admin section again but this time use the following credentials: username: pbxadmin password: cqsimple5103




Can I access the NimbusDashboard remotely?


With the proper port forwarding in the router - Yes! 1. In your firewall forward port 4445 (TCP) to the internal address of the Nimbus. 2. The a remote user would open their web browser on a remote computer and type in: http://WAN IP of Nimbus:58088/fop2 This will take them to the log in where they would input their extension # and password.




Dashboard only showing 15 extensions and requests activation?


In this case your Dashboard has lost connectivity to the register server. Step 1: In the landing page of the Nimbus select Server Info. Copy and paste the Dashboard activation code. Step 2: Log into the Dashboard using a known extension/password. At the bottom where you see the message indicating you are using the Lite version, select Activate and then paste the code you copied from step 1.





Default IPs and Credentials

Nimbus


IP: 192.168.1.245 Username: admin Password: CQSimple




Nimbus Configured Router


IP: 192.168.1.1 Username: admin Password: cqsimple




NimbusWatch Router


IP: 192.168.1.1 Username: Emailed to you Password: Emailed to you WAN Access: cqsimple.mycloudconnection.com WAN access is where the programming of the firewall occurs.




CQ Phones


IP: DHCP, press the check mark in the upper right hand corner of the phone in order to find the LAN IP of the phone. Username: admin Password: admin Older CQ phones may have an admin password of 22222 or 222222




NimbusDashboard


Username: admin Password: CQSimple if you do not see the plugin options in the admin, log out and use the following credentials: U: pbxadmin P: cqsimple5103




Nimbus40 not accessible via default IP?


Be sure you are plugging into the eth port that is closest to the audio jacks. The other eth port is not active.




Can I have root level access?


At this time CQ does not share root level access to the Nimbus system.




Where do I find my Deployment ID?


There are 3 places to find the deployment ID: 1. On the side of the Nimbus server itself you could find a white sticker that proves the Serial #. This is the same as the deployment ID. 2. On the Landing Page of the Nimbus under the Server Info tab you will find your Activation Number: 3. Inside NimbusVoice: Admin --> Nimbus System Admin --> Activation (link on the right), you will find your deployment/activation ID.





SIP Trunks

What's the difference between digest and IP authentication SIP Trunks?


With digest SIP Trunks you check in with the SIP carrier using a username/password. For the most part they don't care what your WAN IP is. This is a must if your customer does not have a static Public IP. With IP authentication you tell the SIP carrier what your Public (WAN) IP is and they send and accept traffic from that IP only. The SIP Trunk programming as you can imagine is different. With the digest SIP Trunks you should expect to have a username, password and register string. The IP Auth has no password, username or register string. Your SIP Trunk provider will be able to indicate which you have. You should also be able to tell from the welcome email they send you whether you are using digest or IP auth trunks.




Are my SIP Trunks really registered?


The first place to look is Reports --> Asterisk Info --> Peers You should see your SIP Trunk, the WAN IP of the SIP Server and the status. OK is a good start although that doesn't guarantee registration. If you see Unreachable then your trunks are not registered. If you have Digest Trunks and you have an OK status then click on the Registry link on the right. Scroll down a bit and you will see your SIP Trunks. If the status is Registered then you should be set. If the status is Auth Sent or Waiting then your trunks are not registered. If you see Auth sent then you might be sending the wrong password or username. Contact your SIP carrier and ask them why your registration packets are not being approved.




How do I program my new SIP Trunks?


I would first start by checking to see if someone else has already attached these SIP Trunks to a Nimbus before. To do this, log into the dealer portal at cqsimple.com and select Wiki. Then scroll to the bottom to find the templates for known SIP Trunks. If you do not see yours then I would start by using a known template from another SIP Carrier on the wiki. If your trunks are digest then follow the template of a digest trunk. If they are IP Authen then follow the template for an IP Auth trunk.





CQ Simple    989-492-7068