Hello,
Thanks for the replies guys!
Juha was right, it's the client... funny thing, though:
When calling:
Client->kamailio->asterisk->gw This works fine...
But when calling:
Client->kamilio->freeswitch->gwThis does NOT work...
I'm thinking maybe there's some topology hiding somewhere,
Kamailio could be ending the call, though it may also be one of the
endpoints.
Anyway, if your clients are dialing sips: URIs, then it is required that
the signaling be TLS end-to-end. If you are trying to translate TLS to TCP,
you should use sip:u...@domain.com;transport=tls. This should enforce
David Villasmil writes:
> I have a kamailio 4.2.8 receiving on tls and i'm trying to forward on tcp,
> but AFTER the call is established, kamailio hangs the call with "SIPS
> required"...
Are you sure that it is K that hangs the established call?
-- Juha
Hello Guys,
I have a kamailio 4.2.8 receiving on tls and i'm trying to forward on tcp,
but AFTER the call is established, kamailio hangs the call with "SIPS
required"...
Has this happened to anyone?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
ᐧ
___