How to make RTC communicate media (RTP and RTCP) over TCP?

[pandre]

Hi everyone

Is there any way to make RTC communicate media (RTP and RTCP) over
TCP, instead of UDP?

Thanks a lot
pandre

[Oscar Newkerk{MSFT]]

The only way to fo this is to negotiate the SDP your self
(CreateSessionwithSDP) and to handle the media your self as well.

--

Oscar Newkerk
Unified Communications Group
---------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

"pandre" <pedro....@gmail.com> wrote in message
news:1179502346.8...@o5g2000hsb.googlegroups.com...

[pandre]

On May 18, 7:56 pm, "Oscar Newkerk{MSFT]"

<oscarn@REMOVE_CAPS.microsoft.com> wrote:
> The only way to fo this is to negotiate the SDP your self
> (CreateSessionwithSDP) and to handle the media your self as well.

Can you provide a small code sample? I'm not understanding what
CreateSessionwithSDP is.
Also, what do you mean by "handle the media for yourself"?

Best Regards
pandre

[Oscar Newkerk{MSFT]]

There is a sample in the RTC 1.3 SDK that shows how to use a custom SDP. If
you install the SDK to the default directory it will be in: C:\Program
Files\RTC Client API v1.3 SDK\SDK\Samples\CustomSDP

The issue with the media is that the built in media capabilities of the RTC
API do not give you any control of the protocol/ports that are used. In the
default case, your program creates a session with automatic SDP negotiation
and then adds a media stream to the session using the IRTCSession::AddStream
interface which takes a media type specfier as one of the arguments..
However, as I said, this does not allow you to specify the protocol or ports
to be used. This is all negotiated "under the covers" by the RTC code using
SDPs to negotiate with the other endpoint.
If you want to control this, then you need to create an application session
and negotiate your own SDP to specify this information. Your app will also
have to handle creating the media streams and handling the data on both
ends.

Some of this is described in the RTC API help file under "Globally Disabling
the Media Stack"

--

Oscar Newkerk
Unified Communications Group
---------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

"pandre" <pedro....@gmail.com> wrote in message

news:1179738819.7...@x18g2000prd.googlegroups.com...

[pandre]

On May 21, 4:51 pm, "Oscar Newkerk{MSFT]"

<oscarn@REMOVE_CAPS.microsoft.com> wrote:
> There is a sample in the RTC 1.3 SDK that shows how to use a custom SDP. If
> you install the SDK to the default directory it will be in: C:\Program
> Files\RTC Client API v1.3 SDK\SDK\Samples\CustomSDP
>
> The issue with the media is that the built in media capabilities of the RTC
> API do not give you any control of the protocol/ports that are used. In the
> default case, your program creates a session with automatic SDP negotiation
> and then adds a media stream to the session using the IRTCSession::AddStream
> interface which takes a media type specfier as one of the arguments..
> However, as I said, this does not allow you to specify the protocol or ports
> to be used. This is all negotiated "under the covers" by the RTC code using
> SDPs to negotiate with the other endpoint.

What about if I change the SDP between the clients? I think I'm able
to do that :)
If that will solve the problem, what changes do I need to make in SDP
in order to have TCP communication?
Otherwise, the only solution is to Globally Disable the Media Stack?

Best Regards
pandre

[sun...@sunsys.net]

Can't you just set the transport type using the protocol="TCP" field
in the Profile XML string?

[Oscar Newkerk{MSFT]]

You can't change the SDP unless you are the one creating and controlling it
by using the IRTCClient::CreateSessionWithDescription() interface.

You use the contents of the SDP to negotiate the ports, protocols, and
codecs that each side has available and wants to use for media. Once you
have done that, then your program is responsible for creating the socket
connection and sending the encoded media to the other endpoint and receiving
and decoding the media from the other endpoint.

--

Oscar Newkerk
Unified Communications Group
---------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

"pandre" <pedro....@gmail.com> wrote in message

news:1179766936....@a26g2000pre.googlegroups.com...

[hasinigunasinghe]

Hi,

I am developing a voip phone application which handles both audio and video.

I have built a graph using directshow filters to handle the media. I am trying to do spd negociation with RTC Client API methods and once the session is negotiated I specified the negociated media ports to the graph to receive media.

But the application crashes when the ports mentioned in SDP negotiation with the CreateSessionWithDescription method, are used again to build the graph.
So if you have any idea on how to integrate our media handling part with RTC Client, please do reply. I am in a trouble without being able to integrate those.
Thank you in advance.

regards,
Hasini.

[hasinigunasinghe]

[sharad shukla]

Hi Guys,

I have seen your block on net for softphone.

I have also develop softphone using MS RTC Client API 1.3.
It's working fine for direct number i.e any mobile or landline number.

But when we are dailing at that number which has required extension number.
i.e. system generated voice please dial extension number.
How we can handle this and make call on that extension number.

If you have any solution please help me as soon as possible.

Thanks

Regards:

Sharad
Email:shar...@gmail.com

url:http://www.ureader.com/msg/1480825.aspx