No subject


Wed Jun 24 00:39:36 CEST 2009


The captured ACK msg:

U 67.154.255.47:4060 (P1) -> 67.154.255.44:5060 (i-cscf)
ACK sip:alice at centercall.net SIP/2.0.


The two ACK msg is different.=20


Questions:

(1) How can I generate the correct ACK msg in this case?

(2) The issue with second ACK need more explaination ( from openims
point of view):

i-cscf ---- s-cscf =20
         |       =20
 U1 --> P1 --> U2

(i/s-cscf is sip proxy)

With this kind of ACK, the ACK first goes to i-cscf, which choose
s-cscf, then goes back to P1, P1 will try to relay the ACK

route[Term_Subsequent]{
   ...
	if (!P_security_relay())
	   P_NAT_relay();

	t_relay()
  ...
}

The log shows:

22106 Mar  2 11:06:25 im1 /usr/sbin/ser[27551]: DEBUG: tm
[t_funcs.c:184]: tm: put_on_wait: transaction 0xb59834b4 already on wait

It seems the tm module put this new ACK (the P1-generated ACK loop back
to P1 now )  on hold, NOT relaying to U2.=20



More information about the sr-dev mailing list