[asterisk-bugs] [JIRA] (PRI-172) Missing handling for mandatory IE 24

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on PRI-172:
-------------------------------------

Please don't post an intense pri debug trace as it is unnecessarily noisy.  Intense trances are for debugging Q.921 as opposed to Q.931 problems.

However, do post a "pri set debug on span x" debug trace.

> Missing handling for mandatory IE 24
> ------------------------------------
>
>                 Key: PRI-172
>                 URL: https://issues.asterisk.org/jira/browse/PRI-172
>             Project: LibPRI
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 1.4.13
>         Environment: Asterisk 11.10.2, Libpri 1.4.15, Dahdi 2.9.1.1, Linux 3.2 (Debian Wheezy)
>            Reporter: Olivier Krief
>            Assignee: Richard Mudgett
>
> My lab setup is:
> Phone1 <---> Asterisk1 <--SIP--> Patton SN 4638 <-- BRI--> Asterisk2 <---> Phone2
> Inside Asterisk2 box is installed an HA8 board with a single 4 BRI module.
> When dialing in from phone1 to phone, no call is established and  Asterisk2 shows:
> ERROR[3819]: chan_dahdi.c:14480 dahdi_pri_error: PRI Span: 1 XXX Missing handling for mandatory IE 24 (cs0, Channel ID) XXX
> When dialing out from phone1 to phone, call is established Asterisk2 shows:
> WARNING[4054][C-00000002]: app_dial.c:1546 wait_for_answer: Unable to write frametype: 2
> I've played such setup hundred times with older versions of Asterisk/Dahdi/Libpri combinations.
> This is the first time I'm observing this and this occurs with version mentioned in Environment.
> I've recorded pri intense debug in a file I can send.
> Before filling this issue, I've googled a bit and found nothing either recent or helpful. Please, apologize if I missed anything.
> I can of course, handle configuration details but I must add I got this issue while preparing/testing to upgrade an 3-4 years old system.



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