I have been messing with the T100P card with and without data
for over a week now, and still to no avail.
Just got off the phone with our T1 provider to make sure our settings
were correct for the T1 in zaptel.
zaptel.conf:
span=0,1,0,esf,b8zs
nethdlc=1-20
fxsks=21-28
loadzone = us
defaultzone=us
ifconfig just after one traceroute attempt to our provider dns server ip
hdlc0 Link encap:(Cisco)-HDLC
inet addr:160.81.118.46 P-t-P:160.81.118.45 Mask:255.255.255.252
UP POINTOPOINT RUNNING MTU:1500 Metric:1
RX packets:0 errors:415 dropped:0 overruns:0 frame:415
TX packets:474 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:8766 (8.5 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3068 (2.9 Kb) TX bytes:3068 (2.9 Kb)
My T1 provider seems to think the transmit signal of the T100p is
not strong enough and is the cause of the frame errors on the
RX trip.
The cable works fine with our cisco so I don't think it is a faulty
cable.
The cable is a standard ethernet cable (which is supposed to work
according to digium tech support). I get the same response when
i use a t1 xover 1-4 , 2-5 (rj48c)
I have even tried an rj48s but that did not five me any lights on the
card.
Connecting T100P to HyperEdge DTWA-528-02 Smart Jack (provided by
verizon)
Has anybody any input or possible resolution?
Regards
Greg Cirino
___________________________________
Cirelle Enterprises Inc.
603-425-2221
www.cirelle.com Website Design
www.cirelle.net ProSpeed High Speed Dial-up - 5 Times Faster
www.cedata.com Web, FTP, Email Hosting Services
www.mlsbot.com MLS IDX Services
When You Want It Done Well, Just Call Cirelle
It's not just a Rhyme... There's a Reason!
On Fri, 2004-10-15 at 14:25 -0400, Cirelle Enterprises wrote:> I have been messing with the T100P card with and without data > for over a week now, and still to no avail. > > Just got off the phone with our T1 provider to make sure our settings > were correct for the T1 in zaptel. > > zaptel.conf: > span=0,1,0,esf,b8zsSpans are 1 based, not zero. span=1,1,0,esf,b8zs> nethdlc=1-20 > fxsks=21-28 > loadzone = us > defaultzone=us-- Steven Critchfield <critch@basesys.com>