Asterisk VOIP Sipura/Linksys PAP2T Calls Not Being Received Solution

This problem seemed to happen recently but was likely causing issues before where the phone(s) do not ring.

Now there are a few reasons why this can happen especially if your adapter has DND mode enabled (disable it).

However that wasn't my issue and I only figured it out the other day  when  by fluke if you're on the phone (making a call) then  calls will come in.

That's when I figured out the solution:

This likely applies to other adapters but in a Sipura/Linksys you'll find this under "Advanced" settings for your line.

    NAT Mapping Enable:   NAT Keep Alive Enable:

Enable both of those especialy the Keep Alive as otherwise the PBX/Asterisk/server won't realize your phone is alive and ready to receive calls.

The above seems to have solved it for me.

What if the solution doesn't work or you have 2 lines active on your Linksys VOIP PAP2T?

This happened to me, at first the second line worked when enabling NAT Mapping and Keep Alive like above but then it stopped.  The solution so far was to keep both lines using the same SIP port (5060) whereas the second line that stopped ringing was using 5061 (I changed it back to 5060).

I am not sure if it's an issue with my router or if it's only able to properly NAT VOIP on port 5060 but for now it is working.

I will try to report back in a few days if it is the final/working solution.

*This doesn't work so the solution was actually very short lived

*Update

My problem was solved by enabling NAT but it seemed something else wrong because the phone wouldn't ring.  I had an old Sipura adapter using the same account that was still connecting and booting off the PAP2T!  So no wonder nothing seemed to make it work.  You shouldn't need to open any ports on your router either and mine works without that and wouldn't work with it.

So if you are upgrading from an old adapter make sure you disconnect and put it away to avoid hassle like mine!


Tags:

asterisk, voip, sipura, linksys, pap, solutionthis, adapter, dnd, mode, enabled, disable, wasn, fluke, applies, adapters, ll, quot, advanced, settings, nat, mapping, enable, especialy, pbx, server, doesn, active, enabling, sip, whereas, router, update, wouldn, connecting, booting, shouldn, ports, upgrading, disconnect, hassle,

Latest Articles

  • qemu: could not load PC BIOS 'bios-256k.bin' solution
  • Proxmox How To Custom Partition During Install
  • Hyper-V Linux VM Boots to Black Screen, Storage, NIC Not Found Issues
  • Ubuntu Mint How to Fix Missing/Broken /dev and /dev/pts which causes terminal to immediately close exit and not work
  • How high can a Xeon CPU get?
  • bash fix PATH environment variable "command not found" solution
  • Ubuntu Linux Mint Debian Redhat Youtube Cannot Play HD or 4K videos, dropped frames or high CPU usage with Nvidia or AMD Driver
  • hostapd example configuration for high speed AC on 5GHz using WPA2
  • hostapd how to enable and use WPS to connect wireless devices like printers
  • Dell Server Workstation iDRAC Dead after Firmware Update Solution R720, R320, R730
  • Cloned VM/Server/Computer in Linux won't boot and goes to initramfs busybox Solution
  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm
  • docker swarm silly issues