- SIP over TCP/TLS arriving on the ports intended for SIP over WebSocket is correctly rejected
- SIP over TCP/TLS arriving on the port intended for MSRP is correctly rejected
In examples/websocket.cfg with default settings:
- SIP over UDP is supported on port 5060
- SIP over TCP is supported on port 5060
- SIP over TLS is supported on port 5061
-
SIP over WS is supported on port 80
- SIP over WSS is supported on port 443
- MSRP is supported over TLS on port 9000
- traffic of the wrong type/transport arriving on the wrong ports is correctly rejected
I believe that the check you have described, and the related ones in onreply_route, event_route[xhttp:request], and event_route[msrp:frame-in], are not too tough do exactly what they are meant to. Whether the checks are too tough for your exact use case depends on what that is.
Regards,
Peter