[OpenSIPS-Users] assigning dialog profiles

[Jeff Pyle]

Bogdan,

I have not been able to reproduce it.  It seems to be a rare occurrence.
Unfortunately I can't leave logging set to 6 because it would prevent me
from continued development on the box.  If it happens again I'll try to take
note of exactly what I had been doing up until that point to see if I can
reproduce it.



- Jeff



On 3/9/09 2:44 PM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:

> Hi Jeff,
> 
> If you can reproduce this, can you get a full log (use debug=6) for the
> call ? It looks like a double de-allocation of the mem chunk.
> 
> Thanks and regards,
> Bogdan
> 
> Jeff Pyle wrote:
>> Hi Bogdan,
>> 
>> I just encountered a new error.  Here's what the log had to say about it:
>> 
>>  Unassigning dialog profile value no
>>  CRITICAL:core:qm_free: freeing already freed pointer, first free:
>> dlg_profile.c: destroy_linkers(234) - aborting
>>  INFO:core:handle_sigs: child process 29729 exited by a signal 6
>>  INFO:core:handle_sigs: core was not generated
>>  INFO:core:handle_sigs: terminating due to SIGCHLD
>> 
>> The first line is from this:
>>   xlog("L_INFO", "Unassigning dialog profile value $avp(s:dlgid_out)\n");
>> 
>> I'm not sure where the "no" came from.
>> 
>> 
>> 
>> - Jeff
>> 
>> 
>> 
>> On 3/9/09 12:51 PM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:
>> 
>>   
>>> Hi Jeff,
>>> 
>>> The error message translates in receiving the ACK before finishing
>>> processing the 200 OK....It is race I know about and I'm planing the fix it.
>>> 
>>> In regards to "opensipsctl fifo dlg_list", by restart, you mean crash?
>>> does the log says something about?
>>> 
>>> Thanks and regards,
>>> Bogdan
>>> 
>>> Jeff Pyle wrote:
>>>     
>>>> Hi Bogdan,
>>>> 
>>>> I updated from svn and the dialog profile assignments seem to be behaving
>>>> now.
>>>> 
>>>> However, I get this error:
>>>> 
>>>> CRITICAL:dialog:log_next_state_dlg: bogus event 6 in state 2 for dlg
>>>> 0xb614953c [3865:384697978] with clid
>>>> '5f55f99253a9471f3672b30a49367e92 at ww.xx.yy.zz' and tags 'as4156018e' ''
>>>> 
>>>> It shows up when the call goes to 200 OK on the second PSTN carrier, after
>>>> failing on the first one, if that's relevant.
>>>> 
>>>> The dialog still shows up in the database in the proper profile with the
>>>> proper value.
>>>> 
>>>> I don't know if this is related, but until just a moment ago anytime I ran
>>>> "opensipsctl fifo dlg_list", Opensips would restart.  I moved debug to 6,
>>>> then to 4, and then back to 3.  And it didn't happen anymore.  Odd.
>>>> 
>>>> 
>>>> - Jeff
>>>> 
>>>> 
>>>> 
>>>> On 3/9/09 10:29 AM, "Bogdan-Andrei Iancu" <bogdan at voice-system.ro> wrote:
>>>> 
>>>>   
>>>>       
>>>>> Hi Jeff,
>>>>> 
>>>>> Thank you for the report - there was a bug in the new code (when
>>>>> create_dialog() was added), but now it is fixed on SVN.
>>>>> 
>>>>> Please update and test again with your initial configuration (see the
>>>>> email I sent to Brett).
>>>>> 
>>>>> Regards,
>>>>> Bogdan
>>>>> 
>>>>> Jeff Pyle wrote:
>>>>>     
>>>>>         
>>>>>> Hello,
>>>>>> 
>>>>>> I'm configuring Opensips' dialog module to keep count of the number of
>>>>>> calls
>>>>>> I have on each outbound PSTN carrier.  Here's my thinking:
>>>>>> 
>>>>>> In request route:
>>>>>> - create_dialog() on new INVITE
>>>>>> - select carrier
>>>>>> - set_dlg_profile() to assign to proper profile with this carrier's value
>>>>>> 
>>>>>> In failure route:
>>>>>> - unset_dlg_profile() to remove from profile, since it failed
>>>>>> - send to original request route to select next carrier, assign profile,
>>>>>> etc
>>>>>> 
>>>>>> When I run this, the first set_dlg_profile() works properly, but the
>>>>>> unset_dlg_profile() in the failure route logs:
>>>>>> 
>>>>>>  ERROR:dialog:unset_dlg_profile: dialog was not yet created - script
>>>>>> error
>>>>>>  ERROR:dialog:w_unset_dlg_profile: failed to unset profile
>>>>>> 
>>>>>> All subsequent set/unset_dlg_profile give the same error.  Does the
>>>>>> dialog
>>>>>> somehow get destroyed when the failure_route is hit?  Is it necessary to
>>>>>> create_dialog() each time the failure_route is hit by sending it back
>>>>>> around
>>>>>> to a request route?
>>>>>> 
>>>>>> 
>>>>>> Thanks,
>>>>>> Jeff
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.opensips.org
>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>> 
>>>>>>   
>>>>>>       
>>>>>>           
>>>>   
>>>>       
>> 
>> 
>>   
>