Hi Rajib, You can investigate further by turning on trace as described here, and taking a look through the logs around the time of the disconnection.
https://clearwater.readthedocs.io/en/stable/Troubleshooting_and_Recovery.html#bono https://clearwater.readthedocs.io/en/stable/Troubleshooting_and_Recovery.html#sprout Inspecting the diags, poring over a tcpdump capture, should help. Also, this thread might be helpful - in this case, the ACK is being rejected by bono: http://lists.projectclearwater.org/pipermail/clearwater_lists.projectclearwater.org/2015-September/002437.html Cheers, Will From: Clearwater [mailto:clearwater-boun...@lists.projectclearwater.org] On Behalf Of Rajib Rajkhowa Sent: 07 June 2018 05:08 To: clearwater@lists.projectclearwater.org Subject: [Project Clearwater] Call getting disconnected in 30 sec using Clearwater vIMS (old architecture) Hi, I am using old vIMS architecture (for some business reason) where Vellum & Dime are not present. I am using a multi VM setup on OpenStack and for SIP client I am using XLite as SIP client. After a lot of struggle and poring over Clearwater mailing lists, I could resolve most of the initial issues. But now I am facing an issue of call getting disconnected within 30 secs of establishment. Interesting observation made, the calling party session continues to be established only the called party session gets disconnected after 30 sec or 32 sec Anticipating your kind support and suggestion Thanks & regards, Rajib
_______________________________________________ Clearwater mailing list Clearwater@lists.projectclearwater.org http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
