[AusNOG] ISDN acting the maggot

[Geordie Guy]

I suspect it's a similar condition to the one that allows me to put a
perfectly aligned white/green, green, white/orange, blue, white/blue,
orange, white/brown, brown RJ45 clip into a crimping tool, squeeze the
handles and observe the finished product to be white/green, white/orange,
green, white/blue, red, white/brown and an OM3 strand.


On Fri, Aug 16, 2013 at 3:10 PM, Peter Adkins <peter.adkins at kernelpicnic.net
> wrote:

> No matter how many times you've checked and double checked the RX/TX lines
> of a device or service, or have worked with it in the past, it's wrong! :)
>
> I learnt recently that it's been dubbed "UART dyslexia" by the internet at
> large. What's worse is it usually only becomes apparent after you've
> soldered, or crimped the pairs...
>
>
> On Fri, Aug 16, 2013 at 9:19 AM, Geordie Guy <elomis at gmail.com> wrote:
>
>> RX/TX pairs not correct.  I blame Friday.
>>
>>
>> On Fri, Aug 16, 2013 at 9:15 AM, Geordie Guy <elomis at gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> CE question but hopefully someone has an idea amidst the hail of "take
>>> it to SAGE".  What would cause an ISDN connection to be able to be looped
>>> back fine both ends (so a loopback on the provider end is visible and get
>>> CD *AND* a loopback on customer end shows at provider the same) but if the
>>> connection is provider to customer there's no carrier?
>>>
>>> - Geordie
>>>
>>
>>
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>
>
> --
> Regards,
> Peter Adkins
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20130816/02af7e95/attachment.html>