Hi Mark,
I jumping in with Ryan because I agree with his experience. Here's
some of mine (for what it is worth)...
>> The phone system is manufactured by Allworx
No experience. Perhaps someone else can comment on Allworx
>> The switches we are using are Dell 3548P PowerConnects.
>> I've configure the network to use two VLANs - one for phone,
>> one for everything else - and used VLAN tagging and CoS to
>> prioritize VoIP traffic. I've actually combed through the configs
>> with a Dell engineer, and we're good there.
I've had a number of hard to track down issues related to Dell
hardware and the Broadcom ethernet gear. During the two nastier
issues, the port would process data fine for a while. Then throughput
would drop to its knees. It was as if packets were being dropped
following a reciprocal-exponential curve. The Dell hardware never
reported any problems.
Also, is the problem with all phones with a more or less random
distribution? Does it look random but with a single switch in common?
or is it related to a collection of handsets?
Jeff
On 6/19/09, Ryan Zuidema <ryan.zuidema@xxxxxxxxxxx> wrote:
>
> Running computers through the phones is entirely normal, the point of VoIP
> is to have a 1 wire office. That said most VoIP installs I have seen still
> run separate lines. The reasoning is that it’s easier to maintain and the
> cost difference is small to run two wires as opposed to one.
>
> It’s not surprising that the server doesn’t tag. It’s reasonable to assume
> that ALL traffic to that port would be on the phone VLAN and high priority.
> The only reason your endpoints need to tag is if they have multiple QoS
> requirements.
>
> Ryan
>
> From: wireshark-users-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of
> Mark Jeffers
> Sent: Friday, June 19, 2009 6:40 AM
> To: Community support list for Wireshark
> Subject: Re: [Wireshark-users] Huge VoIP Problem :(
>
> The phones actually act as a level 2 switch themselves. They tag their own
> packets for VLAN9 (the voice VLAN on my network) and tag the packets of the
> PC attached to them (if there is one) as VLAN1.
>
> Attaching a phone and a pc to the same switch port has made me nervous from
> day one, but the vendor swore up and down it would work no problem.
>
> Also, one thing that has me shaking my head in disbelief is that while
> Allworx built their phones with VLAN tagging abilities, their main phone
> server can't tag its own packets.
>
> But anyway, I was of course suspicious of the pc/phone combo, but some of my
> most problematic phones have no pc attached to them. Plus, I figured
> building the VLANs would solve any problem related to that. Perhaps I was
> wrong?
>
> Cheers,
>
> mj
>
> [SNIP]
>
> From: wireshark-users-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of
> Mark Jeffers
> Sent: Wednesday, June 17, 2009 9:32 AM
> To: wireshark-users@xxxxxxxxxxxxx
> Subject: [Wireshark-users] Huge VoIP Problem :(
>
> We've been having a terrible time with a new VoIP system on our network.
>
> The phone system is manufactured by Allworx - it is tied to the outside
> world with a standard PRI, so the only IP portion of calls takes place
> between our LAN phone server and the IP extensions.
>
> Several of the extensions are having packet loss problems resulting in
> echoes, "static", dropped audio, etc. The problems are intermittent and
> jump around to different phones on the network.
>
> The switches we are using are Dell 3548P PowerConnects. I've configure the
> network to use two VLANs - one for phone, one for everything else - and used
> VLAN tagging and CoS to prioritize VoIP traffic. I've actually combed
> through the configs with a Dell engineer, and we're good there.
>
> So I'm relatively new to both VoIP and hardcore packet analysis, but I found
> an excellent article on troubleshooting VoIP using wireshark and followed
> instructions.
>
> I mirrored one of the Trunk ports on the switch to my laptop, configured
> Wireshark to filter out all but UDP packets and let it run for about an
> hour.
>
> The results are horrible... I've attached screenshot images so you guys
> might be able to help me figure this out.
>
> When I ran an RTP Stream analysis, there were blocks of sessions where
> several of them had "Max Delta" in the thousands (some in the 9000s),
> resulting in 90+% packet loss! See Image1,jpg
>
> I drilled down into one of the streams to see a bunch of "Wrong Sequence nr"
> messages - See Image2.jpg
>
> I went to VoIP Calls under the statistics menu, and pulled up the same call
> shown in Image2 - looked fine to me, but I'm a noob - See Image3.jpg
>
> I'm at a loss here. Obviously severe network issues, or the Phone Switch
> is bad. I've tried everything I can think of to no avail. Anybody have
> any ideas of what might be wrong, or what further information I should
> gather to help pinpoint the issue? I'm going nuts here and any help would
> be greatly, greatly appreciated. :)
>
> Cheers,
>
> Mark
> [SNIP]
