Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

bcm50 - packet loss errors

Status
Not open for further replies.

floppyraid

Technical User
Aug 16, 2009
30
US
greetings.

two questions,

does anyone know of any resources where i can get exact details for how to decipher the errors below? i cant find any documentation that goes into the error codes in any depth.

regardless of finding very detailed documentation, what im mainly trying to figure out is this- are these errors happening because of network congestion while a call is active? or can these errors also appear from just network congestion / loss of connectivity while there isnt an active call? (so far, noone has said that they have had a call dropped, nor has anyone reported poor call quality.)- does the BCM itself handle any sort of configurable QoS or is that mostly left up to other hardware?



Packet Loss Violation Cleared: near DN: 329, source IP: (one ip phone), source port: 51002, destination IP: (another ip phone), destination port: 51004, reasonText: Violation cleared due to call termination

Packet Loss Violation Unacceptable: 88%, nearDN: 329, source IP: (one ip phone), source port: 51002, destination IP: (another ip phone), destination port: 51004, ct 0, eT D, nLR 0, dR 0, bD 0, bL 0, gD 0, gL 0, eSD 0, aNL 0, aSP 0, rTT 725
 
You will only see these log entries when an actual call is dropping packets. The systems uses missing sequence numbers to calculate the percentage of loss.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top