Michal,
In route block 0 I use the following logic for relaying messages.
# Call Tear-Down Section for ACKs - do not account for acks if (method=="ACK") { xlog("L_INFO", "\n[SER]: --ACK--: Time: [%Tf] From: <%fu> To <%tu> Src IP <%is> Method:<%rm>\n"); t_relay(); break; };
-Steve
-----Original Message----- From: Michal Matyska [mailto:michal.matyska@iptel.org] Sent: Friday, August 14, 2009 10:28 AM To: Steven C. Blair Cc: serusers@lists.iptel.org Subject: Re: [Serusers] 200 OK not being ACKnowledged
Steven C. Blair píše v Pá 14. 08. 2009 v 09:30 -0400:
Aug 13 13:07:24 vidar /usr/local/sbin/ser[19053]: [SER]: --ACK--: Time: [Thu Aug 13 13:07:24 2009] From: sip:89390@vidar.net.isc.upenn.edu To sip:92155738396@vidar.net.isc.upenn.edu;user=phone Src IP <128.91.2.223> Method:<ACK>
OK, ACK is received by SER... but is routed incorrectly to itself...
Aug 13 13:07:24 vidar /usr/local/sbin/ser[19053]: [SER]: Too many hops
(qualified guess... to proove it sniff traffic on loopback interface) ... so it ends it the loop, cut off by Max-Forwards limit...
Aug 13 13:07:24 vidar /usr/local/sbin/ser[19053]: Warning: sl_send_reply: I won't send a reply for ACK!!
... it tries to reply 4xx Too many hops, by it's not possible for ACK.
Resume: check your SER script, how you route the 2xx ACK.
Michal