Biamp Tesira

Home Forums V-Control General Biamp Tesira

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1234
    Franziskus
    Participant

    Hello Dierk,

    I now do have to control a Biamp Tesira, which is a Audio-Processor like Soundweb and others.
    http://www.biamp.info/tesira-enterprise-level-audio-platform

    Unfourtunatly the connection to the system is not done by a “raw”socket, but by an explicit Telnet-Connection:
    https://support.biamp.com/Tesira/Control/Telnet_session_negotiation_in_Tesira

    So, whenever there will be an Port opend, there has to be some handshakes, then we can send the command.

    To make it easier, it would be handy to have not only a TCP-Connection, but also a channel with a real telnet connection.
    If I connect to the sysrtem with putty, everthing works like I would expect it.

    Beste Regards,
    Franziskus

    #1236
    Dierk
    Participant

    Hi Franziskus,

    I do not understand your problem. To connect to Telnet devices, create a TCP channel and use Port 23.

    If you need to send more then one command – i.e. a login, you can use the NextCommand dropdown box in the driver.

    As an example, take a look at the Image Pro network Driver.

    #1238
    Franziskus
    Participant

    Hi Dierk,

    from the Biamp – Website:


    Tesira implements a Telnet server on port 23. When the request from the control system to open a session is received, the Tesira Telnet server attempts to negotiate the session’s options, following specifications described in the Telnet standard document RFC 854 as well as document RFC 855, Telnet Option Specifications.

    A standard Telnet client would be able to negotiate the session options without problem, but several third-party controllers do not implement a Telnet client by default. Instead, they implement control over TCP/IP using what’s commonly known as a ‘RAW’ connection. If the Control System does not respond to the Telnet session options negotiations, the session will not go ahead. As such, the control system will have to be programmed to negotiate the Telnet options with Tesira’s Telnet server. Many of the available options can be useful during a control session and indeed a programmer may choose to enable some of them, but if the desire is to continue using a ‘RAW’ connection, the simplest way to initiate a control session is for the control system to respond with a rejection to any option negotiation request from the server.

    So, what we normaly do is a RAW – Socket, but this Devie need to have a REAL Telnet session. That means there are some handshakes to do.
    have a look at Tesira-Website

    I found some vb.net Telenet components to write a proxy, but they are around 300,- EURO. Right now I found a C# – Example for free ….

    • This reply was modified 4 years, 3 months ago by Franziskus.
    #1241
    Dierk
    Participant

    Well, you give the answer already:

    If the Control System does not respond to the Telnet session options negotiations, the session will not go ahead. As such, the control system will have to be programmed to negotiate the Telnet options with Tesira’s Telnet server.

    So the only solution to do it in V-Control is to implement it. Thats why I point you to the ImagePro Network driver, because there you can see an aproach how to do this.

    • This reply was modified 4 years, 3 months ago by Dierk Walter.
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.
Scroll to top