<html><head><base href="x-msg://2453/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Incorrect NAT configuration so one of the boxes is not actually getting a BYE.<div><br></div><div><br><div><div>On Oct 5, 2009, at 3:13 AM, Maciej Aniserowicz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div bgcolor="#ffffff"><div><font size="2" face="Arial">Hi,</font></div><div><font size="2" face="Arial">When I use two FreeSWITCH instances ('internal' and 'external'), all users register to the 'external' instance which acts as a gateway by 'internal' instance (which in turn is controlled by my applicaiton with commands sent by socket).</font></div><div><font size="2" face="Arial">When user hangs up, the 'hanged up' event is propagated to the 'internal' instance after a long time (~3 minutes) instead of being propagated immediately.</font></div><div><font size="2" face="Arial">What can cause this issue?</font></div><div><font size="2" face="Arial"></font></div></div></span></blockquote></div><br></div></body></html>