On Tue, Feb 7, 2012 at 7:42 PM, Boudewyn Ligthart <bligthart@btlnet.co.uk>wrote:
** **
Hi,****
** **
We have been testing with Freeswitch (hacked-20120106T151802Z). There are two profiles, allowing calls through using ACL, the core is running with ODBC on MySQL, all running on ubuntu, virtualized in XEN. ****
** **
When testing with SIPP and standard uac towards Freeswitch there are no issue’s with the SIP messaging,****
SIPP on another machine acts as uas. So call flows SIPP à Freeswitch àSIPP. ****
** **
When testing with SIPP (using same routing) streaming audio after about 100 calls (5 seconds in) there are unexpected ****
BYE’s coming from Freeswitch (I have even lowered the CPS count). ****
** **
I do not see any error’s in the logs, just the BYE’s. What could be causing this issue?
FS might tell you something in the header Reason in the BYE. On a normally terminated call it would be like this: Reason: Q.850;cause=16;text="NORMAL_CLEARING" Other than that, set loglevel to "debug" to check what FS is deciding to do. regards, Takeshi