after lots of testing 1.3b5 I can say nearly everything works fine ... if used properly. Trouble starts, when one tries to use the SIP proxy as a local registrar. This is in general not recommended (e.g. calls between local endpoints won't work). I do have however one special case where it makes sense for me: I register a video endpoint to something like
300@fqdn.com as follows: host.fqdn.com is the DNS entry for m0n0wall's WAN IP Address.
SIP username:
300@host.fqdn.comSIP Registration: direct
SIP Proxy: Enabled
Proxy Hostname: 192.168.1.1 (m0n0wall lan port)
SIP Registrar: enabled
Registrar hostname: 192.168.1.1
Not using the proxy entry will result in blocked SIP traffic.
There is however an issue pending in 1.3b5: siproxd 0.6.0 dejitter function messes up H.264 RTP streams. Recompiling siproxd without dejitter fixes this issue. Submitted the info to the siproxd mailing list. Basically blocks of 5 RTP packets are sent out with reverse sequence numbers.