• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

Tieline codec settings

It's the IP type and no internet on the line at all. It's just point-to-point. I'll give some settings a try soon. The IT guy that actually is their engineering guy is coming back this week from vacation. When he catches up we'll go play around with settings, etc. He's got the keys :) .
 
OK, then you won't be able to use all 512 kbps for audio since there will be packet overhead.

So you'll probably end up using 384 kbps for the codec bit rate. If the codec permits adjusting the packet size you will have some control of the delay vs bandwidth tradeoff.

If you want to run *anything* else over the link you need a managed switch and proper configuration.

As soon as you can put two PC's on the link and run ping -t constant pings and look to see what the results over time.

Even better download the colasoft ping tool (free) and use that to test the link. These results will help you set an appropriate buffer setting (use 1.5 times the longest round trip ping and you should be robust.
 
RolfTaylor said:
OK, then you won't be able to use all 512 kbps for audio since there will be packet overhead.

So you'll probably end up using 384 kbps for the codec bit rate. If the codec permits adjusting the packet size you will have some control of the delay vs bandwidth tradeoff.

If you want to run *anything* else over the link you need a managed switch and proper configuration.

As soon as you can put two PC's on the link and run ping -t constant pings and look to see what the results over time.

Even better download the colasoft ping tool (free) and use that to test the link. These results will help you set an appropriate buffer setting (use 1.5 times the longest round trip ping and you should be robust.
Click to expand...

Ping Tool is a great resource...
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom