[asterisk-bugs] [JIRA] (ASTERISK-22791) asterisk sends Re-INVITE after receiving a BYE

[Paolo Compagnini (JIRA)]

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

Paolo Compagnini commented on ASTERISK-22791:
---------------------------------------------

i can confirm that my asterisk with applied patch passes the test in r4055

sadly i have no access to my old test scenario, so i can't confirm that it will work in this case.

I want to try something similar to what r4055 was doing first( sipp without pcapplay). But instead of Bob I want to use faxreceive() in extension.conf. 

alice INVITE -> asterisk
asterisk 200 OK  -> alice
alice reINVITE with t38 -> asterisk
asterisk 200OK -> alice
the fax transmission will  fail because there is no stream and asterisk would switch back to audio (befor ending the call) right ? So
asterisk reINVITE -> alice
alice 491 -> asterisk
alice BYE -> asterisk
Wait for asterisks behaviour 

What do you think ? 

i am going in vacation in a couple of hours and will return in one week. You probably won't hear anything from me until I return.










> asterisk sends Re-INVITE after receiving a BYE
> ----------------------------------------------
>
>                 Key: ASTERISK-22791
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22791
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Channels/chan_sip/T.38, Resources/res_fax
>    Affects Versions: 11.6.0
>            Reporter: Paolo Compagnini
>            Severity: Trivial
>         Attachments: debug, messages, scrubed_messages, sip.conf
>
>
> i am receiving faxes with receiveFAX().
> after transmitting the document with t38 asterisk changes back to g711.
> Sometimes it happens that even after receiving a BYE asterisk is sending these Re-INVITEs.
> i can provide a sip trace but i don't wanna share it in public.



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