I am running into a problem where SER does not recognize a ua trying to ACK a INVITE 200 OK response. It seems to be the result of pairing of certain SIP ua Mfg. Not all UA's exhibit the problem.
1. Destination UA sends 200 OK to ser 2. SER forwards to origin UA 3. Origin ua sends ACK to SER 4. SER declares "sl_filter_ACK: to late to be a local ACK!" 5. destination UA resends 200 OK and does not open talk path, origin device believes call is connected
The ACK seems to arrive just at the right time so I am not sure what the "to late" debug means.
Greetings from the Interop+Networld SIP ilabs hotstage in Santa Clara California. http://www.interop.com/lasvegas2004/interopnet/
- Dustin -
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: SIP Request: Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: method: <ACK> Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: uri: sip:4991@45.210.3.91:5060 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: version: <SIP/2.0> Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: flags=1 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: Found param type 232, <branch> = <z9hG4bK8872b9128>; state=16 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: end of header reached, state=5 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: Via found, flags=1 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: this is the first via Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: After parse_msg... Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: DEBUG : sl_filter_ACK: to late to be a local ACK!
Origin UA 45.210.9.83 SER 45.210.9.21 Dest UA 45.210.3.91
No. Time Source Destination Protocol Info 33 15.496582 45.210.9.83 45.210.9.21 SIP/SDP Request: INVITE sip:4991@45.210.9.21:5060, with session description 34 15.513769 45.210.9.21 45.210.9.83 SIP Status: 100 trying -- your call is important to us 35 15.515818 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE sip:4991@45.210.3.91:5060, with session description 36 15.850049 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE sip:4991@45.210.3.91:5060, with session description 37 16.108079 45.210.3.91 45.210.9.21 SIP Status: 100 Trying 38 16.108576 45.210.3.91 45.210.9.21 SIP Status: 180 Ringing 41 16.140632 45.210.9.21 45.210.9.83 SIP Status: 180 Ringing 48 19.346818 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 49 19.355727 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 50 19.377798 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 51 19.843133 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 52 19.855180 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 53 19.867245 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 56 20.844637 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 57 20.855263 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 58 20.867249 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 63 22.843774 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 64 22.855381 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 69 25.012302 45.210.3.91 45.210.9.21 SIP Request: BYE sip:4991@45.210.9.21:5060;ftag=1B1B70-179F;lr=on 70 25.026340 45.210.9.21 45.210.9.83 SIP Request: BYE sip:45.210.9.83:5060 71 25.057274 45.210.9.83 45.210.9.21 SIP Status: 200 OK 72 25.067464 45.210.9.21 45.210.3.91 SIP Status: 200 OK
SER does not drop the ACK -- it forwards it. ACKs to non-2xx replies are generated localy, that means SER generates and sends the ACK downstream before it forwards the reply upstream. Because of this it must later ignore ACKs coming from upstream elements (because the downstream ACK was already generated). "Too late to be a local ACK" means that SER will not drop this ACK even if it is localy generated (because it is too late) -- it will forward it.
The interval is 2 seconds.
Jan.
On 05-04 23:38, Dustin Goodwin wrote:
I am running into a problem where SER does not recognize a ua trying to ACK a INVITE 200 OK response. It seems to be the result of pairing of certain SIP ua Mfg. Not all UA's exhibit the problem.
- Destination UA sends 200 OK to ser
- SER forwards to origin UA
- Origin ua sends ACK to SER
- SER declares "sl_filter_ACK: to late to be a local ACK!"
- destination UA resends 200 OK and does not open talk path, origin
device believes call is connected
The ACK seems to arrive just at the right time so I am not sure what the "to late" debug means.
Greetings from the Interop+Networld SIP ilabs hotstage in Santa Clara California. http://www.interop.com/lasvegas2004/interopnet/
- Dustin -
Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: SIP Request: Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: method: <ACK> Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: uri: sip:4991@45.210.3.91:5060 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: version: <SIP/2.0> Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: flags=1 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: Found param type 232, <branch> = <z9hG4bK8872b9128>; state=16 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: end of header reached, state=5 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: Via found, flags=1 Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: parse_headers: this is the first via Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: After parse_msg... Apr 5 23:06:22 ser /usr/local/sbin/ser[6282]: DEBUG : sl_filter_ACK: to late to be a local ACK!
Origin UA 45.210.9.83 SER 45.210.9.21 Dest UA 45.210.3.91
No. Time Source Destination
Protocol Info 33 15.496582 45.210.9.83 45.210.9.21 SIP/SDP Request: INVITE sip:4991@45.210.9.21:5060, with session description 34 15.513769 45.210.9.21 45.210.9.83 SIP Status: 100 trying -- your call is important to us 35 15.515818 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE sip:4991@45.210.3.91:5060, with session description 36 15.850049 45.210.9.21 45.210.3.91 SIP/SDP Request: INVITE sip:4991@45.210.3.91:5060, with session description 37 16.108079 45.210.3.91 45.210.9.21 SIP Status: 100 Trying 38 16.108576 45.210.3.91 45.210.9.21 SIP Status: 180 Ringing 41 16.140632 45.210.9.21 45.210.9.83 SIP Status: 180 Ringing 48 19.346818 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 49 19.355727 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 50 19.377798 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 51 19.843133 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 52 19.855180 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 53 19.867245 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 56 20.844637 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 57 20.855263 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 58 20.867249 45.210.9.83 45.210.9.21 SIP Request: ACK sip:4991@45.210.3.91:5060 63 22.843774 45.210.3.91 45.210.9.21 SIP/SDP Status: 200 OK, with session description 64 22.855381 45.210.9.21 45.210.9.83 SIP/SDP Status: 200 OK, with session description 69 25.012302 45.210.3.91 45.210.9.21 SIP Request: BYE sip:4991@45.210.9.21:5060;ftag=1B1B70-179F;lr=on 70 25.026340 45.210.9.21 45.210.9.83 SIP Request: BYE sip:45.210.9.83:5060 71 25.057274 45.210.9.83 45.210.9.21 SIP Status: 200 OK 72 25.067464 45.210.9.21 45.210.3.91 SIP Status: 200 OK
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers