Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Highlighted
New Member

SPA3102 FXS bug? Will not send to SIP Port other than 5060

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!

2 REPLIES
New Member

Theres no bug! I made the FXS

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

Just to rephrase the

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

159
Views
0
Helpful
2
Replies
CreatePlease login to create content