Note that that test line DOES give out false positivs and false negatives,
so you cannot rely on it as an absolute. Also, the call route to get
there is going to be rather different than the call route to get to you.
Not to mention it is probably a long distance call which means the padding
is very likely to be different than any local call.
Did you try calling your site by forcing it onto a LD carrier? 10288?
>I'd ask here if it could be a padding issue.
You can't tell from your end. Note 'Receive Level' is NOT padding, people
confuse that all the time. Padding can only be accurately measured by
the client device as it is on that end of the connection.
>pm3> version
>Livingston PortMaster PM-3 ComOS 3.7.2c3
>System uptime is 2 hours 44 minutes
>pm3> sho line0
>---------------------- line0 - T1 Inband DS0 ---------------
>
> Status: UP Framing: ESF Encoding: B8ZS PCM: u-law
>
> Signaling: Trunk E&M wink start
>
> Receive Level: +2dB to -7.5dB
>
> Alarms Violations
> ----------------------------- -----------------------------
> Blue 0 Bipolar 0
> Yellow 1 CRC Errors 0
> Receive Carrier Loss 0 Multiframe Sync 0
> Loss of Sync 0
>
>Does this all look normal? And is there anything else I should look at?
Looks good.
-MZ
-- <URL:mailto:megazone@megazone.org> Gweep, author, webmaster, human being, me "A little nonsense now and then, is relished by the wisest men" 781-788-0130 <URL:mailto:megazone@gweep.net> <URL:http://www.megazone.org/> Hail Discordia! - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>