Some services refuse to establish an RTCP connection because MAJESTIC's response to SETUP does not fully implement rfc2326

[USRView]

Some services refuse to establish an RTCP connection because MAJESTIC's response to SETUP does not fully implement rfc2326 (12.39 Transport), namely the response to SETUP.
Majestic responds
Transport: RTP/AVP/UDP; unicast; client_port=....-....
but the services are waiting to be executed
Transport: RTP/AVP/UDP; unicast; client_port=....-....; server_port=...-...
The absence of server_port=...-... in the response it does not allow to establish a connection.
So the services reject the session establishment and send Majestic session - TEAR DOWN.
Can You to fix it?n

[widgetii]

Majestic is based on smolrtsp RTSP library which is opensourced, so the right way to fix all RTSP issues is to add new features to the library