I did do a search of bug9080 and noticed that a patch resolved the issue. I have a release 4.5.88, 1000E that is constantly kicking out a BUG9080 and of course everything is in hex.
I never noticed this issue in the past and not sure why this all of a sudden this error had showed up?
All this error tells me is that call idled still in broadcast trunk list.
Any idea how I can stop this message from being generated?
There was an issue about a week ago where it kept INIing and finally sysload and switched to the other CPU on it's own. We could not figure out why it INI'd other than the MUS broadcast licenses were full. This system only has 20 liceness and apparently that kept being exceeded thus generating an error message. Not sure if this caused the INI or not?
We are concerned that this BUG9080 will cause the PBX to INI since there are all of these messages being generated? It might fill up the buffer?
Nothing has really changed in regards to MUS programming in the last (7) years.
Does anyone have any ideas?
Thank you..
I never noticed this issue in the past and not sure why this all of a sudden this error had showed up?
All this error tells me is that call idled still in broadcast trunk list.
Any idea how I can stop this message from being generated?
There was an issue about a week ago where it kept INIing and finally sysload and switched to the other CPU on it's own. We could not figure out why it INI'd other than the MUS broadcast licenses were full. This system only has 20 liceness and apparently that kept being exceeded thus generating an error message. Not sure if this caused the INI or not?
We are concerned that this BUG9080 will cause the PBX to INI since there are all of these messages being generated? It might fill up the buffer?
Nothing has really changed in regards to MUS programming in the last (7) years.
Does anyone have any ideas?
Thank you..