Summary: | ASTERISK-27664: Register doesn’t work properly in Asterisk Realtime - not ringing calls ocasionally | ||||
Reporter: | LEANDRO MORAES DE OLIVEIRA (lmoraes.oliveira) | Labels: | |||
Date Opened: | 2018-02-09 13:44:08.000-0600 | Date Closed: | 2018-02-09 13:49:04.000-0600 | ||
Priority: | Major | Regression? | No | ||
Status: | Closed/Complete | Components: | Channels/chan_sip/Registration | ||
Versions: | 13.18.5 | Frequency of Occurrence | Occasional | ||
Related Issues: |
| ||||
Environment: | Attachments: | ||||
Description: | I have an Asterisk server 13.18.5 installed in an Ubuntu 16.04 LTS in an Amazon cloud that was working properly until I try to enable the Asterisk Realtime to use Mysql database.
I made a lot of tests, in many situations work properly, but sometimes (1x30) I lost the register of the client and the calls are not delivered, and in the server return it: [2018-02-09 09:32:23] WARNING[6142]: chan_sip.c:4072 retrans_pkt: Retransmission timeout reached on transmission 5aa7afc34fa9290b5b4967a966462a91@54.94.200.147:5060 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions I already use rtcachefriends=yes, rtsavesysname=yes and rtkeepalive=30. When I didn’t use RealTime I solved it with register=>4701006:password@10.120.23.24/4701006 now when I use this command the calls was not delivered and say that the phone is in loop detected: -- Got SIP response 482 Loop Detected back from IP_OF_MY_SERVER -- SIP/BuyDIDHub-0000069e is circuit-busy == Everyone is busy/congested at this time (1:0/1/0) And then the call down. | ||||
Comments: | By: Asterisk Team (asteriskteam) 2018-02-09 13:44:08.980-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Asterisk Team (asteriskteam) 2018-02-09 13:44:09.638-0600 The module you are reporting the issue against is no longer supported as a core module but your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties |