search for: d8fb

Displaying 2 results from an estimated 2 matches for "d8fb".

Did you mean: a8fb
2010 Sep 27
2
SCCP (skinny) phone behind NAT: RTP dest addr wrong
...os 0x0, ttl 50, id 16034, offset 0, flags [none], proto TCP (6), length 72) 71.215.193.161.1025 > 216.251.177.106.2000: Flags [P.], cksum 0x461d (correct), seq 148:180, ack 569, win 16384, length 32 0x0000: 4500 0048 3ea2 0000 3206 b62f 47d7 c1a1 E..H>?..2.?/G??? 0x0010: d8fb b16a 0401 07d0 7c8a ecc6 710d 8d62 ???j...?|.??q..b 0x0020: 5018 4000 461d 0000 1800 0000 0000 0000 P. at .F........... 0x0030: 2200 0000 0000 0000 c0a8 0003 ba71 0000 ".......??..?q.. 0x0040: 6d00 0000 0000 0000 m....... packet tracing RTP at t...
2025 Apr 02
0
wrong NOTIFYTYPE always ONBATT on upssched TIMER ?
...----------- > > Message: 1 > Date: Tue, 1 Apr 2025 17:22:54 +0200 > From: RemiG<mailing-nut at dbmtechnologies.com> > To:nut-upsuser at alioth-lists.debian.net > Subject: [Nut-upsuser] wrong NOTIFYTYPE always ONBATT on upssched > TIMER ? > Message-ID:<c45d0396-d155-d8fb-716e-b18abe23c255 at dbmtechnologies.com> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > HI > > i'am using schema upsmon call : NOTIFYCMD /sbin/upssched > > and this part of upsschede strategy (working fine) > > device.model: E...