search for: rxa

...uch of an impact. > IIRC, standard Ethernet uses pairs 1&2 and 3&6. The color scheme on "568B" is 1&2 = white/orange pair, 3&6 = white/green pair Most Ethernet cables then have the white/blue pair on 4&5, and white/brown on 7&8. An RJ45 carrying a T1 is: 1 - RxA 2 - RxB 4 - TxA 5 - TxB Assuming that you'd want RxA and TxA in the same twisted pair (ditto for RxB and TxB) then a cable would look something like this at each end: 1&4 = white/orange pair 2&5 = white/blue pair I don't know if there's an industry standard for T1 cabling to h...

...000000000000 ? ? ? ? ? TxC 000000000000000000000000 ? # ? ? ? TxD 000000000000000000000000 ? ? ? ? ???????? ? ? ? ? RxA 000000000000000000000000 ? Loop ? ? ? ? ? RxB 000000000000000000000000 ???????? ? ? ? ? RxC 000000000000000000000000 ? ? ? ? RxD 000000000000000000000000 ? If I...

https://bugzilla.samba.org/show_bug.cgi?id=9594 Summary: Error transferring user and non-user xattr using --fake-super under Linux Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

Hello, I am installing asterisk, libpri and zaptel. I have it setup for EM wink. incoming calls are working. outgoing calls are not. zttool shows TxA as 11000000 RxA shows 00000000 This doesnt seem like em_w signalling? Seems like the PBX is not setup for EM_w. Is that the case? Jerry

...risk to work with it. By fiddling about, I've come up with the "almost working" configuration below. This works except that it takes about 4 seconds from when the console says the line is answered until it plays my prompt. Watching the card with zttool, all flags start at 0. Then RxA, RxB, TxA, TxB, TxC, TxD change to 1. Then, a split second later, TxA, TxB, TxC, and TxD change to 0. A couple of seconds later, TxA, TxB, TxC, TxD change to 1 and the call progresses. What does this mean? Can you identify the proper configuration from this "handshake?" Verbosity is a...

...nel 'Zap/1-1' WARNING[14351]: File chan_zap.c, Line 4173 (ss_thread): CallerID returned with rror on channel 'Zap/2-1' and when I call the number that is supposed to terminate there I get busy signal. also in the zttool I see strange thing, in the bottom portion where there are RxA, RxB .... the 1111111 ( ones) sometimes change into 000000, they go from up to down and if I enable all the channels then firs on the first column then on the second column, in the bottom half of the screen. while if I plug the same E1 into Cisco AS5300, whit this config( just exepts): isdn s...

...atch cable as a T1 patch cable. Correct. I mixed up "pair 1" with "the pair of wires connected to pins 1 and 2." T1 uses "Pair 1" and "Pair 2," which was what I was trying to say and what you *did* say! :) > > An RJ45 carrying a T1 is: > > 1 - RxA > > 2 - RxB > > 4 - TxA > > 5 - TxB > If you are referring to A and B as the differential signal components then you're right about the wiring. In either case you're wrong with respect to the pairing. :-) Sorry, I am used to the way NEC documents their PBXs and this...

...dtran What should zttool show if everything is configured properly? After doing 'modprobe wct1xxp;ztcfg' I ran zttool. In the details for the T100P I saw: "Current Alarms: Red Alarm, Sync Source: Internally Clocked" ? TxA 00000000 ? TxB 11111111 ? TxC 00000000 ? TxD 11111111 ? RxA 00000111 ? RxB 11111010 ? RxC 00000000 ? RxD 00000000 Should the transmit and receive settings be mirror images of each other, or is this display correct given my situation? Unfortunately I don't understand what a good display would look like. On another topic, I've tried connecting to...

...Assignee: wayned at samba.org Reporter: shqking at gmail.com QA Contact: rsync-qa at samba.org A suspicious integer overflow is found in xattrs.c:692. The code snippet is as follows. 684 for (num = 1; num <= count; num++) { 685 char *ptr, *name; 686 rsync_xa *rxa; 687 size_t name_len = read_varint(f); 688 size_t datum_len = read_varint(f); 689 size_t dget_len = datum_len > MAX_FULL_DATUM ? 1 + MAX_DIGEST_LEN : datum_len; 690 size_t extra_len = MIGHT_NEED_RPRE ? RPRE_LEN : 0; 691 if ((dget_len + extra_len < dget_len) 692 || (dget_len...

...Should I see OK here instead ? Is it normal > ?) > Sync Source: Internally clocked > IRQ Misses: 0 > Bipolar Viol: 0 > Tx/Rx Levels: 0/ 0 > Total/Conf/Act: 1/ 1/ 1 > > 1 > TxA - > TxB - > TxC - > TxD - > > RxA - > RxB - > RxC - > RxD - > dahdi_cfg -vv > DAHDI Tools Version - 2.2.0 > > DAHDI Version: 2.2.0.2 > Echo Canceller(s): MG2 > Configuration > ====================== > Channel map: > Channel 01: FXS Kewlstart (Default) (Echo Canceler: mg2) (Slaves: 01) > 1 ch...

...a Telephony Interfaces Alarms Span OK Wildcard X101P Board 1 Current Alarms: No alarms. Sync Source: Internally clocked IRQ Misses: 0 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 1/ 1/ 1 1 TxA - TxB - TxC - TxD - RxA - RxB - RxC - RxD - ztcfg === Channel map: Channel 01: FXS Kewlstart (Default) (Slaves: 01) 1 channels configured. /etc/zaptel ======= loadzone=uk defaultzone=us fxsks=1 /etc/asterisk/zapata.conf ================ [trunkgroups] [channels] ; context=default switchtype=national ; signalling=fxo_...

Hi, It seems like my ATA is making a ringing noise... (as it used to), but now (After the upgrade from 1.0.7 to 1.2) asterisk also is either making the ringing, or passing the PRI ringing from the telco on to me. Any suggestions on how to fix this?

...------- - ? ?? ? ? ? TxC --------------- - ? ? ? ? ? TxD --------------- - ? ? ? ? ? ? ? ? RxA --------------- - ? ? ? ? RxB --------------- - ? ? ? ? RxC --------------- - ? ? ? ? RxD --------------- - ? ? ??...

...ally clocked IRQ Misses: 74 Bipolar Viol: 0 Tx/Rx Levels: 0/ 0 Total/Conf/Act: 24/ 24/ 0 111111111122222 123456789012345678901234 TxA ------------------------ TxB ------------------------ TxC ------------------------ TxD ------------------------ RxA ------------------------ RxB ------------------------ RxC ------------------------ RxD ------------------------ *CLI> zap show status Description Alarms IRQ bpviol CRC4 Wildcard TE120P Card 0 OK 74 0 0 *CLI> -------...

https://bugzilla.samba.org/show_bug.cgi?id=6590 Summary: [sender] could not find xattr #1 for home/jdoe/TheFresh Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: stlman at