Ganesh Posted February 10, 2012 Report Posted February 10, 2012 Hi, Our customer is using snomONE version 4.2.0.3958 (Linux)and everthing was working fine. Today they are unable to call between the extensions. The snom phone displays the message as "Temporarily unavailable". In the PBX logs we see "DoS protection: Not accepting more calls" Let me know how we can fix this problem. We are using version 4.2.0.3958 (Linux. Regards Ganesh Quote
Vodia PBX Posted February 10, 2012 Report Posted February 10, 2012 Well, that means that there are too many calls within a short time. You can increase the value of max_udp_invite or use TCP for SIP. Quote
Ganesh Posted February 10, 2012 Author Report Posted February 10, 2012 Well, that means that there are too many calls within a short time. You can increase the value of max_udp_invite or use TCP for SIP. Thanks. Let me know how we can increase this value (max_udp_invite). Is this value in the snomONE configuration settings? Regards, Ganesh Quote
pbx support Posted February 10, 2012 Report Posted February 10, 2012 You have to change this in the pbx.xml file (this is not exposed to the web pages). You can change this either manually editing the pbx.xml (then you need to restart the PBX) or using the "Global configuration file" method (Syntax is here - http://wiki.snomone.com/index.php?title=Global_Configuration_File:) Quote
Vodia support Posted February 10, 2012 Report Posted February 10, 2012 Can you check your access list for malicious IP as well. Quote
pklausner Posted July 23, 2014 Report Posted July 23, 2014 I run into the same error with a PBX which (so far) was basically idle: just 3 phones plus one firewalled SIP trunk. So there really, really are not too many calls and no malicious IP is involved. What are the expected default values for this max_udp_invite? Quote
Vodia PBX Posted July 24, 2014 Report Posted July 24, 2014 The max_udp_invite setting is limiting how many requests the system accepts per second on UDP transport layer. This is simply about situations when the system gets flooded with INVITE requests. There are other settings how many calls you can have per system, or domain and even per extension. The log should show you why ca call gets rejected. Quote
pklausner Posted July 25, 2014 Report Posted July 25, 2014 For the record: as the PBX was up for ~9 months, I simple restarted it. This cleared the issue. The log was not really helpful in this case, see: [8] 20140722141631: HTTP/NTP/SNMP client waited for 60 s[5] 20140722141657: Identify trunk (IP address/port and domain match) 4[5] 20140722141837: Last message repeated 4 times[3] 20140722141837: DoS protection: Not accepting more calls[5] 20140722141857: Identify trunk (IP address/port and domain match) 4[8] 20140722141927: Trunk 4: Preparing for re-registration[8] 20140722141927: Trunk xxx: Sending registration to xxx.xx[8] 20140722141927: Answer challenge with username xxx[8] 20140722141927: Trunk 4: setup callback to send re-registration after 240 seconds[5] 20140722141927: Identify trunk (IP address/port and domain match) 4 Quote
Vodia PBX Posted July 25, 2014 Report Posted July 25, 2014 Is the PBX running on public IP (exposed to scanners)? In that case you could really experience the DoS protection. Even after 9 months it should not deteriorate. For the record, which version is this? Quote
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.