[SR-Users] Persistent dialog

[Jon Bonilla (Manwe)]

Hi all

I'm playing with the dialog module to count the calls and limit the number of
calls per subscriber. 

After configured the proxy I've tested a call and I realize that the dialog
list is not empty after the call ends.

Here's a sample call log and the dialog list while the call was being
stablished and 3 minutes after that:

root at proxy1a:~# grep "fbrzjkplmvlauty at quenya" /var/log/kamailio.log 
New request - M=INVITE
Dialog set mark TOTAL
Proxy authentication failed
New request - M=INVITE
Dialog set mark TOTAL
Dialog set mark user and userout to 'd5a78dafcb93'
Dialog set mark type to outgoing
Call to PSTN
Dialog set mark peer and peerout to '4'
Relaying request
Request leaving server
NAT-Reply - S=100 - Connecting 
NAT-Reply - S=488 - Not Acceptable Here 
Failure route for PSTN call
Unset dialog mark peer and peerout '4' 
Filter reply code 
No failover routing needed for this response code 
New request - M=ACK


While the call was being stablished or just after it was dropped (quickly)
sercmd> dlg.list

hash:3837:638039689 state:1 timestart:0 timeout:0
  callid:fbrzjkplmvlauty at quenya from_tag:inobo to_tag:
  from_uri:sip:123456789 at labsip.com
  to_uri:sip:0043987654321 at labsip.com
  caller_contact:sip:123456789-sbhn1naovm6bc at 111.111.111.164:5060;transport=udp
caller_cseq:149 
  caller_route_set:<sip:111.111.111.135;r2=on;lr=on;ftag=inobo;nat=yes>,<sip:111.111.111.100;r2=on;lr=on;ftag=inobo;nat=yes>
  callee_contact: callee_cseq: callee_route_set:
  caller_bind_addr:udp:111.111.111.138:5062 callee_bind_addr: 


hash:3837:638039690 state:5 timestart:0 timeout:0 
  callid:fbrzjkplmvlauty at quenya
  from_tag:inobo to_tag:
  from_uri:sip:123456789 at labsip.com
  to_uri:sip:0043987654321 at labsip.com
  caller_contact:sip:123456789-sbhn1naovm6bc at 111.111.111.164:5060;transport=udp
  caller_cseq:150 caller_route_set:
  <sip:111.111.111.135;r2=on;lr=on;ftag=inobo;nat=yes>,<sip:111.111.111.100;r2=on;lr=on;ftag=inobo;nat=yes>
  callee_contact: callee_cseq: callee_route_set:
  caller_bind_addr:udp:111.111.111.138:5062 callee_bind_addr:


After a couple of minutes:

hash:3837:638039689 state:1 timestart:0 timeout:0
        callid:fbrzjkplmvlauty at quenya from_tag:inobo to_tag:
        from_uri:sip:123456789 at labsip.com
	to_uri:sip:0043987654321 at labsip.com
	caller_contact:sip:123456789-sbhn1naovm6bc at 111.111.111.164:5060;transport=udp
caller_cseq:149 
	caller_route_set:
<sip:111.111.111.135;r2=on;lr=on;ftag=inobo;nat=yes>,<sip:111.111.111.100;r2=on;lr=on;ftag=inobo;nat=yes>
	callee_contact: callee_cseq: callee_route_set:
	caller_bind_addr:udp:111.111.111.138:5062 callee_bind_addr:


sercmd> dlg.profile_get_size total
Profile:total => profile:total value: count:1
sercmd> dlg.profile_get_size user
Profile:user => profile:user value: count:0
sercmd> dlg.profile_get_size userout
Profile:userout => profile:userout value: count:0
sercmd> dlg.profile_get_size peer
Profile:peer => profile:peer value: count:0
sercmd> dlg.profile_get_size peerout
Profile:peerout => profile:peerout value: count:0


Obviously, there's no such a call. But my dialog profile TOTOAL say's there's
one, which is listed by sercmd. The dialog is persistent, I guess it will be
destroyed after 12 hours, but I'd like to know why it's still there if I
received a negative response and the ACK for it.


Thanks,

Jon