On Wednesday 11 June 2008, Henning Westerholt wrote: > if you don't use record routing the module can't track all the messages > from the dialog, so the internal dialog state will be different. But i can > confirm the problem with the timeout_avp value, i've did some tests with > your configuration.
It seems that in this case the AVP value is not valid, and the default timeout is used. Some logs (from trunk): Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:dlg_onroute: route param is '494.7573c3' (len=10) Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:lookup_dlg: ref dlg 0xb5c61e50 with 1 -> 3 Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:lookup_dlg: dialog id=3946327 found on entry 1172 Jun 11 14:37:52 ca ../openser[23446]: DBG:core:parse_headers: flags=48 Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:next_state_dlg: dialog 0xb5c61e50 changed from state 3 to state 4, due event 6 Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:dlg_onroute: sequential request successfully processed Jun 11 14:37:52 ca ../openser[23446]: INFO:dialog:get_dlg_timeout: invalid AVP value, use default timeout Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:insert_dlg_timer_unsafe: inserting 0xb5c61e78 for 43211 Jun 11 14:37:52 ca ../openser[23446]: DBG:dialog:dlg_update_cseq: cseq is 20 Jun 11 14:37:52 ca ../openser[23446]: DBG:uri:has_totag: totag found Henning _______________________________________________ Users mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/users
