All,
is any of you aware about limitation how many reg entries can be stored in s-cscf for 1 contact ? From what I'm observing here : s-cscf can have up to 12 reg entries for 1 contact and then other entries are silently discarded.
Use case:
- crash of app happens 12 times
- app retries to register
- s-cscf sends back 200 OK with 13 contacts
- another app registers and tries to send SIP MESSAGE to 1st app
Result: message never gets delivered and tcpdump shows 12 messages sent out to p-cscf but not 13th one which is actually live session between client and proxy.
thanks
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.
Hi Dan,
There is a hard coded limit on the number of branches that a SIP transaction can have in Kamailio, i.e. number of forked destinations It is currently set to 12 (defined in config.h).
Some people with other use cases have recompiled with a higher limit, but this may cause further problems for you (extra requests to generate & send and responses to process when the dead connections timeout)
You've already asked on this list about the 'allow single registration' feature in ims_registrar and the tcp connection lost detection, which are the usual solutions to this. Another solution may be to try integrating the outbound functionality into the IMS example configs which can detect when flows fail, and use that to delete the dead location entries.
Regards, Hugh
From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Ciprus, Daniel Sent: 17 June 2014 22:02 To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] s-cscf - limit of entries for 1 contact
All,
is any of you aware about limitation how many reg entries can be stored in s-cscf for 1 contact ? From what I'm observing here : s-cscf can have up to 12 reg entries for 1 contact and then other entries are silently discarded.
Use case:
- crash of app happens 12 times
- app retries to register
- s-cscf sends back 200 OK with 13 contacts
- another app registers and tries to send SIP MESSAGE to 1st app
Result: message never gets delivered and tcpdump shows 12 messages sent out to p-cscf but not 13th one which is actually live session between client and proxy.
thanks
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.
________________________________ 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.
?Thanks Hugh,
Wondering why 12 and not 11 ? ;-) Anyway, seems like we're hitting this limit. This is just a consequence from crashing application trying to re-register again and again.
________________________________ From: sr-users-bounces@lists.sip-router.org sr-users-bounces@lists.sip-router.org on behalf of Waite, Hugh hugh.waite@acision.com Sent: Tuesday, June 17, 2014 6:46 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] s-cscf - limit of entries for 1 contact
Hi Dan,
There is a hard coded limit on the number of branches that a SIP transaction can have in Kamailio, i.e. number of forked destinations It is currently set to 12 (defined in config.h).
Some people with other use cases have recompiled with a higher limit, but this may cause further problems for you (extra requests to generate & send and responses to process when the dead connections timeout)
You've already asked on this list about the 'allow single registration' feature in ims_registrar and the tcp connection lost detection, which are the usual solutions to this. Another solution may be to try integrating the outbound functionality into the IMS example configs which can detect when flows fail, and use that to delete the dead location entries.
Regards, Hugh
From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Ciprus, Daniel Sent: 17 June 2014 22:02 To: Kamailio (SER) - Users Mailing List Subject: [SR-Users] s-cscf - limit of entries for 1 contact
All,
is any of you aware about limitation how many reg entries can be stored in s-cscf for 1 contact ? From what I'm observing here : s-cscf can have up to 12 reg entries for 1 contact and then other entries are silently discarded.
Use case:
- crash of app happens 12 times
- app retries to register
- s-cscf sends back 200 OK with 13 contacts
- another app registers and tries to send SIP MESSAGE to 1st app
Result: message never gets delivered and tcpdump shows 12 messages sent out to p-cscf but not 13th one which is actually live session between client and proxy.
thanks
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.
________________________________ 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.
________________________________ 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.
-
Ciprus, Daniel -
Waite, Hugh