Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Forums › New Zealand Broadband › VoIP tagging (UFF + Cisco + Bitstream 2)
MichaelNZ

1594 posts

Uber Geek
+1 received by user: 485

Trusted
Net Trust Ltd

#150776 2-Aug-2014 19:14
Send private message

Reading through the service description of an Ultrafast 100/50 Bistream 2 service I have ordered for installation - I have noticed it has a minimum of 2.5Mbps CIR accessible by QOS tagging.

I'll be using a Cisco router.

What has been others experiences and results with QOS tagging on Ultrafast UFB services?

Also - can someone enlighten me on the difference between Bitstream 2 and Bitstream 2 Ultra?




WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET

Create new topic

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

MichaelNZ

1594 posts

Uber Geek
+1 received by user: 485

Trusted
Net Trust Ltd

  #1101966 4-Aug-2014 18:37
Send private message

LennonNZ: To use the QOS Correctly you really need the connection tagged high Priority traffic both ways (Ie ISP to tag the traffic towards you and you to tag the traffic towards the ISP).

But first you have to decide WHAT you are going to tag (and remember you only have 2.5M (or whatever plan you are are) of traffic) . Normally you would tag VOIP Traffic for example as this is usually what its used for. Either Based on Destination of the VOIP Server and/or based on DSCP Values what your PABX/VOIP Phones sets and translating them to 802.1p value on the Bitstream 2 plans. Then the ISP has to do the same/similar on their end (Most ISP's won't give you a choice of this and might set this if its coming from their OWN VOIP Product)

This tagging would give the tagged traffic higher priority on the chorus network and cause less jitter and normal untagged traffic won't kill your VOIP traffic.

After it gets to the ISP then it could be a different story. They might convert the 802.1p Value to a DSCP Value thru their network (to their VOIP Product). After it leaves the ISPs then these markings won't make any difference.





Thanks for this information.

How is this set - Do I use "set cos" or another command?




WFH Linux Systems and Networks Engineer in the Internet industry | Specialising in Mikrotik | APNIC member | Open to job offers | ZL2NET

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Updates »

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.








RSS feeds
Main feed
Forums feed
Copyright
©2002-2026 Geekzone®
Site features
Geekzone BI dashboard
Geekzone Badges
Geekzone Status Page

 

Site Information
Subscribe to Geekzone
Privacy Statement
Forum Usage Guidelines (FUG)
Advertising
Trademark and copyright