[asterisk-bugs] [JIRA] (ASTERISK-25858) Early media not processed when received ACM with some conditions

[Igor Nikolaev (JIRA)]

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

Igor Nikolaev updated ASTERISK-25858:
-------------------------------------

    Attachment: sig_ss7.c.patch
                libss7.h.patch
                isup.h.patch
                isup.c.patch

In this patches we do:
- implement processing optional backward call indicators in libss7 module;
- implement processing called party's indicator 'no indication' value with set inband ready indication on the optional backward call indicators.


> Early media not processed when received ACM with some conditions
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-25858
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25858
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi/SS7
>    Affects Versions: 13.0.0, 13.0.1, 13.0.2, 13.1.0, 13.1.1, 13.2.0, 13.2.1, 13.3.0, 13.3.1, 13.3.2, 13.4.0, 13.5.0, 13.6.0, 13.7.0, 13.7.1, 13.7.2
>         Environment: libss7-2.0.0
> SS7 digital trunk environment
>            Reporter: Igor Nikolaev
>              Labels: SS7
>         Attachments: bad.pcap, isup.c.patch, isup.h.patch, libss7.h.patch, sig_ss7.c.patch
>
>
> If we making outbound call via SS7 and after sending ISUP IAM we got ACM with following conditions:
> Backward call indicators contain called party's status indicator "no indication" (i.e. == 0);
> Optional backward call indicators contain in-band information indicator (i.e. == 0x01);
> we must do a PROGRESS SIP message and start early media channel.
> Required procedure described at the ETSI ES 283 027 V1.4.0 (2007-09) in section 7.2.3.1.4a Sending of 183 Session Progress for early media scenarios.



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