Author
Topic: Life without UDP 5060 (Read 4063 times)

Seems like no calls possible if there's no udp listener on port 5060.If default listener is tcp or tls then both client hang up in 15 seconds, no voice is transmitted.If I setup 2 listeners, one tcp, another udp, setup both clients to use tcp - then calls proceed.In log file I see that client on some stage sends udp message and server receives it. This fact recovers situation. But its wrong, because udp should not be used.My task is to setup secure tls communication (TLS+SRTP).I tried on eyebeam 1.5 and 3CXphone 6. Situation is the same.

It seems there is an issue with the Contact header.Yate sends the Contact header with local ip/port.The second log shows the ACK to OK comes on UDP (which uses the same port as TCP, 5060).I suspect the failure in the first log is due to the fact the remote client sends the ACK on UDP port 5061.

I do have a separate Listener Configured for TLS with NAT, It Works if I call in via TLS-NAT and the internal Endpoint uses UDP Only..As soon as I use TCP or TLS on the Internal Client I do have bidirectional RTP, but the call gets disconnected after 15 sec.

So question:Optimising th call.answer section is probably on solution.But I do not get the advantage / disadvantage of the contact type set with the transport type or not.

I updated to release 6.0 but it is still the same .Could someone colaborate on this?