Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-13 Thread Alex Balashov
Daniel, On 03/12/2014 04:27 AM, Daniel-Constantin Mierla wrote: On 11/03/14 18:44, Alex Balashov wrote: We appear to have fixed this problem by calling dlg_manage() before doing any set_dlg_profile() manipulations. The documentation is not clear on whether dlg_manage() needs to be called fir

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-13 Thread Daniel-Constantin Mierla
On 12/03/14 16:58, Brooks Bridges wrote: Do you happen to have any additional information about this? No time to look over the code, I might mix it with the plans for designing ng version. I've referenced the documentation for both dialog and dialog_ng, and there's no mention of reuse that f

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-12 Thread Brooks Bridges
Do you happen to have any additional information about this? I've referenced the documentation for both dialog and dialog_ng, and there's no mention of reuse that fits this description. We've confirmed that calling dlg_manage() on a new authenticated invite does result in a second entry in th

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-12 Thread Daniel-Constantin Mierla
On 11/03/14 18:44, Alex Balashov wrote: We appear to have fixed this problem by calling dlg_manage() before doing any set_dlg_profile() manipulations. The documentation is not clear on whether dlg_manage() needs to be called first before doing this. But it makes me wonder: if dlg_manage() is

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-12 Thread Daniel-Constantin Mierla
Are you using the latest 4.1.x? There was a fix related to the counting of the dialog in profile, by removing it from profiles when the call gets to terminated state. The dialog is still kept for a bit in memory after termination and was blocking new calls as the user appear to still have anoth

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-11 Thread Alex Balashov
I do wonder if this [relatively new] setting is relevant: http://kamailio.org/docs/modules/4.1.x/modules/dialog.html#idp1930160 We don't have it set. Since the default value of this is '1', it makes me wonder if, in the olden days, when one used a flag, it was inconsequential to mess with pro

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-11 Thread Alex Balashov
We appear to have fixed this problem by calling dlg_manage() before doing any set_dlg_profile() manipulations. The documentation is not clear on whether dlg_manage() needs to be called first before doing this. But it makes me wonder: if dlg_manage() is prerequisite, then why would the profile

Re: [SR-Users] Bizarre dialog profile tracking behaviour

2014-03-11 Thread Alex Balashov
Something I should probably add: On 03/11/2014 10:28 AM, Alex Balashov wrote: Hello, We've got an issue we've been trying to track for days with 'dialog', where the dialogs go through the following life cycle: 1. INVITE --> 2. <-- 407 challenge 3. ACK --> 4. INVITE --> 5. <-- 100 Trying 6. <-

[SR-Users] Bizarre dialog profile tracking behaviour

2014-03-11 Thread Alex Balashov
Hello, We've got an issue we've been trying to track for days with 'dialog', where the dialogs go through the following life cycle: 1. INVITE --> 2. <-- 407 challenge 3. ACK --> 4. INVITE --> 5. <-- 100 Trying 6. <-- 180 Ringing 7. <-- 183 Session Progress 8. <-- 200 OK 9. ACK --> 10. BYE -->