Hi Max,
I was able to track this down to something else entirely. We are using Twilio and everything works for the first 25 minutes. WCS5 sends a SIP UPDATE after 25 minutes which Twilio responds to with a 405 METHOD NOT SUPPORTED and then WCS5 immediately terminates the call. Is this UPDATE...
Further debugging, found that WCS is sending a SIP update to Twilio at 25 minutes into the call and Twilio is responding with 405 - Method Not Allowed. Once Twilio returns this 405 the call is dropped.
Why is WCS consistently sending an UPDATE message at 25 minutes? If there a way around this...
Thank you for the response. We are hitting a Twilio SIP domain after following the instructions at https://flashphoner.com/docs/wcs5/184/html/en/wcs-user-guide/sip_as_rtmp_with_twilio.htm and I just noticed that this must have been an issue before since WCS has the setting to generate an...
Using Web Call Server Version 5.2.755
I'm passing the following to /rest-api/call/startup
{
"callId": "1234567",
"callee": "1234567",
"hasVideo": false,
"hasAudio": false,
"sipLogin": "[login]",
"sipAuthenticationName": "[authName]",
"sipPassword": "[password]"...