12-06-2014 09:52 PM - edited 03-21-2019 10:21 AM
I have a SPA3102 that I am using only the FXS (Line 1) and trying to register to FreePBX
- SPA3102 IP address 192.168.9.203
- FreePBX IP address 192.168.9.204
It works fine when I use port 5060 on the FreePBx, but I changed the SIP bindport on FreePBX to, lets say, 9901, in order to hide it from internet attacks.
So the FreePBX expects the SPA3102 to register its extension to SIP Port 9901, and will ignore requests to 5060.
Simple enough, but when I change the SIP Port in the FXS (Line 1) settings of the SPA3102, it doesn't register.
So I opened up wireshark and saw that the SPA3102 was doing something strange --
As you can see, it is using the "SIP Port" value as the port it is COMING FROM instead of SENDING TO
What gives? I hope this can be fixed.
Thanks!
12-06-2014 10:31 PM
Theres no bug!
I made the FXS register by adding the custom port after the IP in the PROXY SETTING of SPA3102
For example
PROXY 192.168.2.204:9901
(FreePBX-IP:FreePBX-custom-bindport)
See this forum for more info
http://community.freepbx.org/t/cant-get-fxs-on-spa3102-to-register-after-bindport-change/25999/12
12-07-2014 04:07 PM
Just to rephrase the answer
There are two ports involved. The port you are sending to and the port you are sending from. There is absolutely no requirement that they be the same number.
The Sip Port: setting on the SPA3102 Line Tab refers to the port you are sending from.
You put the port you are sending to in the Proxy address as the other post indicated, i.e. 192.158.9.204:9901
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide