>Jordan Mendelson wrote:
>
>> I've reported this over and over. If you see an extremely high number of
>> "Lost Carrier" messages in your syslog, take a real close look at them.
>> You might see something like what we have:
>>
>> The real way to get Lost Carrier reporting is of course radius.
>>
>> RADIUS reporting:
>> Lost Carrier 7.84% 936/11942
>>
>> SYSLOG reporting:
>> Lost Carrier 1.05% 111/10528
>
>Woops, this is backwards, should have been:
>
>SYSLOG reporting:
> Lost Carrier 7.84% 936/11942
>
>RADIUS reporting:
> Lost Carrier 1.05% 111/10528
>
>Sorry for the confusion. Don't use the syslog logs for judging Lost
>Carriers, the PM3's have misreported it for ages.
I read it as reporting different information. Assuming your POP dialin
number isnt next to a phone sex line, some percentage of the extra Lost
Carriers as reported by syslog are customer's dialing in and not being able
to make a connection. Yes, the figures in syslog are different than that
of the information gained from RADIUS call completions. However, the stats
are just as useful in that they answer a different question. On my PRI
pops, I see about 91-92% successful call completions according to RADIUS
looking at the figures over a week's period compared to 80% of all calls
made to the pool result in a connection of some sort...
---Mike
Mike Tancsa (mdtancsa@sentex.net)
Sentex Communications Corp,
Waterloo, Ontario, Canada
-
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/>