Should have mentioned that to start with.
SlowRRQ means the keepalive acknowledge packets coming from the phone are not or close to the time limit they should be within.
Keepalive are the above mentioned packets which the phone must reply on within a fixed amount of time. A full H.323 trace will show that time.
ExistRRQ is when the gatekeeper receives a Registration ReQuest which is in use by another device or the device rebooted unexpectedly while it was registered.
All they above will happen on poor connections. Enabling QoS within the VPN tunnel and the intermediate switches may help.
The phones and the system will be regularly talking even when no calls are in progress. The phones want to know that the system is still there (else in some scenarios they will try to connect to a fallback system). The system wants to know that a registered device is still there to potentially answer calls rather than wasting times routing calls to devices that have been switched off.
That non-call traffic, is also useful to stop intermediate devices like firewalls and routers from closing down the connections between the phone and the system.
A URQ is a User ReQuest, usually it has a command with it.
If it comes from the Gatekeeper(IP Office) it is reboot or re-register request, if it comes from the endpoint it is a notification to the Gatekeeper, usually a message the phone wants to unregister or is about to reboot.
You can initiate a reboot/re-register request from within sysMon or SSA or with local admin on the phone.
Both slowRRQ and missing keepalives are bad, the messages use UDP so there is no session to terminate by a firewall.
H323 is a complex sessionless protocol, that is why SIP was introduced which prefferred use TCP for Gatkeeper <> endpoint communication.
we are having the issues with many phones in our office, rebooting when idle or freezing when on a call. when I pull up monitor we see the same things BResource had.
a ton of these every day :
SlowRRQ, existrrq, keepalive, TCP close, sysmonRestart
but our network team says they see nothing wrong. I s there something I can show them to prove its a network issue and to dig deeper?
Your network guys don't see issues because they don't look or they don't really care, it is a common attitude for network guys.
Most of them know how to setup a network but are really bad in trouble shooting, you need some luck to find the right guy or complain to the CEO and increase the pressure on them.
* SlowRRQ means the keepalive acknowledge packets coming from the phone are not or close to the time limit they should be within.
* Keepalive are the above mentioned packets which the phone must reply on within a fixed amount of time. A full H.323 trace will show that time.
* ExistRRQ is when the gatekeeper receives a Registration ReQuest which is in use by another device or the device rebooted unexpectedly while it was registered. Phone rebooted between heartbeat time outs. If it breaches the time out and reregisters you wont see this.
Phones heartbeat every 55s (sometimes different) with a registration request.
The system timesout the phone if it sees no registrations in 240s and the phone is classed as unregistered after this time.
The Registrations tab shows how many times a phone has registered since the system has been up. This doesnt mean how many heartbeats it has had but full on registrations from such things as a phone reboot etc. You can break down why the phone has had say 20 registrations by counting how many ErrorURQ and ExistURQs there have been and adding 1 for the original registration. It may have had 15 ErrorURQs indicating phone reboots/packet timeouts before the 240s timeout and 4 times another device has tried to be this extension (or they hotdesk).
RRQtime >150% Avg this counter shows how many times the heartbeat has been outside of the 55s but also inside of 240s. Indicateing a slow connection.
Error URQ counter shows how many times a phone has timed out or lost registration for what ever reason between hearbeats but within the 240s timeout.
ExistURQ means that the phone was registered on another device or re-registered during the 240s timeout. If the phone registered after the 240s timeout it would be seen as a clean registration.
If all is perfect you will not see any URQ reasons. If there is a ErrorURQ during this time the URQreason shows 'KeepAlive'.
Delay disabled in a trace means that the phone is off hook.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.