Hello,

Another dialog got stuck in kamailio, so I checked a few kamctl commands. This is what I found.

When viewing the profile size the count is 0 (using kamctl fifo profile_get_size [NAME])

When using the kamctl fifo get_statistics all command, the dialog:active_dialogs shows 1. There are no other calls active at this point, so this must be the one that got stuck.

The call is still in state 4. I don’t know what this means, but I’m guessing active.

Why did the dialog module fail to release this dialog? The profile was configured to allow 2 concurrent calls. We called the number using two phones and only one made it through.

Is this a bug?

Regards,

Grant

From: sr-users-bounces@lists.sip-router.org [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Grant Bagdasarian
Sent: Monday, April 22, 2013 10:55 AM
To: sr-users@lists.sip-router.org
Subject: [SR-Users] Kamailio dialog termination

Hello,

Using the dialog module. According to the documentation a dialog is automatically destroyed when a BYE is received. In case of no BYE, the dialog lifetime is controlled via the default timeout.

I’m assuming the dialog module only creates a dialog when a 200 OK is received on the INVITE. So if a CANCEL request is sent for this INVITE or the server answers with anything but a 200 OK, no dialog is created and maintained by the dialog module?

Also, when the dialog is terminated, is it guaranteed the dialog entry is removed from memory at all times, but there might be a chance the dialog remains stored in the database table because of some error? I’m using the dialog module to control the number of calls allowed to a certain destination, but it sometimes does occur that an entry in the database is not removed, but I’m not sure if the dialog is also removed from memory when this happens.

I hope someone could clear this out for me.

Thanks,

Grant