< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
That is not expected. I have no idea why you would be seeing this. If you can post a test program that shows this behaviour, we can probably help.For your reference the resip/stack/test/testSdp unit tests contain some good sample code for using the SdpContent class. Also, its a good starting point for a little test program that could be created to show the behaviour you describe.Cheers,ScottOn Wed, Dec 7, 2016 at 1:38 PM, Francesco Lamonica <alienpenguin@xxxxxxxxx> wrote:______________________________Hi all,i receive with a simple resiprocate app the following sdp in the answer:---------> ANSWERED SDP <-----------
v=0
o=root 735036303 735036303 IN IP4 192.168.23.107
s=KalliopePBX/4.3.1
c=IN IP4 192.168.23.107
t=0 0
m=audio 15732 RTP/AVP 8 0 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=maxptime:150
a=sendrecv
Then if i call
SdpContents::Session::MediumC
ontainer answeredMediaVec = answeredSdp.session().media();
qDebug() << "There are # of answered media: " << answeredMediaVec.size();i do get the output: There are # of answered media: 2and if i iterate over answeredMediaVec like this:for (itAnsMedia = answeredMediaVec.begin(); itAnsMedia != answeredMediaVec.end(); ++itAnsMedia) {qDebug() << itAnsMedia->name().c_str() << " -- "<< itAnsMedia->protocol().c_str() << " -- "<< itAnsMedia->port() << " -- " << sessionConnection; //FIXME - this should / could be overridden by m= connectionthe output is:audio -- RTP/AVP -- 15732 -- "192.168.23.107"
audio -- RTP/AVP -- 15732 -- "192.168.23.107"
Is this the expected behaviour? if so, can you explain why? i would expect to see just one media session, provided the SDP that was received in the onAnswer() callback.
Thanks everyone for any hints :)_________________
resiprocate-users mailing list
resiprocate-users@resiprocate.org
List Archive: http://list.resiprocate.org/archive/resiprocate-users/