|Summary:||ASTERISK-18710: Alarms not properly set on PRI trunks at startup|
|Reporter:||Tzafrir Cohen (tzafrir)||Labels:|
|Date Opened:||2011-10-12 10:52:36||Date Closed:||2011-10-12 15:09:25|
|Versions:||SVN 184.108.40.206||Frequency of|
|Environment:||Asterisk 1.8 rev. 340365 Test system: Centos 5, Xorcom PRI interface, DAHDI 220.127.116.11||Attachments:||( 0) pri_alarms_param.diff|
|Description:||Asterisk 1.8 does not properly set alarms at startup on PRI (ISDN) channels: it calls sig_pri_set_alarm() with an inalarm value of 0. The same seems to apply to branch 10 as well.|
In trunk I suspect that we have the reverse bug: sig_pri_chan_alarm_notify() is called with the value of the alarms, which considers it a "no alarm" value.
(I also have no idea what happened to the SS7 code that was added in 1.8 and 10, but does not exist in trunk).
Patch tested with SVN rev.
|Comments:||By: Richard Mudgett (rmudgett) 2011-10-12 14:51:09.089-0500|
That particular area of code has not changed between v1.8 and trunk. I suspect your trunk workspace is corrupted or very old since you mention the SS7 code is missing.