Procedure 52 calculating known conference traffic, Procedure 52, Calculating known conference traffic – Nortel Networks NN43001-314 User Manual

Page 380

Advertising
background image

380

Appendix B Branch Office engineering example

LAN/WAN kbps = TCON (erlangs) x 37 kbps

—End—

Procedure 52

Calculating known conference traffic

Step

Action

When a Branch Office is known or expected to make a significant number of
conference calls, traffic statistics should be collected or estimated. Use the
statistics to calculate LAN/WAN bandwidth requirements.

1

Calculate conference traffic:

Cc = conference calls/busy hour (a 6- or 3-way conference call is
counted as 6 or 3 calls, respectively)

Ht = Average talk time (holding time) of conference in seconds (if you
have no data, use 900 seconds as a default)

TCON = (3 x # 3-way conference calls + 6 x # 6-way conference
calls + ...) x Ht/100 CCS = Total Cc x Ht/3600 erlangs

2

Calculate LAN/WAN bandwidth:

For a G.729A/30 ms codec:

LAN/WAN kbps = TCON (erlangs) x 9 kbps

For a G.711/30 ms codec:

LAN/WAN kbps = TCON (erlangs) x 37 kbps

Use other bandwidth data from

Table 44 "LAN/WAN bandwidth for

one channel (one Erlang)" (page 377)

if the codec and payload differ

from those listed above.

—End—

With local conference Integrated Conference Bridge card

When a Branch Office conference is provided locally, there is no need to
route conference traffic to the main office for service. A local conference
generates no LAN/WAN traffic and does not require a LAN/WAN bandwidth
calculation.

Nortel Communication Server 1000

Branch Office Installation and Commissioning

NN43001-314

01.02

Standard

Release 5.0

20 June 2007

Copyright © 2007, Nortel Networks

.

Advertising