Ok my first freePBX install has gone smoothly until now. I got the PBX installed, our extension numbers, ring groups, IVR, follow me, etc. All internally working. Setup the trunk, got outbound working. Been reading and I like IAX because of its flexibility and security. Please feel free to change my mind.
I could not for the life of me figure out why I can’t get inbound working.
I see in my provider’s portal (voip.ms) that the server is registered. I’ve opened the IAX port to the server but it’s not showing.
The troubleshooting steps I took are this. From this point forward I tested only by calling the DID or using advanced port checker. Tested DID with a quality test. Then forwarded it to IAX sub account.
My setup is as follows. Unraid build with freePBX install on a VM. Other VMs not having any problem, so I never tested anything with VM or host machine.
First I opened all ports in router and checked open ports by scanning for UDP 4569 on my machine via the local network. Doesn’t show open. 5060 does, but not even 80 does. But the web interface does work. Does the build of PBX not allow for port scanning? What should I see?
I did netstat and saw all ports I wanted were listed.
So I decided there might be an issue with router port forwarding. After I disabled the firewall I decided to DMZ it temporarily and see the results. I’m picking up the web interface on port 80 externally. Tried calling the DID with no luck.
I decided to try and do all the previous with SIP instead because the port was open. Routed my DID to the main account and created a new trunk which registered no problem. Then tested DID with no luck.
So I have a few questions for the community.
Should I use SIP or IAX? Which is most secure?
Will Advanced Port Scanner be able to see UDP ports 4569, 5060 and 5160? Why can I only see 5060? Is there any additional configuration in freePBX for opening those ports?
If port scanners don’t work is there other tools I can use to test where the issue exists?
Is there a way to test the inbound on my desk phone to ensure it’s the FreePBX server as I suspect or if it’s my network or ISP?
Does anyone know where I messed up?
Check your logs.
If I were registered, but not receiving any inbound I’d look for my freepbx inbound route and trunk configuration.
For voipms and half a dozen other providers on a physical server, ice never had to open or forward any ports on my router.
Feeling dumb thinking back I only setup for local during testing I never added the provider once we got the DID. Because I’m new could you guys tell me best way to view logs, should I pull the file? Is there a way to view live traffic? Any tools you guys can recommend for troubleshooting?
Ok, so I closed the ports, I just assumed I needed them open. Still no luck, busy signal on the number. This is the log of me changing from an incorrectly configured trunk to one that shows registered on the remote server. I do have a SIP trunk which isn’t connected right now. It was for testing I couldn’t get inbound calls working on that either. I attempt a call which doesn’t appear to show in the logs:
[2018-06-10 12:47:40] ERROR[11842] netsock2.c: Unknown address family ‘0’.
[2018-06-10 12:47:40] WARNING[11842] netsock2.c: Port disallowed in 'XX.XX.XX.147:4569
[2018-06-10 12:47:40] WARNING[11842] acl.c: Unable to lookup '‘XX.XX.XX.147:4569’
[2018-06-10 12:47:40] WARNING[11842] iax2/firmware.c: Error opening firmware directory ‘/var/lib/asterisk/firmware/iax’: No such file or directory
[2018-06-10 12:47:40] NOTICE[11842] iax2/provision.c: No IAX provisioning configuration found, IAX provisioning disabled.
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘chan_motif.so’ (Motif Jingle Channel Driver)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/motif.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/motif_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘chan_sip.so’ (Session Initiation Protocol (SIP))
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘chan_dahdi.so’ (DAHDI Telephony w/PRI & SS7 & MFC/R2)
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘res_adsi.so’ (ADSI Resource)
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘res_pjsip_notify.so’ (CLI/AMI PJSIP NOTIFY Support)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/pjsip_notify.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/sip_notify_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/sip_notify_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘res_pjsip_outbound_registration.so’ (PJSIP Outbound Registration Support)
[2018-06-10 12:47:40] ERROR[11842] res_pjsip_config_wizard.c: Unable to load config file ‘pjsip_wizard.conf’
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_confbridge.so’ (Conference Bridge Application)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/confbridge.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/confbridge_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/confbridge_custom.conf’: Found
[2018-06-10 12:47:40] NOTICE[11842] confbridge/conf_config_parser.c: Adding default_menu menu to app_confbridge
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_meetme.so’ (MeetMe conference bridge)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/meetme.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/meetme_general_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/meetme_general_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/meetme_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] chan_sip.c: Reloading SIP
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘cel_manager.so’ (Asterisk Manager Interface CEL Backend)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_general_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel_general_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel_general_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_general_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel_custom_post.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_nat.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_registrations_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘cel_odbc.so’ (ODBC CEL backend)
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel_odbc.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_registrations.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/cel_odbc_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_custom_post.conf’: Found
[2018-06-10 12:47:40] WARNING[2253] chan_sip.c: Failed to bind to 0.0.0.0:5060: Address already in use
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_notify.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_notify_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[2253] config.c: Parsing ‘/etc/asterisk/sip_notify_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] cel_odbc.c: Found CEL table cel@asteriskcdrdb.
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_playback.so’ (Sound File Playback Application)
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_voicemail.so’ (Comedian Mail (Voicemail System))
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/voicemail.conf’: Found
[2018-06-10 12:47:40] WARNING[11842] app_voicemail.c: maxsilence should be less than minsecs or you may get empty messages
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_flite.so’ (Flite TTS Interface)
[2018-06-10 12:47:40] WARNING[11842] app_flite.c: Flite: Unable to read config file flite.conf. Using default settings
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘codec_dahdi.so’ (Generic DAHDI Transcoder Codec Translator)
[2018-06-10 12:47:40] VERBOSE[11842] loader.c: Reloading module ‘app_queue.so’ (True Call Queueing)
[2018-06-10 12:47:40] NOTICE[11842] app_queue.c: queuerules.conf has not changed since it was last loaded. Not taking any action.
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues_general_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues_custom_general.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues_additional.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] config.c: Parsing ‘/etc/asterisk/queues_post_custom.conf’: Found
[2018-06-10 12:47:40] VERBOSE[11842] asterisk.c: Remote UNIX connection disconnected
[2018-06-10 12:47:40] NOTICE[2248] chan_iax2.c: Peer ‘voipms’ is now REACHABLE! Time: 43
[2018-06-10 12:47:40] VERBOSE[2241] chan_iax2.c: Registered IAX2 to ‘XX.XX.XX.147:4569’, who sees us as XX.XX.XX.188:4569 with no messages waiting
why are you using aix to connect to voip.ms - use chan sip. follow their setup instructions exactly and assuming you do have an inbound route set up it will work fine. just make sure that you are pointing your trunk to the server that has your did (.i.e. losangles or newyork or where ever you have your did set to) if you register to the wrong server I think you can make outbound calls but inbound will not work
After about 30 minutes worth of research I’ve determined IAX is safer and will be more flexible down the road. I’ve got it working with that advice. I didn’t realize all servers not available for IAX so I picked a different server and all was well.