[asterisk-bugs] [JIRA] (PRI-182) Tighten mandatory ie checks

[Kevin Harwell (JIRA)]

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

Kevin Harwell updated PRI-182:
------------------------------

    Description: 
Libpri is lax in checking if a missing channel identification ie is mandatory for the SETUP ACKNOWLEDGE, PROCEEDING, ALERTING, and CONNECT messages. That ie is mandatory when those messages are the first response to a SETUP message sent by the CPE side.

Make coding errors in mandatory ie's send a STATUS with cause 100 "Invalid information element contents" in response. Also fix detection of coding errors in channel identification ie.

Other misc items to fix:

Update ALERTING_NO_PROGRESS conditional code.
Make it not recognize ie 0x01 for switches other than 4ESS, 5ESS, NI2, and DMS-100.
Send STATUS messages when receiving messages in the wrong call state.
Send DM and DISC frames with only three data octets instead of an extra fourth octet.


  was:
Libpri is lax in checking if a missing channel identification ie is mandatory for the SETUP ACKNOWLEDGE, PROCEEDING, ALERTING, and CONNECT messages. That ie is mandatory when those messages are the first response to a SETUP message sent by the CPE side.

Make coding errors in mandatory ie's send a STATUS with cause 100 "Invalid information element contents" in response. Also fix detection of coding errors in channel identification ie.


> Tighten mandatory ie checks
> ---------------------------
>
>                 Key: PRI-182
>                 URL: https://issues.asterisk.org/jira/browse/PRI-182
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 1.4.13
>            Reporter: Kevin Harwell
>            Assignee: Richard Mudgett
>      Target Release: 1.5.0
>
>
> Libpri is lax in checking if a missing channel identification ie is mandatory for the SETUP ACKNOWLEDGE, PROCEEDING, ALERTING, and CONNECT messages. That ie is mandatory when those messages are the first response to a SETUP message sent by the CPE side.
> Make coding errors in mandatory ie's send a STATUS with cause 100 "Invalid information element contents" in response. Also fix detection of coding errors in channel identification ie.
> Other misc items to fix:
> Update ALERTING_NO_PROGRESS conditional code.
> Make it not recognize ie 0x01 for switches other than 4ESS, 5ESS, NI2, and DMS-100.
> Send STATUS messages when receiving messages in the wrong call state.
> Send DM and DISC frames with only three data octets instead of an extra fourth octet.



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