Is your profile listening on port 32060 <http://175.159.77.82:32060/> ? you can run on the cli "sofia status profile [your-profile]" and you will get a response including your URL which should include the port number. You can also run: netstat -putan if you're on debian, that should show the ports in use, and freeswitch should show up there. also, you can use ngrep: ngrep -qW byline port 32060 and that would show ANY packet coming and going to that port... - if you see the responses going out and they don't, there's a problem on the path and someone is blocking it. - if you don't see ANY request coming in from your client's IP, the someone is blocking it. hope this helps ᐧ Regards, David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 On Thu, Jan 11, 2018 at 9:39 PM, Brian West <brian@freeswitch.com> wrote:

we have no filters like that, sounds like a network path issue.

/b

On Thu, Jan 11, 2018 at 9:47 AM, Alex Lake <alex@digitalmail.com> wrote:

...

Hi,

Got a problem with a handset that doesn't seem to be registering on our Freeswitch server. The diagnostics from a member of Cisco support said...

"At packet 422 we see the phone "0_4147057716@192.168.40.26" <0_4147057716@192.168.40.26> send a registration request to 5.9.36.113:5060 from 175.159.77.82:32060 - We do not see a reply to this from the SIP provider.

We responses to requests from 0_359240637@192.168.40.26 with source port 5060, which suggests to me that the SIP provider is not replying to the high UDP port requests. As the MX is a NAT device, subsequent SIP requests will always have a high UDP port."

I'm not sure where we might configure acceptable ranges of SIP source or if it's something else.

Thanks for any suggestions...

Alex

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com

Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

--

Brian West | Co-founder and Developer

Need Commercial support? email sales@freeswitch.com

FreeSWITCH Solutions | 17345 Civic Drive #2531 Brookfield, WI 53045 <https://maps.google.com/?q=17345+Civic+Drive+%232531+Brookfield,+WI+53045&entry=gmail&source=g>

Email: brian@freeswitch.com

Mobile: 918-424-9378 <(918)%20424-9378>

Website: https://www.FreeSWITCH.com <https://www.freeswitch.com/>

[image: color-facebook-96.png] <https://www.facebook.com/freeswitch/>[image: color-twitter-96.png] <https://twitter.com/freeswitch?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor>

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com

Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

AFAIK, Meraki does not have a SIP/ALG. Did you check for any FW or IDS policy that could affect the SIP flows ? Did you check the logs from the FW/IDS to see if packets are rejected ? On the FS side, you could try adding: <variable name="sip-force-contact" value="NDLB-connectile-dysfunction"/> or <variable name="sip-force-contact" value="NDLB-connectile-dysfunction-2.0"/> in the user account. Le 15 janv. 2018 à 11:46, Alex Lake a écrit :

I'm beginning to think that this high port number thing is a red herring. The router in question is a Meraki and it seems to have trouble allowing more than one SIP client to register with freeswitch (maybe a NAT/ALG issue)- is this some kind of FAQ?

On 11/01/2018 15:47, Alex Lake wrote:

...

Hi,

Got a problem with a handset that doesn't seem to be registering on our Freeswitch server. The diagnostics from a member of Cisco support said...

"At packet 422 we see the phone "0_4147057716@192.168.40.26" send a registration request to 5.9.36.113:5060 from 175.159.77.82:32060 - We do not see a reply to this from the SIP provider.

We responses to requests from 0_359240637@192.168.40.26 with source port 5060, which suggests to me that the SIP provider is not replying to the high UDP port requests. As the MX is a NAT device, subsequent SIP requests will always have a high UDP port."

I'm not sure where we might configure acceptable ranges of SIP source or if it's something else.

Thanks for any suggestions...

Alex

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com

Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com

Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com

FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org