I would like SIP/TCP support to be available on AASIP. The RFC requires both UDP and TCP support, and it would probably have saved a lot of pain this week with non-delivery of fragmented UDP packets stopping me making outgoing calls.
Sorry for delay, we're currently developing a new SIP platform based on FireBrick.
Currently TCP is not supported. However, we are compatible with RFC compliant devices; in that devices should fall back to UDP if TCP is unavailable.
It may well be that we do support TCP SIP on the FireBrick.
Idea status:
completed
Comments
jzaw, 01.07.2014, 14:46
using ipv6 only I'm encountering LARGE SIP UDP pkts
freeswitch tries to switch to using TCP but of course that fails since revtel doesnt support that and doesnt do UDP pkt fragmentation
nta.c:8370 outgoing_try_tcp_instead() nta: INVITE (61776863) too large for UDP, trying TCP
.
.
nta.c:8494 outgoing_print_tport_error() nta: INVITE (61776863): retrying with UDP after Connection refused (111) with tcp/[2001:8b0:0:30::5060:1]:5060
.
.