[pjsip] Fwd: Video media channel update

[P.Muge Ersoy]

There is also one thing i wonder about..

I can successfully create two sessions and streams .. This is what  after
sdp negotiation

v=0
o=- 3432391052 3432391053 IN IP4 192.168.0.220
s=pjmedia
c=IN IP4 192.168.0.220
t=0 0
a=X-nat:0
m=audio 4000 RTP/AVP 3
a=rtpmap:3 GSM/8000
m=video 4002 RTP/AVP 34
a=rtpmap:34 H263/90000
a=sendrecv

But when the stream connected i guess it sets both audio and video port to "
4000 " I am suspected from below code;

if (pjsua_var.ua_cfg.cb.on_stream_created) {
        pjsua_var.ua_cfg.cb.on_stream_created(call_id, call->session,
                          0, &media_port);
    }

I thought pjsip will automatically set to video and audio port..

How can i change it ?

Any comment

Regards
Muge

---------- Forwarded message ----------
From: P.Muge Ersoy <muge.ersoy at gmail.com>
Date: Tue, Oct 7, 2008 at 3:33 PM
Subject: Video media channel update
To: pjsip list <pjsip at lists.pjsip.org>


Hi;

I am still struggling with adding h263 codec..
I have a problem at the below code ;

status = pjmedia_stream_create(endpt, session->pool,
                       &session->stream_info[i],
                      (transports?transports[i]:NULL),
                       session,
                       &session->stream[i]);
    if (status == PJ_SUCCESS){
         status = pjmedia_stream_start(session->stream[i]);
    }

As far as i examine the code i need to create two different rtp stream for
both audio and video.. I check transports[1] (which is for the video stream)
and it was null .. So i set it to transports[0] for both streams .. but than
i had a problem with   PJ_ASSERT_RETURN(!udp->attached, PJ_EINVALIDOP);

Do you advice to create two calls  as if in the pjsua_media_channel_update
function or handling everything inside the somewhere else :) not sure
where..

Thanks advance
muge
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20081007/9d1efd86/attachment-0001.html>