Re: WMContentBitrate - not working on distribution server



oops sorry, forgot some important stuff :)

Im running WM9.0 on W2k3 Enterprise servers (3 of them).

Limit at 60000 on individual publishing points, umm, where do you do that?
ive tryed limiting the publishing point on the "limit the bw per stream per
player" to less than 64Kb but it doesnt work as i wanted to. The server will
"talk" with the client before checking the limit, so if the client has more
than 64Kb (who doesnt :P) the server offers the 64Kb stream, then it checks
the limits and cause he cant go past the limit ive put in it just doesnt give
the stream, when he should offer the 32Kb ;)

I have (atm) 201 publishing points on each server. All of them stream at
32Kb cept one that has 32Kb/64Kb on MBR (testing to upgrade all the rest
later on). Im getting more than 2000 users listening to it, over the internet
(and the world :D), and i have 100mbits on my disposal. At some hours i reach
85mbits-90mbits with large portion of the trafic being from the 64Kb stream.

What i wanted was to limit the publishing point to 32Kb sometimes, manually,
using the url modifiers but its not working :(

On an advanced stage i would like to control the negotiation, if its even
possible :)

What i mean by controling the negotiation that the client has with the
server is something along the lines of beetween peek hours i would only
supply the 32Kb version, allowing more listeners, other than that i would
give the 64Kb and 32Kb version.

Sorry if the english is a little messy but english is not my primary
language ;)
Thanks.

"Neil Smith [MVP Digital Media]" wrote:

On Tue, 6 Jun 2006 09:40:02 -0700, Hugo Picão
<HugoPico@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi there,

ive read in Microsoft Documents that WMContentBitrate modifier can be aplied
to distribution servers.

I have a MBR publishing point that has 32Kb and 64Kb so if i would stick in
one of my distribution servers the source -
rstp://myserver.com/publishingpoint?WMContentBitrate=60000 - anyone who would
connect to it would get the 32Kb, right?

well it aint working, those modifiers work on the player but not on
distribution server or... im doing something wrong :)

any ideias?


You missed off the version of WMS you're running, and on which
platform. My impression was this will work on WMS running on WS2003
though I suppose it could depend on the version of WS installed.

Are you aware you can set the limit at 60000 on individual publishing
points, for the distribution servers ? It's a reasonable workaround if
you can't figure out what's up.

btw any way to control the negotiation beetween the server and the player
with some kinda of plugin? might not the the right place to ask this but
seeing im already posting.

What sort of negotiation and what sort of "control" are you looking
for ? I'm afraid this one is hopelessly wooly ;-))

Cheers - Neil
------------------------------------------------
Digital Media MVP : 2004-2006
http://mvp.support.microsoft.com/mvpfaqs

.



Relevant Pages

  • Broadcast publishing point stops
    ... Broadcast publishing points stop and do not restart if the ... that stream gives an error message "Windows Media Player ... of our servers to go down. ...
    (microsoft.public.windowsmedia.server)
  • RE: FrontPage Publishing Speed
    ... FrontPage doesn't limit transfer speed. ... You're also correct in that the servers you are publishing to have no ...
    (microsoft.public.frontpage.client)
  • Re: [OT] Google Page Rank mystery
    ... >> If they're the same site, then why are you publishing it at two different ... > Google to figure that out. ... Different websites often exist at the same IP ... > ...I could suppose I could have posted to a 'servers' group. ...
    (comp.infosystems.www.authoring.html)
  • RE: Load Balancing Live Streams - Remote publishing points, etc.
    ... When you have distribution servers (edge servers) source from an original ... Publishing point Property tab, ...
    (microsoft.public.windowsmedia.server)
  • Looking for an alternative to org library....
    ... library for many offices on many servers. ... So, publishing forms to this ... library is causing users from other offices having to log on through ... they just get the generic message form. ...
    (microsoft.public.outlook)