Hi,
I am having a situation where the client sends each RE-REGISTER with a new Call-ID, causing it to create a new entry in the location table.
The problem is that this client sends the Re-REGISTER in a Expires/2 time, and as the RFC says, the 200ok is sent with the 2 contacts, with each expire, then the client receive this 2 contacts with 2 expires and "thinks" that it should renew the REGISTER for the old contact and sends a new REGISTER, with a new Call-ID, and adds another entry in the location table, which causes the response returns 3 contacts with 3 expires, and so on...
There is some way to handle this issue?
Thanks Lucio
Hi Lucio,
It looks like a buggy client - The client must internally keep the status of each contact he registered and do the registrations based on this status.
Regards, Bogdan
Lucio Maciel wrote:
Hi,
I am having a situation where the client sends each RE-REGISTER with a new Call-ID, causing it to create a new entry in the location table.
The problem is that this client sends the Re-REGISTER in a Expires/2 time, and as the RFC says, the 200ok is sent with the 2 contacts, with each expire, then the client receive this 2 contacts with 2 expires and "thinks" that it should renew the REGISTER for the old contact and sends a new REGISTER, with a new Call-ID, and adds another entry in the location table, which causes the response returns 3 contacts with 3 expires, and so on...
There is some way to handle this issue?
Thanks Lucio
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users