<div dir="ltr">Hi, Sergio,<br><br>If there is no capability mapping, how does asterisk decide what capabilities to put in the SDP body of the SIP Invite message?<br><br><br>When I originate a call from a Nokia N73 to a SIP client, the Invite message includes and SDP section for video:<br>
<pre>m=video 10070 RTP/AVP 34 103<br>a=rtpmap:103 h263-1998/90000<br>a=sendrecv<br></pre><br>When I originate a call from a Nokia N95 the SDP is different and also includes the h263/9000 capability:<br><pre>m=video 10120 RTP/AVP 34 103<br>
a=rtpmap:34 H263/90000<br>a=rtpmap:103 h263-1998/90000<br>a=sendrecv<br></pre><br><br><br>Thanks,<br>Dan<br><br><div class="gmail_quote">On Tue, Sep 9, 2008 at 11:54 AM, Sergio Garcia Murillo <span dir="ltr"><<a href="mailto:sergio.garcia@fontventa.com">sergio.garcia@fontventa.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Hi Dan,<br>
<br>
There is no capability negotiation, or mapping between SIP and the
h245, I send fixed ones For H263 and AMR:<br>
<br>
<br>
[0]={<br>
capabilityTableEntryNumber = 1<br>
capability = receiveAndTransmitVideoCapability
h263VideoCapability {<br>
qcifMPI = 2<br>
maxBitRate = 520<br>
unrestrictedVector = FALSE<br>
arithmeticCoding = FALSE<br>
advancedPrediction = FALSE<br>
pbFrames = FALSE<br>
temporalSpatialTradeOffCapability = FALSE<br>
errorCompensation = FALSE<br>
}<br>
}<br>
[1]={<br>
capabilityTableEntryNumber = 2<br>
capability = receiveAndTransmitAudioCapability
genericAudioCapability {<br>
capabilityIdentifier = standard 0.0.8.245.1.1.1<br>
maxBitRate = 122<br>
collapsing = 1 entries {<br>
[0]={<br>
parameterIdentifier = standard 0<br>
parameterValue = unsignedMin 1<br>
}<br>
}<br>
}<br>
}<br>
.<br>
<br>
Best regards<br>
Sergio<br>
<br>
Dan Julius escribió:
<blockquote type="cite"><div><div></div><div class="Wj3C7c">
<div dir="ltr">Hi, <br>
<br>
I'm experiencing some issues when using Asterisk as a gateway between
3G and SIP clients.<br>
I'm trying to complete a call using h263p as the video codec on the sip
client in order to avoid video transcoding.<br>
For audio I'm using AMR on the 3G side and g711 on the SIP side since
most SIP clients don't support AMR out of the box.<br>
<br>
For some phones this works without a problem while other phones don't
seem to show video depending on the SIP client.<br>
For example: N73 works with X-Lite, but not with OpenPhone. N95 works
with both.<br>
I've traced this down to an issue with the capability exchange,
specifically how capabilities are translated from h245 to SIP.<br>
<br>
Can someone point to which part of the code, Asterisk or libh324M does
the mapping between capabilities?<br>
After reviewing some relevant RFCs and specs, it is not clear to me
what the 1:1 mapping should be - is there any relevant documentation?<br>
<br>
Thanks,<br>
Dan<br>
<br>
<br>
</div>
</div></div><pre><hr size="4" width="90%">
_______________________________________________
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a>--
asterisk-video mailing list
To UNSUBSCRIBE or update options visit:
<a href="http://lists.digium.com/mailman/listinfo/asterisk-video" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-video</a></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-video mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-video" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-video</a><br></blockquote></div><br></div>