Search results

Hi- I have no additional settings configured within the advanced portion of my VI gateway. Can you provide the sip flow on the actual invite of the call? I have attached an example.. Your other screenshot looks like a netstat output of listening ports, not iptables.. do an iptables...

No worries! You will need a dummy username and dummy password in your Gateway settings and yes, ensure port 5080 is opened in iptables. If you're used to FreePBX, the equivilent of of viewing the Asterisk logs by typing "asterisk -rvvvvvvv" in the command line for Freeswitch is "fs_cli". Type...

You mentioned that you are aware that FusionPBX requires a username and password for gateways even though VoIP Innovations uses IP authentication, but I don't see a username and password entered in the corresponding fields in the screenshot. Did you enter a dummy username and password? If you...

The "Show All" button only displays for the Super Admin permission, which is used to administer the entire PBX. If you are attempting to assign admin permissions to an account for a specific domain only, you need to give the user account Admin permissions, not Super Admin permissions.

See: https://docs.fusionpbx.com/en/latest/accounts/extensions.html "Call screen if set will ask the caller to identify themselves their response will be recorded and offered to the person receiving the call."

What softphone are you using? Have you tried an alternative softphone to help isolate the issue?

I have a dummy extension (that isn't registered to an endpoint) that has a follow me set to a cellphone number. When this extension is dialed, the call fails and the logs show the following error: Cannot create outgoing channel of type [user] cause: [USER_NOT_REGISTERED] This makes sense...

The issue is still persistent with my install on the master branch -- the outbound calls in the CDRs show the outbound caller ID of the caller (which is usually the main number of the organization) rather than the extension number of the caller.

I have seen instances where I get a 401 from the PBX when trying to register even though I have whitelisted the IP in Fail2Ban's jail.conf file and reset Fail2Ban as well.. In the latest instance of this happening, enabling rport on the device fixed it for me.

Have you looked at the sngrep logs to see if the REGISTER from the phone is even hitting the primary server?

Just a guess but is 112.215.6.210 the IP address of your PBX? That error message looks like you are trying to register an endpoint to 112.215.6.210, and that isn't defined as a valid domain within your FusionPBX instance.

Do you have something specified in the Emergency Caller ID and Emergency Caller ID Number for the extension that you are attempting to call 911/933 with?

The best way to do this is by using a class of service. This is discussed and taught in the FusionPBX admin class. https://www.fusionpbx.com/training.php

Sounds like you need to add an outbound route for E911. Dialplan > Outbound Routes > Add Choose your gateway Hit the dropdown for dialplan selection and select 911 Emergency.

What is your Outbound Caller ID Number set to for the extension that you are testing with?

Well... have you checked the logs or sngrep when placing an outbound call? If you posted those, that would be helpful..

I completely agree... I personally have taken both training classes, am an active continuing education member, and pay Mark for 1 on 1 support when needed... I hope that the training and continuing education pays off for the project in the long run to enable Mark to bring on more developers to...

Have you restarted nginx or rebooted your server? I'd probably start there.

The external profile runs on port 5080, is that port open on your firewall? Alternatively, you could set your gateway to register on the internal profile which uses port 5060 and then add the IP addresses of your providers to the domain ACL list.

Hi Steve -- welcome! I'm in Dallas as well :)