Missed packets in Monitor? 9

[atcom]

Anybody know what these messages mean in monitor? It would sure help if it told us why the packets were "missed"!

********** Warning: Missed 13 packet(s) Total late 0 packet(s) **********

The context is a SIP trunk that's acting up - this issue seems to come up far more often after an upgrade from 9.0.x to 9.1.3

-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[tlpeter]

TCP means that there is a check if the packets are received, if not than the packets are send again.
UDP is send and that is it as there is no check.
So this means the network is too busy for UDP.
And if this is the voice network than put it in it's own (voice) vlan with QOS.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Jimmyjoe1975]

Thanks for the answer.
So are you 100% sure that it can be solve setting up right the network options?
I'm agree with you, I mean I think the same, it is a network thing, but I just want to make sure that improving the network connection isn't a waste of time.

 

[IPGuru]

Basic VoIP diagnostic

1: It is the data network, get the data network checked

2: Data Network has been checked, goto step 1



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[Jimmyjoe1975]

In this case, Server Edition is in a Virtual Machine and Chronicall is in another virtual machine of the same VMWare Server so they are sharing the same network interface. Besides both servers are in the same subnet (only 1 hop in the traceroute), so I even can't provide Qos to the router because is not used in this connection.
I don't know what else I can do in this case.
Thanks

 

[tlpeter]

If it isa served edition then there is something wrong in the setup of the network settings within VMware.

BAZINGA!

I'm not insane, my mother had me tested!

 

[janni78]

What hardware is WMware running on?

"Trying is the first step to failure..." - Homer

 

[Jimmyjoe1975]

Sorry for the delay in the answer.
I was following the Avaya documentation during the installation, and regarding the network options doesn't have too much information or maybe were isn't any special configuration regarding network settings.
It is a VMware 5.5 working in a couple HP Proliant DL360P G8, and it is Ip Office Select R.9.1.4 with high availability.
Thanks for the help.

 

[janni78]

How many VMs do you have on the same hardware? (a HP server don't say much. it can have anything inside)

Most likely if you would install this on it's own hardware you wouldn't have the same issue so it's probably not a IPO problem.

"Trying is the first step to failure..." - Homer

 

[tlpeter]

Are the reservations still like they should be?
Does the IPO has two dedicated NIC's or does it share the NIC's?
Do you use VLAN's on the NIC's?


BAZINGA!

I'm not insane, my mother had me tested!

 

[Jimmyjoe1975]

Hi,

Thanks for the answers.
There are 10 VMs in both servers, but I am pretty confident with the VmWare setup because the administrator is somebody with lots of experience, so I will doubt it is something related to the hardware or the VMWare config.
Besides I execute Monitor in another PC (in the same subnet and 1 hop to reach the Ip Office in traceroute) different to the VM and still missing packages with UDP protocol, so it looks like isn`t related to the VMware per se. It is pointing to a Ip Office configuration.
This is a Virtual Machine and the second NIC is disabled at startup, so it is only working with 1 network interface without any VLAN and I don't know what`s exactly about the reservations, could you explain it to me tlpeter?

 

[derfloh]

and 1 hop to reach the Ip Office in traceroute

That doesn't say anything about the network. You can have a hundred switches connected in a row but you will still have 1 hop. The hop count will only increase with every router the packet goes through.

 

[atcom]

At the end of the day these "missed packets" messages are only a cryptic indicator of a network based problem. In my case I believe it was the router/firewall messing with SIP ALG or NAT type stuff (turns out it would occur every time I disconnected my remote IPsec connection). In working with Asterisk PBX's one can capture every single packet at the NIC with tcpdump, but IPoffice doesn't offer that level of capture. You can always go through the pain of putting a PC inline with the NIC on the IPO and capturing with Wireshark which is the only way you're going to see the root cause of the issue (often port numbers or IPs changing mid-stream).


-----------------------------------

Calgary Telephone Systems, Avaya LG Asterisk (FreePBX) VOIP & TDM

 

[derfloh]

Most switches allow to configure a mirror port for packet capturing. But I agree that it would be easier if IPO would be able to save a packet trace as pcap file like ASBCE does.

 

[CarGoSki]

You can dump all the lan1 or lan2 packets if you know how.
Very handy for those pesky SCN issues. You can see the SCN packet go out into the world to the central site and you can see it received.
Wireshark is best since monitor is a literal dump.

 

[intrigrant]

IP Office monitor was and is never build for network monitoring, Wireshark is a far better tool and free so why invest a hughe sum of money for something that is free.
I have been working close with Avaya developing features for IP Office in the past and this passed the list as well, there is no real need for it.

 

[derfloh]

Saving a packet dump for further investigation would be good. Just to save a dump to SD Card (or perhaps on the optional SD) to download it. Then you can look at it with wireshark. It would be a good option if you are not at the IPO site. And you don't need a network engineer to configure a mirror port.

Remote pcap could also be an option if you have a server onsite.