Asterisk 1.4.31 IAX2/RSA BUG If "A" tries to register on "B" and the RSA key from "A" does not match the key on "inkeys" on "B", "B" do not send a "REGREJ", instead it sends a "REGAUTH" with a new "CHALLENGE", then "A" send a new "REGREQ" for this "CHALLENGE" with the same wrong RSA key and it loops forever on this (with a storm of REGREQ <--> REGAUTH packets).
The same was true in version 1.2.31.1, but was corrected in a patch. (see issue 14386 <https://issues.asterisk.org/view.php?id=14386>). I tested some patches but nothing worked. The console from the server ("B") will be flooded with this: [May 31 07:37:43] NOTICE[3774] chan_iax2.c: No registration for peer 'pfcliente' (from 189.19.36.253) [May 31 07:37:43] NOTICE[3770] chan_iax2.c: No registration for peer 'pfcliente' (from 189.19.36.253) [May 31 07:37:43] NOTICE[3766] chan_iax2.c: No registration for peer 'pfcliente' (from 189.19.36.253) [May 31 07:37:43] NOTICE[3768] chan_iax2.c: No registration for peer 'pfcliente' (from 189.19.36.253) [May 31 07:37:43] NOTICE[3771] chan_iax2.c: No registration for peer 'pfcliente' (from 189.19.36.253) ------------------------------------------------------------------------------------------------------------------------------------------------------------------ André Magalhães "May the Source be With You!" Linux user #433396 http://counter.li.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
