Author Topic: CCM and Stream Manager and TSERVER  (Read 3075 times)

Timmy2000

  • Guest
CCM and Stream Manager and TSERVER
« on: January 01, 1970, 12:00:00 AM »
Can someone please tell me how SM and TSERVER communicate when used with CCM?

TIMMY!

Offline MJ

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: CCM and Stream Manager and TSERVER
« Reply #1 on: January 13, 2010, 07:06:23 PM »
You need to create a voice over ip service DN under the CCM DNs.
This DN needs a T-Server section in the annex tab with a key of contact and value of the <IP:Port> of where your SM is installed and the port which you have configured in your SM application object in the options tab: contact section: sip-port.
In addition you need to create a connection from your SM object to your CCM T-Server. Not sure if you need to have a connection between SipServer and CCM T-Server for this to fully work, I have it in there for an ISCC transfer to CMM.

I understand this isn't exactly the answer to your question but I wasn't sure if you wanted the theory behind it (other than CCM using the VOIP Service DN) I'm not 100% clear either) or the application.

Marked as best answer by on November 30, 2024, 03:36:19 AM

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: CCM and Stream Manager and TSERVER
« Reply #2 on: January 14, 2010, 09:17:21 PM »
  • Undo Best Answer
  • Hi Timmy,

    TServer for Cisco communicates with Stream Manager using proprietary Genesys protocol. After start-up, Stream Manager connects to port specified in TServer's option "sm-port". Please note that Stream Manager connects to TServer configured on its Connection tab and that it can connect to single TServer only.

    In case of URS asking TServer to play an announcement etc. the flow is:
    - URS sends request to TServer
    - TServer will send request to Stream Manager
    - Stream Manager will return IP address and port that RTP stream should be connect to
    - TServer sends request to CCM to connect RTP stream to address/port provided by SM

    Information in mjarocki's post is related to situation when Stream Manager is used with SIP Server.

    R.