[asterisk-users] Strange problem with PRI on 64-bit?
tony at softins.co.uk
Wed Apr 4 08:29:25 CDT 2018
In article <pa2c9u$1pa$1 at softins.softins.co.uk>,
Tony Mountifield <tony at softins.co.uk> wrote:
> In article <CAHZ_z=wt3SAQnDOy26umPeC9=UNS8zg_WOofMnGuD=yntAmHPg at mail.gmail.com>,
> Matt Fredrickson <creslin at digium.com> wrote:
> > On Tue, Apr 3, 2018 at 4:38 PM, Tony Mountifield <tony at softins.co.uk> wrote:
> > > In article <CAHZ_z=w5DMg93gShtC93kuC+fnmraPgV46BS956U5BQXVgyhxg at mail.gmail.com>,
> > > Matt Fredrickson <creslin at digium.com> wrote:
> > >> That does seem quite odd. If I remember right, those messages would
> > >> come up if it looked like the other end hadn't received a message when
> > >> it thought it should have. I can't think of anything that would
> > >> particularly impact 64 bit systems versus 32 bit systems in that
> > >> domain (ISDN real time message timing, etc). Are you sure there's
> > >> nothing else different (kernel version or something else like that)?
> > >> Maybe also run a patlooptest on the spans in question to make sure
> > >> that they're running cleanly.
> > >
> > > Hi Matt, thanks for the reply.
> > >
> > > Both the 32-bit and 64-bit were fresh installs of the latest CentOS 6.9 from
> > > online repositories using a kickstart build. I'm going to try installing the
> > > 64-bit version again tomorrow to see if the problem re-appears, just to be
> > > certain it wasn't anything transient. I don't think there is anything unclean
> > > about the spans, because they were running fine on CentOS 4 with the versions
> > > I mentioned, and are now running well again with 32-bit CentOS 6.
> > Hey Tony,
> > The paylooptest recommendation wasn't necessarily about screening
> > hardware problems but weeding out that there weren't any potential
> > driver issues on the 64bit install.
> Ok, sure. I assumed that DAHDI would have had a lot of use on 64-bit by now,
> especially since RHEL 7 is 64-bit only (although I believe CentOS 7 has been
> made available also in 32-bit).
> I've just done a 64-bit rebuild again, so will do some tests.
... And this time, I am not getting the MDL errors that I was getting last time.
So it looks like 64-bit is ok (which is what I would expect!), the trunks must
have got into an unexpected state, and I didn't try hard enough to get them to
reset. I have now made several test calls in and out without problems.
So apologies for the false alarm, and I appreciate the feedback!
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
More information about the asterisk-users