Yes, agreed…either making it return sips: or adding transport=TLS will fix it.
I will configure a SIP proxy to rewrite the RURI of the ACK to change from sip: to sips: or prefix transport=TLS really quickly to get around this until a fix is issued.
Thanks!
I’ll wait for a fix. thanks for the help.
Turns out that the deploy last night hit a snag. The fix is now actually deployed, let me know if you’re still seeing this issue.
That was it…it’s working now…thanks Justin!
Hello!!! @juberti ! Is there any way that the error occurred again by any chance?? im having the same problem that the same configuration that had previously been working, now it connects but transcripts are silent! Same description Josh was having at the start of this conversation topic.
Thankyou!
@Eugenio it’s still working for me. Do you have a SIP Capture you can share?
what a shame guys 
My tokens had run out… i had to pay more. Thank you very much for your fast response!
We have had to manip sips to sip.
Will this be fixed?