Error says it all. Check all your inbound routes, one or more has a bad dest.
↧
Reload failed because retrieve_conf encountered an error: 255
↧
Network setup
Please tell us about the application. New system? If so, why on-site, rather than in the cloud? If not, what are you replacing and why? Approximate size (number of extensions, number of simultaneous calls)? Any non-VoIP trunks (POTS, PRI, GSM gateway, etc.)?
Why is a single NIC connected to your existing LAN unsuitable?
That implies either multiple public IP addresses or double NAT. Why do you want to do this? What equipment do you have now between the pfSense and your ISP(s)?
Is the machine virtual or physical? If virtual, which platform? If physical, can you connect a keyboard and monitor to it so you can troubleshoot when the network isn’t working?
↧
↧
Suspicious activity
What kind of trunk (pjsip or chan sip) for your carrier? Is port 5060 on your box ties to pjsip or chan sip?
↧
Suspicious activity
In Reports->Asterisk Info, does Peers show the trunk as online? If using registration, does Registries show it as registered? If not, fix those things first. pjsip logger should show REGISTER and OPTIONS requests and any responses.
If the trunk is online, pjsip logger should show an outgoing INVITE for a call attempt and any responses.
↧
ALL CIRCUIT BUSY pjsip log
Solution: Enabling SIP Credentials at Flowroute allowed outbound calling, no more ACB message.
In reviewing security settings it was suggested to disable SIP Credentials if using a static IP host, when I did that we lost outbound calling. Enabled it and outbound started to work but we lost inbound!
As I said, I had mistakenly changed the SIP port in both my PBX and at Flowroute in Inbound Routes. Though I had changed the SIP port back to 5060 to it required deleting and adding the route.
All is well. Thanks.
↧
↧
ALL CIRCUIT BUSY pjsip log
This usually means that the public IP address from which you sent the call is not listed in Allowed Outbound IPs on Flowroute.
↧
How to Handle Multiple Deployments
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
↧
Reload failed because retrieve_conf encountered an error: 255
Thanks Lorne. I had tried that in a prior build, but I think I got googled off the right path and tried that last. I’ll take another look doing route triage first. Thank you.
Edit: There was one default route in there with no destination. It was the ANY route which was not pointed anywhere. Killed it off and reapplied with success! Thanks again!
↧
Suspicious activity
Let me say, thanks for your patience and assistance.
All is working and each of the issues that have been raised in this thread addressed.
In reviewing security settings Flowroute documentation suggested to disable SIP Credentials if using a static IP host as I am. Doing this now appears to have what disabled outbound calling. Enabling SIP Credentials restored outbound calls. Great.
But we lost inbound calls. (Really!?) As I said, I had changed the SIP port but changed it in both: CONNECTIVITY-TRUNKS - SIP SERVER PORT and
SETTINGS - ASTERISK SIP SETTINGS - CHAN PJSIP SETTINGS - UDP - PORT TO LISTEN ON
I saw that, though I had changed the SIP Port back to 5060 in CONNECTIVITY-TRUNKS - SIP SERVER PORT and in Inbound Routes at Flowroute, it was still using the modified port number. Deleting and recreating the Inbound Route at Flowroute fixed.
So, to address Suspicious Activity we have:
- Changed all passwords for users and device secret words.
- Made all device secret words longer and unique, had been all the same and 8 chars.
- Changed provisioning to http rather than tftp.
4, Verified all IP addresses in whitelist - Verified Firewall enabled
- Verified Responsive Firewall was enabled for SIP.
- Enabled IP Authorization for connection to SIP provider.
- Verified all open ports and confirmed standard ports not used for http and ssh.
What I need to learn yet is how to read log files and SIP traffic.
↧
↧
Suspicious activity
This won’t do you any good unless either it’s password protected (the phone or other device must supply a password to retrieve its provisioning info) or it’s firewalled (only authorized IP addresses can access provisioning data).
Using an obscure port is a big help if you do it from the start; the bad guys can’t afford to scan every port on the internet. But once your machine has been compromised, unless you have changed your IP address, they will scan every port on your IP in an attempt to regain access.
↧
Reload failed because retrieve_conf encountered an error: 255
One other question, if I may. I am doing this move to allow pjsip connections with flowroute, as the Nevada POP is going dark on June 11, 2020. The other edge servers don’t allow sip/chan_sip so I need to connect some other way. I was thinking pjsip.
As the pjsip trunk tab was not available, I started looking into why. I noticed that the FreePBX V12 machine could be set to BOTH for a SIP driver.
So my question is, if I change
SIP channel driver from “chan_sip” to “both”, leave the extensions on chan_sip, and set up trunks for pjsip, will this work? In other words, will chan_sip talk with pjsip?
↧
ALL CIRCUIT BUSY pjsip log
We had changed the SIP port then changed it back to 5060. The Outbound Route still used address:xxxxx instead of address:5060. Deleted the route and recreated it, all is well. Thanks.
↧
Suspicious activity
Each phone has a unique password for provisioning. Obscuring the provisioning port is a good idea, thanks. I have to assume someone has my ip.
↧
↧
Setting up OBI110 for FXO Gateway
Quetion for you Stewart1,
I have everything working with this setup, I can dial out to the MJ and a 10 digit rings through locally for me but if I put a 1 into the mix I get a message back that I need to dial a 1 or area code and then MJ hangs up. I checked outgoing manipulation rules on OBI110 trunk and set up for long distance and 11 digit dialing but still not working. Is there and adj. in the OBI110 that needs to be done for long distance?
Thank You
James
↧
Reload failed because retrieve_conf encountered an error: 255
The Trunk and extensions do bot have to use the same technology.
↧
[ChanSccpB] Auto Answer
Hello, I’m still having issues with getting the phones to answer, and can only find a gitter chat on the github, if you have anymore advice I’d greatly appreciate it if not I’ll continue to play around.
Thanks
↧
Regenerate/SubmitAll command
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
↧
↧
Working Software for Android?
Bria by Counterpath works good for mobile soft phones, don’t know if it’s on any non google / Apple application stores.
↧
Issue with Misc Destination call forwarding
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
↧
SIP Trunk Issue
Including Sangoma owned VoipInnovations. I love them but would love to see a better updated PJSIP guide. I figured it out on my own, no idea if it’s working 100% well but no complaints so far.
↧