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

[Benjamin Keith Ford (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Keith Ford updated ASTERISK-28634:
-------------------------------------------

    Assignee: Joeran Vinzens
      Status: Waiting for Feedback  (was: Triage)

Can you provide your pjsip.conf file? Do you know what's going on at the time when the re-invites begin, such as channels being put on hold, or topology changes that could result in the need for a re-invite?

I'm going over the pcap currently to see if there's any additional information to be gathered from there. Can you specify which IP address belongs to what? And is the scenario Asterisk and another phone, or some other setup?

> 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
>            Assignee: Joeran Vinzens
>         Attachments: invite_loop_small.pcap, 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)