<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Except it is not owned by the customer. <o:p></o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> smithsonianwa@gmail.com
[mailto:smithsonianwa@gmail.com] <b>On Behalf Of </b>Tim Smith<br>
<b>Sent:</b> Wednesday, June 03, 2009 4:40 PM<br>
<b>To:</b> Voice Noob<br>
<b>Cc:</b> Dane; cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] T1 xover or straight through?<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>IAD would still be considered
customer equipment as well I'd think.<br>
<br>
Cheers,<br>
<br>
Tim<o:p></o:p></p>
<div>
<p class=MsoNormal>On Wed, Jun 3, 2009 at 11:06 PM, Voice Noob <<a
href="mailto:voicenoob@gmail.com">voicenoob@gmail.com</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p><span style='font-size:11.0pt;color:#1F497D'>I have had providers install an
IAD device where they take the circuit from the Telco into their IAD. Then they
hand of a PRI to my equipment from the IAD. In this case you need a Crossover
T-1 cable.</span><o:p></o:p></p>
<p><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<p><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:
10.0pt'> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Tim Smith<br>
<b>Sent:</b> Wednesday, June 03, 2009 7:37 AM<br>
<b>To:</b> Dane<br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] T1 xover or straight through?</span><o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
<p style='margin-bottom:12.0pt'>Hi Dane..<br>
<br>
Simple rule for this.<br>
<br>
1. Customer Equipment to Customer Equipment = T1/E1 cross over cable<br>
2. Customer Equipment to Network = Straight through cable<br>
<br>
Customer Equipment = PBX, Voice cards on routers, key systems <br>
Network = the PSTN, your carrier, etc<br>
<br>
Bit more info to help explain hopefully :)<br>
<br>
Your 3845 T1 voice interface has pin outs as follows<br>
<br>
Pin<br>
1 - Receive (RX) Ring<br>
2 - RX Tip<br>
4 - Transmit (TX) Ring<br>
5 - TX Tip<br>
<br>
Think of receive as your ear and transmit as your mouth<br>
Straight through cables connect pin 1 to 1, 2 to 2, 4 to 4, 5 to 5.<br>
<br>
So when connecting customer to customer equipment with a straight through cable<br>
You are essentially connecting ear to ear and mouth to mouth.<br>
To get complete circuits you need ear to mouth and mouth to ear<br>
<br>
An E1/T1 cross over cable "crosses" the RX and TX connections as
follows:<br>
Pin 1 to Pin 4<br>
Pin 2 to Pin 5<br>
Pin 4 to Pin 1<br>
Pin 5 to Pin 2<br>
<br>
Network / PSTN equipment has different pinouts.. i.e. it expects RX on pin's 1
and 2, and expects TX on Pins 4 and 5 from your equipment. Hence straight through
cable required.<br>
<br>
Also dont forget if this is ISDN you also have a layer 2 network / user element
to consider. i.e. if you connect 2 x customer equipment together - one side
needs to be configured as Network side, and the other as user.<br>
<br>
Hope this helps a bit..<br>
<br>
Cheers,<br>
<br>
Tim<o:p></o:p></p>
<div>
<p>On Wed, Jun 3, 2009 at 7:04 PM, Dane <<a href="mailto:dane@pktloss.net"
target="_blank">dane@pktloss.net</a>> wrote:<o:p></o:p></p>
<p>First I wanted to say thanks for the replies and information.<br>
<br>
Second, well I got it sorted out finally. I took down one of the<br>
PRI's after hours from the IAD and connected it to the 3845 with a<br>
straight through cable just to test. It did not come up which is what<br>
I think I and everyone who responded on this list would have expected.<br>
I connected the IAD to the 3845 with a T1 crossover just as I have<br>
the IAD connected to my CMM-6T1s and it came up.<br>
<br>
Now the kicker is that this same 3845 T1/PRI port connected to the<br>
AT&T demarc requires a straight through cable.<br>
<br>
I have to be honest and admit that this confuses me. Of course its<br>
4am and I have been busting my ass since 6am so I am not able to<br>
mentally sort this out. Have to give it some thought when I have my<br>
wits how the 3845 port takes either a T1 crossover or a straight<br>
through depending on the other side apparently.<br>
<br>
Anyway, I thought it was interesting to note and share.<br>
<br>
Thanks again for the help.<br>
<br>
<br>
<br>
<br>
<br>
On Mon, Jun 1, 2009 at 12:31 PM, Go0se<<a href="mailto:me@go0se.com"
target="_blank">me@go0se.com</a>> wrote:<br>
> As a general rule a T1 crossover cable is always required between PBXs no<br>
> matter how you interconnect them. I'm not aware of a T1 controller that
will<br>
> auto-mdix. You can build your own T1 crossover - cross pins 1&2 to
pins 4&5.<br>
> (1 to 4 and 2 to 5)<br>
><br>
> -Go0se<br>
> <a href="http://atc.go0se.com" target="_blank">http://atc.go0se.com</a><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
On Behalf Of Dane<br>
> Sent: Monday, June 01, 2009 11:28 AM<br>
> To: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> Subject: [cisco-voip] T1 xover or straight through?<br>
><br>
> Anyone know if you need a straight through or t1 crossover to go from<br>
> an IAD to a 3845 with a PRI port? We have some IAD's that terminate<br>
> with CMM's and those use t1 crossovers. Not sure about the 3845<br>
> ports.<br>
><br>
> Connecting to AT&T circuits to the 3845's required straight through.<br>
> Wish I had one to test.<br>
><br>
> Just wondering if anyone might know, wondering if the 3845s can handle<br>
> either / or, and if the requirement comes from the demarc side (either<br>
> AT&T or IAD's).<br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
><br>
><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>