[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: Re: Details of next xPLRioNet Release - for comment
- Subject: RE: Re: Details of next xPLRioNet Release - for
comment
- From: "Tony Tofts" <tony@xxxxxxxxxx>
- Date: Sat, 31 Jul 2004 05:00:30 +0100
> this could break caller id announce. caller id here comes
> over on the 2nd ring. by the time the announce is made (10
> seconds?) that could be the 4th ring & the caller has hung up
> or gone to voicemail...
Exactly, but there's no way around it with injection into the stream?
On the Rio side there are possibilities to overcome this, since I can play
with the source code.
On the exstreamer side there is the possibility to 'flush' the play buffer
and loose some music - not a big issue as it can be assumed the tts
overwrote the music.
On the slim side, maybe the same as the exstreamer.
I'll code 'as is' for now, and then look at improving things.
I'm really tempted on the rio side to totally rewrite the client streaming,
so instead of rio requesting it just gets pushed to (tcp) by the server
like
the exstreamer (tcp) and slim (udp).
Regards
Tony
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|