I am seeing lots of lost packets when running the command sip show channelstats 
at the CLI.
There are issues across multiple Asterisk servers I am trying to diagnose but 
everything I read seems to point to this command being pretty unreliable.
Can I trust the info this command shows?
I am showing lots of lost packets in sip show channelstats but I can't see any 
packet loss when pinging the same IP's to/from.
Since I don't 100% control the network my gear is on, I need something outside 
of Asterisk to show the network engineer to convince here and myself that there 
are network issues.
All I have is the loss that's shown from this command with no real network 
stats to back it up.
Is there a magic command in CentOS anyone can recommend to diagnose and match 
up the issues shown in Asterisk using this command?
Moving gear around on the network changes the info Asterisk shows a LOT. For 
example, if I point traffic to the main physical gateway I get loss to a 
particular customer's IP (their PBX), if I move it to another place on the 
network (as a VM) their IP is good and other customers IP's start showing loss 
using the channelstats info.
Driving me freakin' crazy. It does appear there are network issues causing my 
troubles but I can't get help if I can't point to some hard and fast issues 
outside of Asterisk.
The only thing I have right now is collissions showing on one of a few of our 
pfSense devices but they are virtual running on XenServer, still this would 
indicate a problem in my opinion.
Thanks in advance for any assistance on this issue. Stepping back from the 
ledge now LOL

                                          
-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to