<div>Yes, they say that at moment VLC can only send RTP packets with 96 dynamic payload. How can I solve it?<br></div><div>I'm not expert programmer.</div><div><br></div><div><br></div><div><br></div><br><div class="gmail_quote">
2010/2/9 Kristian Kielhofner <span dir="ltr"><<a href="mailto:kristian.kielhofner@gmail.com">kristian.kielhofner@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Tue, Feb 9, 2010 at 3:46 AM, Salvatore Frandina<br>
<div class="im"><<a href="mailto:salvatore.frandina@gmail.com">salvatore.frandina@gmail.com</a>> wrote:<br>
</div><div class="im">> I'm using SIPp not with pcapplay only with modified uac scenario. I have<br>
> adapted the uac.xml scenario for my purposes.<br>
> VLC can't choose the payload type but it selects the first dynamic payload<br>
> type 96. The strange thing is that my application works with Asterisk 1.6<br>
> family but not with Asterisk 1.4. Hence I think that there is a bug in one<br>
> on these version.<br>
> I can't understand why response of Asterisk is different from request by<br>
> SIPp+VLC...<br>
> PS I have attached the scenarios sipp.xml and SIP message between SIPp and<br>
> Asterisk.<br>
><br>
<br>
</div>Salvatore,<br>
<br>
Kevin and Olle have already explained that Asterisk 1.6 has a<br>
different codec negotiation scheme that will (even though it doesn't<br>
need to) attempt to use the same payload type as the far end. Just<br>
because it is different does not mean that 1.4 is broken or invalid.<br>
They've already quoted the relevant RFCs that back up Asterisk in this<br>
case.<br>
<br>
Changing the payload type in your sipp scenario is simple. VLC<br>
starting at 96 is not a problem but if it expects Asterisk to use the<br>
same dynamic payload type it is broken. Have you asked the VLC<br>
developers about this?<br>
<font color="#888888"><br>
--<br>
</font><div><div class="h5">Kristian Kielhofner<br>
<a href="http://www.astlinux.org" target="_blank">http://www.astlinux.org</a><br>
<a href="http://blog.krisk.org" target="_blank">http://blog.krisk.org</a><br>
<a href="http://www.star2star.com" target="_blank">http://www.star2star.com</a><br>
<a href="http://www.submityoursip.com" target="_blank">http://www.submityoursip.com</a><br>
<a href="http://www.voalte.com" target="_blank">http://www.voalte.com</a><br>
<br>
--<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-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>_______________________________________<br>Salvatore Frandina<br>website: <a href="http://frandinas.altervista.org">http://frandinas.altervista.org</a><br>mail: <a href="mailto:salvatore.frandina@gmail.com">salvatore.frandina@gmail.com</a><br>
<br>_______________________________________<br><br>