<html><body>
<DIV>Thank you very much. You are absolutely correct. Removed the lookup and relied on loose-route and problem is solved.</DIV>
<DIV> </DIV>
<DIV class=signature id=signature>Jim</DIV>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR><BR>> <BR>> <BR>> jim.pafford@comcast.net wrote: <BR>> > In ser 0.9.3 I am seeing the following problem with a parallel forking <BR>> > scenario. The SER is sending the final Request ACK to the wrong location <BR>> > every time. Is there a way to fix this. See below: <BR>> > <BR>> > Endpoint (xyz@1.1.1.1 <mailto:xyz@1.1.1.1>) sends <BR>> > Invite(abc123@proxy.com <mailto:abc123@proxy.com>) to the SER. <BR>> > SER looks up location and then sends the following three messages: <BR>> > TRYING back to (xyz@1.1.1.1 <mailto:xyz@1.1.1.1>) <BR>> > INVITE to abc123@2.2.2.2 <mailto:abc123@2.2.2.2><BR>> > INVITE to abc123@3.3.3.3 <mailto:abc123@3.3.3.3><BR>> > <BR>> > This looks good so far. <BR>> > SER then gets back ringing from both endpoints and sends along to <BR>> > xyz@1.1.1.1 <mailto:xyz@1.1.1.1><BR>> > <BR>> > abc123@3.3.3.3 <mailto:abc123@3.3.3.3>answers the call and sends back OK <BR>> > SER then sends OK to xyz@1.1.1.1 <mailto:xyz@1.1.1.1>- Still good <BR>> > SER then sends CANCEL to abc123@2.2.2.2 <mailto:abc123@2.2.2.2><BR>> > abc123@2.2.2.2 <mailto:abc123@2.2.2.2>responds with 200 Canceling - so <BR>> > far so good. <BR>> > <BR>> > Now xyz@1.1.1.1 <mailto:xyz@1.1.1.1>sends the ACK to (abc123@proxy.com <BR>> > <mailto:abc123@proxy.com>) - Still looks good. <BR>> > <BR>> > But now after looking up location for abc123 SER sends the ACK to the <BR>> <BR>> Do you use lookup(location) for ACK? This is not necessary. It should be <BR>> handled in loose_route section. <BR>> <BR>> klaus <BR>> <BR>> <BR>> > wrong endpoint abc123@2.2.2.2 <mailto:abc123@2.2.2.2><BR>> > <BR>> > What am I doing wrong? SER always sends the ACK back to the first <BR>> > address in the list as shown by serctl ul show abc123. Is there a way <BR>> > to correct this so that SER knows the correct endpoint to relay the ACK <BR>> > to? Seems like it should understand which endpoint sent back the OK to <BR>> > the original INVITE and then send the ACK to that endpoint and not the <BR>> > first one in the list after a location lookup. <BR>> > <BR>> > thanks, <BR>> > Jim <BR>> > <BR>> > <BR>> > ------------------------------------------------------------------------ <BR>> > <BR>> > _______________________________________________ <BR>> > Serusers mailing list <BR>> > serusers@lists.iptel.org <BR>> > http://lists.iptel.org/mailman/listinfo/serusers </BLOCKQUOTE></mailto:abc123@2.2.2.2></mailto:abc123@proxy.com></mailto:xyz@1.1.1.1></mailto:abc123@2.2.2.2></mailto:abc123@2.2.2.2></mailto:xyz@1.1.1.1></mailto:abc123@3.3.3.3></mailto:xyz@1.1.1.1></mailto:abc123@3.3.3.3></mailto:abc123@2.2.2.2></mailto:xyz@1.1.1.1></mailto:abc123@proxy.com></mailto:xyz@1.1.1.1></body></html>