Should be easy to verify. Four contacts should generate four REGISTER messages. However, the ngrep of OK does not show four contacts with four different ports with the same expiry.
This is what it looks like to me: - The client registers more often than expiry time (some clients can set expiry and register interval separately) or your reboot causes this - This means that the client will re-register before the contact has expired in SER - The client is behind a NAT where port allocation is done in a serialized fashion, i.e. the port is not re-used, but each time a new REGISTER is done, a new port is allocated - This again means that the NAT probably does not support external NAT keepalive (I assume you use nathelper/mediaproxy) and the NAT binding will expire - You should then get a rotation of 10 active contacts if the client registers every 360 seconds with expiry 3600
Makes sense? ;-) g-)
Iqbal wrote:
the expire times do vary, the thing is they get all created on register at the same time, so I have 4 contacts for a new registers.
Iqbal
Klaus Darilion wrote:
MAybe the NAT binding disappears and a new port will bu used by the NAT device. If you use nathelper, then you will save teh port of the new binding.
Do the contacts vary in their expire time? Yes: NAT problem No: ? client problem?
klaus
Iqbal wrote:
Hi
I have a really strange problem, when I am registering a IP phone, which is connected to a simple 4 port router, it i submitting multiple contacts into the db.
Even in the sip messages I can see multiple entries, the IP:port pairs only differ in the port numbers. Anyone else had this problem,
Iqbal
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers