Sorry, in advance

[ednunnemaker]

OK, I have searched and searched with no success, so I'm sorry if this is a duplicate post. Here are my issues, which I have come to the conclusion are all related somehow.

1) Nothing outside my private network will stay connected or monitored, it doesn't matter if its sip, iax, an extension or trunk, it will register but soon after it shows in the asterisk info that it is unreachable and unmonitored. Yes I have a static IP address, yes I have turned off IPTables, yes I have ALL the ports open on my sonicwall firewall. I CAN make calls from any trunk or extension but cannot receive anything if it has been registered for more than a few seconds and it appears they don't try to re register at any time or they are somehow blocked from re registering.

2) The FOP just has flashing red and green icons (even for the internal stuff) and refreshes every couple of seconds, like it cannot retrieve the status of any trunk or extension.

3) My Les.net DID's will not ring, I just get dead air (I am assuming this has something to do with #1 above)

4) I still have the Ultimate Cnam problem when I have it selected as the lookup source the notification email is plain text with no attachment.

With my limited knowledge about Linux and networking I am at a stand still, all these issues seem to relate to registration or lack there of, maybe someone could at least point me in the right direction.

 

[frontline]

Curious whether your les.net trunk shows an IP in the registered area on the les.net control panel. It should be indicated whether you are in fact negotiating a register or using a public IP.

You say you can terminate calls from any extension/trunk. Are these calls all from instruments located on the same LAN as the server?

The appropriate ports must not only be open on sonicwall but also forwarded to your server.

 

[ednunnemaker]

yes it shows registered on the les.net website, in my asterisk info tab it shows registered but unmonitored, I'll throw up a screen shot in a sec.

 

[frontline]

yes it shows registered on the les.net website, in my asterisk info tab it shows registered but unmonitored, I'll throw up a screen shot in a sec.

On the info tab it will be unmonitored unless you put the qualify option in the trunk configuration. That would not be an indicator of this problem.

I edited my earlier post re. port forwarding..

 

[ednunnemaker]

here are the screen shots

here are the screen shots of les.net and asterisk info

 

[ednunnemaker]

the ports are open and forwarded, everything coming in is sent to the PiaF server via forwarding, I do always have the qualify=yes option for all extensions and trunks.

 

[frontline]

Still curious whether all the successful calls are being placed from the same LAN as the server. Every indication I see is that the firewall is not open for whatever reason. Also you may need to search for the correct setting in sip.conf for your particular LAN/NAT setup.

 

[ednunnemaker]

yes all internal (same lan) calls work its everything outside the private network that has issues, i have set up in sip_custom.conf

externip=xx.xxx.xxx.xxx
localnet=192.168.xxx.x/255.255.xxx.xx
nat=yes
externrefresh=10

I thought something with the server registrations was the issue based on the FOP panel and Ultimate CNAM not working correctly.

 

[frontline]

What is showing in the SIP registry section of the info page? Or look at "sip show registry" in the asterisk CLI/

 

[ednunnemaker]

I'm rebuilding the sonicwall configuration, to see if that helps, I may have missed something, I'll post my results when done, thank you for the help so far.

 

[jroper]

Hi

I think you are on the right track with the firewall.

One of the symptoms of network connectivity issues is a flashing FOP panel, which usually means that port 4445 is not open.

Joe

 

[ednunnemaker]

I can't fn beleive it

Well thank you all for the help, it was the firewall, i replaced it with another one with the exact same settings and low and behold everything works as it should. i guess that just goes to show that just because the Configuration is correct doesn't mean the hardware is good. I bet this will solve a lot of my "other" issues as well, for everyone that has unexplainable issues check your hardware. Thanks again, I could have reprogrammed that firewall for a week and never gotten it to work.

 

[darmock]

Sonic firewalls use something called stateful packet inspection (to the best of my recollection and this needs to be disabled. I am pulling this from the dregs of my memory and I could be wrong but it seems to me if this is turned off all of the problems magically disappear. That being said I am prepared to be wrong.

Tom