You are tryin to send a reply to the ACK.

Make sure the ACK will be loose_routed.

klaus

Fernando Patzlaff wrote:

Hi all,

I have problem with my SER. It's work fine on the version 0.8.14.

I upgrade its to 0.9.4, but when I make a call from a gateway to another gateway bypassing the SER the call is ended in 15 seconds.

The message appears on tethreal is:

[root@sv02 ser]# tethereal -R sip Capturing on eth0 11.426429 10.128.16.3 -> 10.128.0.11 SIP/SDP Request: INVITE sip:3354@10.128.0.11:5070, with session description 11.428174 10.128.0.11 -> 10.128.16.3 SIP Status: 401 Unauthorized 11.505784 10.128.16.3 -> 10.128.0.11 SIP Request: ACK sip:3354@10.128.0.11:5070 11.528044 10.128.16.3 -> 10.128.0.11 SIP/SDP Request: INVITE sip:3354@10.128.0.11:5070, with session description 0(3732) -> encaminhando para o gv01 asdasdasd 11.531864 10.128.0.11 -> 10.128.16.3 SIP Status: 100 trying -- your call is important to us 11.532865 10.128.0.11 -> 10.128.0.2 SIP/SDP Request: INVITE sip:3354@10.128.0.11:5070, with session description 11.591058 10.128.0.2 -> 10.128.0.11 SIP Status: 100 Trying 13.129865 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 183 Session Progress, with session description 13.130850 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 183 Session Progress, with session description 13.242219 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 180 Ringing, with session description 13.242898 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 180 Ringing, with session description 13.257439 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 200 OK, with session description 13.258149 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 200 OK, with session description 0(3732) ACC: transaction answered: method=INVITE, i-uri=sip:3354@10.128.0.11:5070, o-uri=sip:3354@10.128.0.11:5070, call_id=call-805E8372-0630-DA11-0214-E@10.128.16.3, from=sip:10.128.16.3;tag=a801003-12, code=200 13.406006 10.128.16.3 -> 10.128.0.11 SIP Request: ACK sip:10.128.0.11:5070;ftag=a801003-12;lr=on 0(3732) ACC: request acknowledged: method=ACK, i-uri=sip:10.128.0.11:5070;ftag=a801003-12;lr=on, o-uri=sip:10.128.0.11:5070;ftag=a801003-12;lr=on, call_id=call-805E8372-0630-DA11-0214-E@10.128.16.3, from=sip:10.128.16.3;tag=a801003-12, code=200 0(3732) Warning: sl_send_reply: I won't send a reply for ACK!! 13.755012 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 200 OK, with session description 13.756575 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 200 OK, with session description 14.755003 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 200 OK, with session description 14.756304 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 200 OK, with session description 16.755340 10.128.0.2 -> 10.128.0.11 SIP/SDP Status: 200 OK, with session description 16.756279 10.128.0.11 -> 10.128.16.3 SIP/SDP Status: 200 OK, with session description 45.262004 10.128.0.2 -> 10.128.0.11 SIP Request: BYE sip:10.128.0.11:5070;ftag=a801003-12;lr=on 45.262719 10.128.0.11 -> 10.128.16.3 SIP Request: BYE sip:10.128.16.3 45.336383 10.128.16.3 -> 10.128.0.11 SIP Status: 200 OK 45.336871 10.128.0.11 -> 10.128.0.2 SIP Status: 200 OK

Do they have an idea?

Thanks,

Fernando Patzlaff

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers