You would have to look at a debug log to find out more of what was causing this <span></span><br><br>On Monday, June 29, 2015, Vishal Sharma &lt;<a href="mailto:vishal.sharma@knowlarity.com">vishal.sharma@knowlarity.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hi All,<br></div>I am using ESL to control the call flow.<br></div>My initial call flow is as following<br><br></div>1.      INVITE---&gt; FS<br><div>2.      180&lt;--------|<br>3.      200&lt;--------|<br></div><div>4.      ------------&gt;ACK<br></div><div>5.     *************|--------------&gt;INVITE<br>6.     *************|&lt;---------------180<br></div><div>7.     BYE-------&gt;|<br></div><div>8.     Retransmissions of BYE<br></div><div>9.     *************|&lt;----------------200 OK<br></div><div>10.   200(bye)&lt;---|<br><br><br><br></div><div>Now Leg B remains hanging... Shouldn&#39;t FS have killed it since legA is dead.<br>legB was generated using bridge command.<br><br></div>On Application I get Channel Hangup on 200 bye.<br></div></div>In channle hangup . there is no legB uuid hence application neither can disconnect the legB nor it can wait on any events/messages.<br><br></div><div>This issue seems to sofia related.<br></div><div><br><br></div><div>Regards,<br></div><div>Vishal Sharma f<br></div><div><div><br><br><div><br><br></div></div></div></div>

<br>
SuperReceptionist is now available on Android mobiles. Track your 
business on the go with call analytics, recordings, insights and more: <a href="https://play.google.com/store/apps/details?id=com.superreceptionist" target="_blank">Download the app here</a></blockquote>