Bug 903070 - Asterisk upgrade breaks IAX
Summary: Asterisk upgrade breaks IAX
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: asterisk
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-23 04:46 UTC by Doug Mitchell
Modified: 2020-11-30 15:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-30 15:02:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Doug Mitchell 2013-01-23 04:46:41 UTC
Description of problem:
Upgrading to latest asterisk breaking IAX2 trunks

Version-Release number of selected component (if applicable):
asterisk-1.8.19.0-1.el6

How reproducible:
Use "yum upgrade" to upgrade from asterisk-1.8.18.0-1.el6.x86_64 to 1.8.19.0-1.el6.x86_64 and restart asterisk.

  
Actual results:
IAX trunks are initially okay, but within a few minutes they all go unreachable.  Additionally, incoming UDP packets can be seen piling up in the UDP receive queue for UDP port 4569 as if asterisk is not reading them any more.

Expected results:
IAX should just keep working like it used to.

Additional info:
I was unable to roll back to the old package because it was removed from the repository.  This is a very bad idea.  Also, I was unable to locate the source package which was used it locate the good binaries, it was also deleted.  Deletion of historical source packages from repositories is a very bad idea and might border on a GPL violation.

Comment 1 Alec Davis 2013-08-06 10:48:37 UTC
I'm sure this UNREACHABLE condition has been fixed since 1.8.23 or 11.5.0

Specfically refer to the 2 commits on April 12 2013 http://svnview.digium.com/svn/asterisk/branches/1.8/channels/chan_iax2.c?view=log

Alec Davis

Comment 2 Ben Cotton 2020-11-05 16:52:57 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged  change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.

Comment 3 Ben Cotton 2020-11-05 16:55:33 UTC
This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version.

Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above.

Comment 4 Ben Cotton 2020-11-30 15:02:00 UTC
EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
EPEL please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.