sipXproxy dns issue

[Roy Reynolds]

Hello, 

I get repeated alarm messages from the pbx complaining about dns: No valid 'SRV' records found\"

Suggested Resolution: Check DNS settings. The pbx is it's own dns server and there is no external dns configured. I can only resolve this by restarting the sipxecs services.  The strange thing is the emails with the alarms are sent which suggests that dns is working. 

This seems to happen if the network connection is disrupted but the sipXproxy services don't recover. Calls don't work until the services are restarted and the alarms for my email until the restart is complete. 

Is there a fix for this?

[Support]

We don’t configure SIP SRV records and have seen this warning with no detriment to anything, the lookup logic should just fall back to regular DNS A records. So beware it might be something else causing your problem.

Anyhow, there is a related troubleshooting tip in the wiki here: https://onrelay.github.io/sipxecs/troubleshooting.html

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/f0a60286-7a02-4d1a-8c28-70dc0fc96f42n%40googlegroups.com.

[Roy Reynolds]

Thanks for responding so quickly. 

I can't seem to find the cause but will look through your guide for clues.

[Support]

Are you using STUN? There is perhaps a possibility the STUN lookup fails when your network is down, and doesn’t recheck when network comes back up. 

If so, worth trying to configure your public IP instead, if it is static. 

[Roy Reynolds]

I will double check the stun settings but I believe I already set it to use the ip address of the pbx as the public address. 

The alarms always start with a message saying sipXproxy lost contact with sipxrelay and will give up retrying. The service must be manually restarted. 

I'm not sure how that is possible when both services show that they are running and both are on the same pbx.

The issue is not frequent and can sometimes work for weeks or months without a problem. 

[Support]

That sounds much more like sipXrelay running out of resources and / or memory.

You may want to update the java command in /etc/init.d/sipxrelay with an -Xmx parameter to increase max available memory. 

-Xmx512m is 512M, -Xmx1024m is 1GB, -Xmx2048m is 2GB etc.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/1DCD6164-FE0E-44DC-8FCB-5921DD0B34E6%40onrelay.net.

[Roy Reynolds]

Thanks. I'll check that as well. I can't think of any system over the years that had these issues. Seems to be unique but the cause eludes me. 

[Support]

Oh on older versions we had sipxrelay run out of resource / memory all the time, but not something we have seen on 24.01.

Also sipX doesn’t live in a vacuum and as surrounding networking equipment protocols are updated they may also affect low level sipX resources.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/CALz8TxnaEAc7SThrNVXSkW4xz44ud%2BG%2BBrRVp30zdE02uqTNqQ%40mail.gmail.com.