[Problem] establishing client server connection unirmcp
127 views
Skip to first unread message
matteo peperoni
Nov 8, 2016, 11:27:08 AM11/8/16
to UniMRCP
Hi,
i'm having problem to establishing a connection from an external client (HP OCMP) and an unimrcp server using ONLY a RTSP protocol and the RSTP Agent.
I get the follow message in the server logs:
2016-11-08 13:56:45:593801 [DEBUG] Wait for Messages [RTSP-Agent-1]
2016-11-08 13:56:45:595545 [DEBUG] Process Signalled Descriptor [RTSP-Agent-1]
2016-11-08 13:56:45:595576 [INFO] Receive RTSP Data (IP SERVER):(PORT)<-> (IP CLIENT):(PORT) [56 bytes]
OPTIONS rtsp://IP_SERVER:PORT RTSP/1.0
CSeq: 16
2016-11-08 13:56:45:595596 [WARN] Missing RTSP Session-ID
2016-11-08 13:56:45:595608 [INFO] Send RTSP Data (IP SERVER):(PORT) <-> (IP CLIENT):(PORT) [38 bytes]
RTSP/1.0 400 Bad Request
CSeq: 16
2016-11-08 13:56:45:595633 [WARN] Failed to Create RTSP Session
2016-11-08 13:56:45:595645 [INFO] Send RTSP Data (IP SERVER):(PORT) <-> (IP CLIENT):(PORT) [41 bytes]
RTSP/1.0 406 Not Acceptable
CSeq: 16
Please can someone help me on this? Thanks for your support.
matteo peperoni
Nov 9, 2016, 10:18:38 AM11/9/16
to UniMRCP
Hi, i noticed that the client sends to the unimrcp server the OPTIONS request but it looks like the server doesn't respond with the list of all the accepted requests Have i need to create e plugin to set correctly the OPTIONS response or is it a problem of a wrong server configuration?
If i need to create a plugin how can i do it?
Arsen Chaloyan
Nov 9, 2016, 10:29:01 PM11/9/16
to UniMRCP
You seem to be on the right track. Please note that the RTSP stack does not currently support the OPTIONS method, since there is no much use of this method in the MRCP scope.
I believe the RTSP OPTIONS is used as a basic keep-alive mechanism by your client. Anyway, if you can implement the missing functionality in the stack, I'd be glad to apply your changes to the upstream version. You may start off from the definition of the currently supported methods:
I believe the RTSP OPTIONS is used as a basic keep-alive mechanism by your client. Anyway, if you can implement the missing functionality in the stack, I'd be glad to apply your changes to the upstream version. You may start off from the definition of the currently supported methods:
--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Reply all
Reply to author
Forward
0 new messages