There are a bunch, and you need them all.
https://backoffice.voipinnovations.com/Wiki/View.aspx?article=VoIPInnovationsSIPSignalingIPAddresses
↧
FreePBX with VoIP Innovations, NAT and firewall *or* block WAN registrations
↧
Endpoint Manager missing options?
Some basefile edits are not GUI accessible. Check these docs
↧
↧
Google Voice no "ringback" when calling out?
@wmjackson Can you describe where/how you investigated these responses?
I’m having a similar or same problem with a new install of 13 and I’d like to see if I’m getting the 180 response or not. I typically get one maybe two ringback tones then silence till answered.
My Motif version is 12.0.4.2 (I think - checked in Admin->Module Adminstration under “Connectivity”)
Thanks
↧
FreePBX + Digium gateway 2G402F
Dear all,
I installed a free-PBX (version 14.0.2.14) + Digium Gate 2G402F (4 port) + two PSTN providers
Free-PBX server IP: 192.168.1.10
Digium gateway has two IPs: 192.168.1.11 and 192.168.1.12
I have two extensions: 6XXX and 7XXX
I need to configure outbound calls for extensions with: 7XXX through port 1 on Digium gateway and 6XXX through port 2 on Digium gateway. so I created two trunks in freePBX to Digium gateway:
first trunk:
trunk name: 6XXX
type=peer
secret=password
host=192.168.1.11
defaultuser=user
context=from-trunk
and second trunk:
trunk name: 7XXX
type=peer
secret=password
host=192.168.1.12
defaultuser=user
context=from-trunk
I created outbound route in freePBX and saw that extensions 6XXX go through trunk name: 6XXX and extensions 7XXX go through trunk name: 7XXX
I also created two call routing rules on Digium gateway. the outbound calls on trunk 6XXX go through port 1 and 7XXX go through port 2.
but I have issue, all outbound calls go through port 1 on Digium gateway.
Please help on this
↧
Google Voice no "ringback" when calling out?
I think this is wrong.
Please run
fwconsole ma list | grep motif
If you do have 12.x try updating
↧
↧
FreePBX + Digium gateway 2G402F?
That is probably because the ports in the gateway are configured to act as a trunk, that is the gateway decides which port to use. Look for an option to configure port selection.
↧
After Yesterday's Module Updates, 4-2-18, Fail2ban Should Always be Running
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
↧
Live Network Usage not updating
this dashboard window has not updated for almost a month now
I am running v14 in a Hyper-V on Windows Server
everything is up-to-date
Uptime isn’t correct either - says last reboot was a month ago, but rebooted server yesterday
everything else seems OK
mark
↧
Asterisk and Salesforce integration
Hi,
Actually we made a Salesforce click-to-call app that uses ARI in Asterisk 13.
we want to integrate Salesforce with Asterisk using REST API ARI…
I would like to know the difference between chan_sip and chan_pjsip and what is the best between them…
thank you in advance.
↧
↧
FreePBX + Digium gateway 2G402F?
I re-checked the call routing rules in gateway.
the trunk 6XXX --> port1 in gateway --> PSTN 1
the trunk 7XXX --> port2 in gateway --> PSTN 2
But outbound calls still went through port 1 --> PSTN1
when I tried to disable port1 in gateway, then outbound calls went through port2 --> PSTN2
Does the gateway verify the trunk by IP address, so any trunks from one IP will be same?
Thanks
↧
Live Network Usage not updating
what happens when you check for online updates?
Or run fwconsole ma listonline
↧
Live Network Usage not updating
online updates - all OK, both module & system
↧
FreePBX + Digium gateway 2G402F?
In general, all FXO gateways decide internally how to use the ports. Depending on the brand, the configuration varies according to how they manage port assignment. If you are sure that your outbound rules are correctly defined, I suggest you take a look on Digium’s documents to configure port assignment. For example, on Grandstream gateways, you assign the FXO ports to different TCP ports and configure the trunks for each port, like 5060, 5062 and so on. That way the gateway knows which FXO port to use depending on the TCP port that received the dial request. I guess your Digium gateway might have a similar way of doing it, either by TCP ports or by SIP accounts, but you need to check the manual to be sure.
↧
↧
"Works For Me" Status for issues
And why then do we take time to report problems, isn’t it a partnership? Just trying to share thoughts on keeping it constructive.
↧
Resolving Dashboard message
May want to make make the names match as we may not be able to translate.
Just checked and Check Online does not offer a new version and PBX Updater says it is up to date so the Dashboard message is not actually correct.
I deleted it once in the past but it came back. I am sure I can delete it but I just wanted you to know.
↧
Resolving Dashboard message
Well, that massage is sitting there for more than 3 months, you probably already long installed it but never dismissed the notification.
↧
Resolving Dashboard message
Yes it does seem old so I am not sure why it reappeared. Maybe due to the process of reinstalling the distro and restoring.
↧
↧
Resolving Dashboard message
Those dashboard displays are the result of there being records in the notifications table of the asterisk database, You can arbitrarily delete them from the screen, but if the underlying cause remeains, they will be recreated . I don’t believe that they are otherwise spontaneously created randomly without a reason.
↧
"Works For Me" Status for issues
To improve the project and fix bugs
If you have a problem with this status then we it “works for me” what would you suggest we do
↧
"Works For Me" Status for issues
It is a partnership, but it’s important to know that the issue tracker exists for the benefit of the project, which in turn benefits the project’s users. It’s pedantic, but there’s a reason it’s called an issue tracker and not a problem tracker. The dev team can’t action a problem, only the cause of the problem. If the ticket creator can’t identify the cause, nor describe the problem in enough detail so it can be consistently reproduced, there isn’t much a dev can do to proceed. Either the ticket gets a request for additional information or it gets closed as “Works For Me”.
You mention that “Works For Me” rubs you the wrong way, but you neglect to add that each one of those tickets gets a response worded as such:
The issue tracker is not the place for determining the cause of problems. The expectation is that the reporter will avail themselves of other resources to get further assistance. If it later proves that there is indeed a FreePBX bug, the ticket can be reopened with additional details.
↧