Lost Registration on Register Expires |
|
I've recently run into an issues where my PAP2T will lose registration once the registration expires and it attempts to re-register. It fails to re-register on expiration, so it goes into a timeout (that I set to 30 seconds), retries and then will be successful.
The second port on the PAP2T registers to a different registry, and uses the same "registration expires" amount, but does not have issues with lost registration.
Before having this issue I also noticed also when my network experiences heavy traffic flow, the ata will lose registration to pbxes, but will stay connected to the other registry.
I'm using a stun server to aid with nat, which up til now has been working flawlessly. I've read that nat keep-alive is enabled at pbxes, must it be activated through the web gui, or is it enough to activate it in the ata?
What would you recommend for the nat keep alive interval, and what do you recommend for ata re-registration interval? I am using QoS to prioritze the PAP2T, which has helped keep good voice quality while on a call.
edit: I was checking my ata's connection remotely over vpn, which I believe is generating the sufficient amount of traffic to cause it to fail to re-registering. I'm wondering if this has to do with the nat keep-alive. I left it at the default 15 seconds, but maybe this value is too small? The other registry does not have issues like I said, so I'm amiss as to what the problem might be.
This post has been edited 3 time(s), it was last edited by lan on 16.08.2011 at 18:32.
|