| Summary: | ASTERISK-25979: res_pjsip: Weird flood of traffic when authentication fails on TCP | ||
| Reporter: | Mark Michelson (mmichelson) | Labels: | |
| Date Opened: | 2016-05-02 13:36:41 | Date Closed: | |
| Priority: | Major | Regression? | No |
| Status: | Open/New | Components: | Resources/res_pjsip |
| Versions: | 13.8.2 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | This was discovered during the process that found ASTERISK-25978.
* Set up two Asterisk boxes so they can call each other using chan_pjsip over TCP. * Have the client Asterisk originate a call to the server Asterisk. * Have the server Asterisk reject the call due to failed authentication. In our case, the bug in ASTERISK-25978 caused this. What ensues is that the client Asterisk will re-attempt the call a BUNCH of times after the initial authentication rejection, resulting in a flood of traffic between the two Asterisk servers. Eventually the client will stop attempting calls because the PJSIP stack returns an ETOOMANY error during an operation. While this was observed as the result of another open issue, this presumably could happen with any UAS that rejects our authentication credentials. Asterisk should attempt authentication once, and if that authentication is rejected, there should be no further attempts to complete the call. | ||
| Comments: | |||