Hi Uwe, please see my previous email regarding the traces.
Regards, Bogdan Uwe Kastens wrote: > Hi, > > If I use db_mode=1 the dialog is deleted from the database (as expected) > but not from the memory. I will test with a fresh installation and maybe > open a bug report. > > BR > > Uwe > > > Uwe Kastens schrieb: > >> Hi again, >> >> So I think it might be a bug. One direction (UA to PSTN) works everytime >> perfectly. It doesn't matter on which side the BYE is sent. If I try the >> other direction, the dialog will not be removed. Again it won't matter >> on which side the BYE is sent - the dialog will stay active. >> >> Unfort I was not able to find out what the states and the events means. >> So its not easy to debug further. >> >> Working direction: >> DBG:dialog:next_state_dlg: dialog 0xd7a30870 changed from state 1 to >> state 2, due event 2 >> DBG:dialog:next_state_dlg: dialog 0xd7a30870 changed from state 2 to >> state 3, due event 3 >> DBG:dialog:next_state_dlg: dialog 0xd7a30870 changed from state 3 to >> state 4, due event 6 >> DBG:dialog:next_state_dlg: dialog 0xd7a30870 changed from state 4 to >> state 4, due event 6 >> DBG:dialog:next_state_dlg: dialog 0xd7a30870 changed from state 4 to >> state 4, due event 1 >> >> Not Working >> DBG:dialog:next_state_dlg: dialog 0xd7a2c6e0 changed from state 1 to >> state 2, due event 2 >> DBG:dialog:next_state_dlg: dialog 0xd7a2c6e0 changed from state 2 to >> state 2, due event 2 >> DBG:dialog:next_state_dlg: dialog 0xd7a2c6e0 changed from state 2 to >> state 3, due event 3 >> DBG:dialog:next_state_dlg: dialog 0xd7a2c6e0 changed from state 3 to >> state 5, due event 7 >> DBG:dialog:next_state_dlg: dialog 0xd7a2c6e0 changed from state 5 to >> state 5, due event 1 >> >> Anyone could help please? >> >> BR >> >> Uwe >> >> >> Uwe Kastens schrieb: >> >>> Hello again, >>> >>> I think the dialog is destroyed, if no reference is left. And so I asume >>> the dialog is missing the ACK for the BYE. Or do I need to unref it >>> manually via reply_route? I will attach the log. >>> >>> dialog:: hash=440:1838775488 >>> state:: 5 >>> user_flags:: 0 >>> timestart:: 1246005835 >>> timeout:: 0 >>> callid:: [email protected] >>> from_uri:: sip:[email protected]:5100 >>> from_tag:: as619609ab >>> caller_contact:: sip:[email protected]:5100 >>> caller_cseq:: 102 >>> caller_route_set:: >>> caller_bind_addr:: udp:10.20.138.125:5100 >>> to_uri:: sip:[email protected]:5100 >>> to_tag:: ZdwulVArZJyQZ6lMpIk9pvPlzPV73upl >>> callee_contact:: sip:[email protected]:5060 >>> callee_cseq:: 102 >>> callee_route_set:: >>> <sip:10.20.138.145;lr;ftag=as619609ab;did=8b1.8ddb7a7> >>> callee_bind_addr:: udp:10.20.138.125:5100 >>> >>> BR >>> >>> Uwe >>> >>> Uwe Kastens schrieb: >>> >>>> Hello list, >>>> >>>> I am using DIALOG for the Concurrent calls limitation following the >>>> tutorial. Its working pretty well - in one direction :-) >>>> >>>> DIALOGs from UA to PSTN are deleted after processing the BYE. In the >>>> other direction I see that the BYE is processed correctly, but DIALOGs >>>> are staying in state 5. >>>> >>>> Where can I find the documentation for the states? Which will delete a >>>> DIALOG. The BYE or the ack for the BYE? >>>> >>>> >>>> BR >>>> >>>> Uwe >>>> >>>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> > > > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
