Changed BindPort now cant register ZoIPER remote ext

[rchase (Reilly Chase)]

dicko!

I got it working. Here’s what I did:

• Read this article on changing bindport

Changing SIP bind port

We have started having a problem with SIP softphone registration happening every few hours for no apparent reason. People will all be working away on the phones, then suddenly no phones can register, I think the ISP is sporadically blocking port 5060 for whatever reason. Otherwise I have no explanation why things are fine, then suddenly not, then fine 30 minutes later. This also started happening right after upgrading our internet speed. We are on an HA system at a hosting company. I want to tr…

• Read this article on SIP over TCP

Tips for FreePBX and android phones

Some great tips here, but I thought I should share a particular issue I found with disabling the “qualify” feature from the extension settings… Without qualify checking that the extension is online, it will take the ringtime (default 15 seconds) before any “forward if unavailable” action takes place. This was a particular issue for me because I wanted Asterisk for forward calls for the Android extension to the Android’s cell network when the phone is not connected directly to the Asterisk serve…

To summarize both articles:

BindPort

1. Set custom BindPort in SIP settings, but also set Bind Address to freepbx local IP (192.168.x.x)
2. amportal restart
3. Ignore extension SIP Port settings, they are ignored because I am using “dynamic IP”
4. Check to make sure it is binding to the port with

Changing SIP bind port

Instead of all this guessing you can run a simple command to see if Asterisk is binding to the port you want it to: netstat -lnp | grep asterisk

TCP:

• In your PBX, Go to Applications–> Extensions → Transport → All TCP - Primary. That’s going to make it use TCP for your extension.
• Still in your PBX, go to Settings → Asterisk SIP settings → Other SIP Settings, and add “tcpenable=yes”. That’s going to allow Asterisk to use TCP connection, otherwise the extension TCP setting is irrelevant.
• In your phone, check “use TCP” box in your SIP app.
• Change the “TCP keep alive” in your SIP app to 1200 seconds, or play with it. That’s right, 1200 seconds is 20 minutes. I’ve found that 15 minutes was not unnecessary, and 30 minutes was to much, gave to much time to unregister.
• Go in your extension settings, and change the qualify option from “yes” to “no”.

Problems Discovered:

This lead me to discover that TCP was not binding to my custom port, but stayed listening on 5060, which is why ZoIPER would not register:

netstat -lnp | grep asterisk

root@raspbx:~# netstat -lnp | grep asterisk
tcp 0 0 192.168.2.200:5060 0.0.0.0:* LISTEN 2968/asterisk
tcp 0 0 127.0.0.1:5038 0.0.0.0:* LISTEN 2968/asterisk
tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 2968/asterisk
tcp 0 0 0.0.0.0:1720 0.0.0.0:* LISTEN 2968/asterisk
udp 0 0 0.0.0.0:4569 0.0.0.0:* 2968/asterisk
udp 0 0 192.1682…200:9997 0.0.0.0:* 2968/asterisk
udp 0 0 0.0.0.0:5000 0.0.0.0:* 2968/asterisk
udp 0 0 0.0.0.0:4520 0.0.0.0:* 2968/asterisk
unix 2 [ ACC ] STREAM LISTENING 3819 2968/asterisk /var/run/asterisk/asterisk.ctl
root@raspbx:~#

This was solved thanks to dicko

Why is FreePBX listening on 5060 for TCP but 9997 for UDP?

Try setting your tcpbindaddress to n.n.n.n:9997 where n.n.n.n is appropriate to your deployment, generally tcpbindaddress=0.0.0.0:9997 will listen to any TCP SIP connections on port 9997 (but no longer on 5060 )

Also, as you can see in my config in original post, I did not put the “domain” settings correctly

it should be

domain Public-IP-of-FreePBXP:custom-bindport (for example 1.1.1:9997)

EVERYTHING IS WORKING EXCEPT

SPA3102 FXS extension STILL will not register since the bindport change. I dont know what to do or why