All,
This is just a placeholder for issue we're facing in our deployment of Kamailio IMS core : client uses TCP to send REGISTER. Occasionally client crashes/lost connection so new REGISTER is sent towards P-CSCF. Instead of removing old registration (there is no
way to match these obviously) P-CSCF will create new entry and keeps this information for future use. Once SIP request is sent out to the contact, P-CSCF uses all registration entries in the memory and forks requests to all destinations (which are in most
cases unreachable). This creates flood of timeouts from S-CSCF towards AS and sometimes bad timing is even causing calls not being processed since 408 Request Timeout is delivered sooner than 200 OK. I'm pretty sure Carsten is aware about this issue that's
why this note at very beginning about "placeholder"
thank you
Dan.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed
to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.