[asterisk-bugs] [JIRA] (ASTERISK-28634) Invite loop within PJSIP

[Joeran Vinzens (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249686#comment-249686 ] 

Joeran Vinzens commented on ASTERISK-28634:
-------------------------------------------

We have some problems reproducing the issue and provide logs. (without any customer relevant content)

We do have this issue frequently but sporadic in our production environment. We took the SIP Messages from this call and configured SIPP with that but we were not able to reproduce.

Are there any more debug flags we can switch on to see why this occur? In the logs you cannot see any reason why just that there is a reinvite in PJSIP logger.

At the moment we use Asterisk 17.1 in production where we see this issue.

> Invite loop within PJSIP
> ------------------------
>
>                 Key: ASTERISK-28634
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28634
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 17.0.0
>         Environment: Asterisk 17.0.0 with bundled PJSIP on Debian Buster
>            Reporter: Joeran Vinzens
>         Attachments: asterisk_invite_loop_other_side.pcap, invite_loop_small.pcap, pjsip.conf, Screenshot from 2019-11-26 10-19-59.png
>
>
> Fom time to time we can see traffic increase on out Asterisk Systems. After some debugging we see the Asterisk send kind of an Invite loop over and over. Since there is no way to deny re-invites in PJSIP there is no way out of it. From asterisk perspective it sends these re-invites as fast as it can which result in an increase of 3MBit/s of signalling traffic from this maschine. So far we do not know how to reproduce the issue but we captured the scenario from our production system. (trace attached) the Asterisk log itself just tells us the Invite is going out but nothing further. There was no trigger on the other call-leg.



--
This message was sent by Atlassian JIRA
(v6.2#6252)