| Summary: | ASTERISK-19997: Faulty asterisk sip registrations - cause incoming network buffer to rise | ||
| Reporter: | Maciej Krajewski (jamicque) | Labels: | |
| Date Opened: | 2012-06-14 04:41:48 | Date Closed: | 2012-06-26 08:33:25 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
| Versions: | 1.8.13.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) full | |
| Description: | I've made some testing, and I've found out that when asterisk tries to register to a peer which do not answer and during this registration other users tries to register to asterisk the incoming buffer on network card rises. Sometimes such behaviour coses asterisk to loose user registrations or not to process incoming calls. I would attach logs, but on debug there is no info that could help to solve this issue. Buffers are checked with "netstat -nacp" command. | ||
| Comments: | By: David Woolley (davidw) 2012-06-14 05:22:15.517-0500 You definitely need to provide debugging output. My initial impression is that this is a problem with the network card driver, and nothing to do with Asterisk. By: Maciej Krajewski (jamicque) 2012-06-14 05:23:52.324-0500 Tested on 5 different server configurations. I will provide output in a sec. By: Maciej Krajewski (jamicque) 2012-06-14 06:35:08.713-0500 Ok - I've made some additional tests, and my description was not complete. The issue only occurs when asterisk tries to register on domain name, and DNS is not responding. When such situation occurs the buffor rises. the full log is attached. udp 0 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 3496 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 5244 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 5244 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 6992 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 6992 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 6992 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 6992 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 8740 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 8740 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 8740 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 8740 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 10488 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 10488 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 10488 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 12236 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 12236 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 12236 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 12236 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 13984 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 13984 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 13984 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk udp 13984 0 0.0.0.0:5060 0.0.0.0:* 30990/asterisk By: Maciej Krajewski (jamicque) 2012-06-14 06:51:14.461-0500 I've also noticed that during registration timeout this buffer also rises, however not as much. By: Matt Jordan (mjordan) 2012-06-26 08:33:17.879-0500 If you attempt to register to a hostname and DNS does not respond, Asterisk will typically continue to attempt to register to that hostname. In addition, because Asterisk does not perform DNS lookups asynchronously, various services can block when this occurs - so I would expect you would see buffer increases at the network layer. As such, I do not think this is a bug with Asterisk, but rather a system configuration issue. | ||