Friends, Any thoughts...

-VG

On Tue, Aug 26, 2014 at 6:03 AM, Veerabhara Gundu gveerab@gmail.com wrote:

Hello Friends,

I have a scenario, where clients are going away and re-registering with new IP and Port numbers. Presence server keep sending NOTIFY messages for both old Subscription and new Subscription for same clients till the old subscription expires. It's unnecessary traffic and processing on both client and server.

I am looking for a way to force Kamailio to use one subscription per user similar to mode:04 of location table. If it's not possible, looking for a way to remove subscription from config file when I detect this error.We have an option to remove automatically Subscription when NOTIFY failed, but this is not working for TCP based clients. In TCP mode, when Kamailio not event trying to send NOTIFY if Kamailio already knows that TCP connection is broken and replying with 500 error.

Any alternative suggestion also welcome.

Thanks, Veera

Thanks, VG

any help on this?

Thanks, Veera

On Tue, Aug 26, 2014 at 6:03 AM, Veerabhara Gundu gveerab@gmail.com wrote:

Hello Friends,

I have a scenario, where clients are going away and re-registering with new IP and Port numbers. Presence server keep sending NOTIFY messages for both old Subscription and new Subscription for same clients till the old subscription expires. It's unnecessary traffic and processing on both client and server.

I am looking for a way to force Kamailio to use one subscription per user similar to mode:04 of location table. If it's not possible, looking for a way to remove subscription from config file when I detect this error.We have an option to remove automatically Subscription when NOTIFY failed, but this is not working for TCP based clients. In TCP mode, when Kamailio not event trying to send NOTIFY if Kamailio already knows that TCP connection is broken and replying with 500 error.

Any alternative suggestion also welcome.

Thanks, Veera

Thanks, VG