Re: [Sarp-users] Malformed UTF-8 character errors

[Andrew R. <an...@ra...>]

Hmm,

That is a very interesting error. The obvious link between those 4 lines
is that they are dealing with the RTP packet. At no point do we ever try
to interpret the contents of that packet. The closest we ever get to
that is to read the length of it but that would only account for lines
377 and 382. For some reason it looks like Perl is trying to treat this
data as UTF-8 formatted text. I'm guessing this is because of some data
at the beginning of the packet. What codec and client are you using? And
does it go away if you try using a different codec? (I use Speex almost
exclusively).

Regards,

Andrew

On Tue, Sep 02, 2003 at 05:51:09PM -0400, mattf wrote:
> Hello,
> 
> After some trial and error with my firewalls I was able to get sarp running,
> it now connects wonderfully. 
> 
> Redhat 9
> Linksys firewall/gateway (I couldn't get my very strict iptables firewall to
> let and any audio through)
> sarp 3 rc2
> 
> I am having a lot of errors show up with Malformed UTF-8 characters:
> 
> Malformed UTF-8 character (unexpected end of string) at
> /usr/local/sarp/sarp.pl line 377.
> Malformed UTF-8 character (unexpected end of string) at
> /usr/local/sarp/sarp.pl line 379.
> Malformed UTF-8 character (unexpected end of string) at
> /usr/local/sarp/sarp.pl line 382.
> Malformed UTF-8 character (unexpected end of string) at
> /usr/local/sarp/sarp.pl line 384.
> 
> several hundred of these show up per minute.
> 
> Should this worry me or should I just turn the error messages off and forget
> about it?
> 
> Thanks,
> 
> MATT---