Vodia PBX Posted February 28, 2012 Report Share Posted February 28, 2012 I dont see anything special about that DNS address: $ host -t NAPTR voip.eutelia.it $ host -t SRV _sips._tcp.voip.eutelia.it Host _sips._tcp.voip.eutelia.it not found: 3(NXDOMAIN) $ host -t SRV _sip._tcp.voip.eutelia.it Host _sip._tcp.voip.eutelia.it not found: 3(NXDOMAIN) $ host -t SRV _sip._udp.voip.eutelia.it _sip._udp.voip.eutelia.it has SRV record 0 0 5060 voip.eutelia.it. $ host -t AAAA voip.eutelia.it $ host -t A voip.eutelia.it voip.eutelia.it has address 83.211.227.21 Quote Link to comment Share on other sites More sharing options...
dario Posted March 3, 2012 Report Share Posted March 3, 2012 I dont see anything special about that DNS address: $ host -t NAPTR voip.eutelia.it $ host -t SRV _sips._tcp.voip.eutelia.it Host _sips._tcp.voip.eutelia.it not found: 3(NXDOMAIN) $ host -t SRV _sip._tcp.voip.eutelia.it Host _sip._tcp.voip.eutelia.it not found: 3(NXDOMAIN) $ host -t SRV _sip._udp.voip.eutelia.it _sip._udp.voip.eutelia.it has SRV record 0 0 5060 voip.eutelia.it. $ host -t AAAA voip.eutelia.it $ host -t A voip.eutelia.it voip.eutelia.it has address 83.211.227.21 You don't see anything special about that DNS address... But i can tell you that if I set the proxy address as "voip.eutelia.it" I have the problem; if I set "83.211.227.21" I don't have the problem. Any idea? Thanks Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 3, 2012 Report Share Posted March 3, 2012 We had cases where there were so many DNS entries for records that the UDP packet got too big. Thats not the case here. We have seen a lot of other cases, where DNS servers were simply buggy, e.g. could not handle NAPTR, SRV or AAAA requests and that was causing issues. Especially when using DNS servers from small, cheap DSL or cable modem routers, chances are that they mingle the DNS packets up. Usually it helps to use a public DNS server instead (e.g. 8.8.8.8 from Google). Quote Link to comment Share on other sites More sharing options...
dario Posted March 5, 2012 Report Share Posted March 5, 2012 I have changed the DNS in 8.8.8.8, but i still have the problem... Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 5, 2012 Report Share Posted March 5, 2012 Really hard to say... Only PCAP will tell us what is going on on the network level. If not too inconvenient, can you run Wireshark and send me a private message with the link to the data? Quote Link to comment Share on other sites More sharing options...
dario Posted March 10, 2012 Report Share Posted March 10, 2012 Really hard to say... Only PCAP will tell us what is going on on the network level. If not too inconvenient, can you run Wireshark and send me a private message with the link to the data? According to snom support, i have updated the software to 2011-4.5.0.1016 Alpha Monocerotids version and now the system is ok. Thank you anyway. Dario Quote Link to comment Share on other sites More sharing options...
Bela Posted May 5, 2012 Report Share Posted May 5, 2012 Its weird I am experiencing similar problems with the latest version (2011-4.5.0.1050 Coma Berenicids (Win64)) installed. Any ideas? Bela Quote Link to comment Share on other sites More sharing options...
pbx support Posted May 7, 2012 Report Share Posted May 7, 2012 Do you mean you trunk is getting de-registered or something else? Quote Link to comment Share on other sites More sharing options...
skyplonk Posted May 7, 2012 Report Share Posted May 7, 2012 I don't know about the Beta but I have customers on 5021 and if the internet goes out at one of my customers, then comes back some time later, the trunk stays 408 until someone manually clicks the register button. The worst part is I don't get an email in this instance because the PBX also thinks the email has been sent. I will disconnect my company PBX from the network tonight (It has the new Beta) for 15 minutes and see if it reconnects after I connect it back to the network. We get this a lot now. Used to get it all the time in early version 4 builds, Went away for a long time, but seems to be happening again. Might be just coincident. If we hard code to a proxy with its IP it is never an issue, if we have it pointing to the FCDN of the server after the connection is backup it sits on "408 Request timed out - Retry in 60 seconds", but never does. If we hit "Register" it is fine. We don't want to hard code to the IP of the server as we have SRV entries on the Domain Name and some failover/load balancing setup. If we hard code to 1 server we loose redundancy. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 8, 2012 Report Share Posted May 8, 2012 The alternative might be to try a local DNS server (in the LAN). If that is not too much work, you could try that, and make sure that the server keeps the relevant entries in the case, so that the PBX does not have to worry about slow DNS responses. Quote Link to comment Share on other sites More sharing options...
pbx support Posted May 8, 2012 Report Share Posted May 8, 2012 Are these TCP based registrations or UDP? There was an issue in the low level TCP layer in the last version(symptom was TCP CDR stopped working). Just wanted to see if that is the case here too. This problem has been fixed. If both are related, then this should be fixed too. We are releasing the new version later today. Quote Link to comment Share on other sites More sharing options...
skyplonk Posted May 8, 2012 Report Share Posted May 8, 2012 Ours are UDP registrations. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.