[App_rpt-users] strangle garbling on second node

Pierre Martel petem001 at gmail.com
Sun Jan 21 19:03:26 EST 2018


Just ont thing those test were made when both of my nodes are linked.

Just did another test and when unlinked both echolink and iaxrpt
transmission wont make multiple hungup message.

they connect by the startup_macro command and the macro is permanent link
(03)

.


2018-01-21 18:43 GMT-05:00 Pierre Martel <petem001 at gmail.com>:

> I have my nodes 27821 and 28739, they use to run on an old P4.
>
> The nodes are on UsbRadio and the levels have been adjusted on with an
> IFR1500 so they are inline.
>
> I switched computer yesterday and now I use a Proliant G5P computer on
> Stretch.
>
> Got some help to make it run but all seem prety well. I also run
> chan_echolink with chan_usbradio.
>
> the drive is aN SSD, got 8 gig of ram and the cpu is an 8 core xeon at 2.2
> ghz.
>
> I also use the Raid controler to have a 1 TB raid 1 array.
>
> If I run the GUI ( Mate)  or only CLI ( init level 3) it still the same. I
> tested on the same usb bus or different usb bus and it make no difference
>
> here is the outpu of lsusb
>
>  lsusb
> Bus 005 Device 002: ID 03f0:1027 Hewlett-Packard Virtual keyboard and mouse
> Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 010: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio
> Controller
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 014: ID 0d8c:013a C-Media Electronics, Inc.
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>
> I use 2 URI. they are not modded fob.
>
> I switched usb cable.
>
> I used iaxrpt to connect to both repeater and I got that in the log of
> asterisk:
>
>  WARNING[9017]: chan_iax2.c:921 jb_warning_output: Resyncing the jb.
> last_delay -98, this delay 2918, threshold 1164, new offset -2918
>
> and we receive a lot of hungup message for only one short ptt:
>
>  -- Hungup 'DAHDI/pseudo-1302878576'
>     -- Hungup 'DAHDI/pseudo-1313783111'
>     -- Hungup 'DAHDI/pseudo-1265694909'
>     -- Hungup 'DAHDI/pseudo-1223961614'
>     -- Hungup 'DAHDI/pseudo-1745973833'
>     -- Hungup 'DAHDI/pseudo-311499195'
>     -- Hungup 'DAHDI/pseudo-1573868247'
>     -- Hungup 'DAHDI/pseudo-56935586'
>     -- Hungup 'DAHDI/pseudo-267958833'
>     -- Hungup 'DAHDI/pseudo-580580533'
>     -- Hungup 'DAHDI/pseudo-1976922523'
>
> Even with an echolink connection there are multiple Hungup 'DAHDI/pseudo
> messages in the log for only one tx.
>
> Anyone can help?
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20180121/d726878a/attachment.html>


More information about the App_rpt-users mailing list