Free Erlang traffic calculators

The world's first online Erlang traffic calculators

Telecom Traffic Online
  Home | Free calculators | Products | Tech. papers | Forum | About us
Erlang for Excel
A-Z termination using H.323 and SIP
A-Z termination
  • VoIP softswitch

    DUAL Softswitch is a complete Voice over IP switching and billing solution.  Flat monthly rate.

    Web control panels; Least Cost Routing; Excel tariff uploads; SIP and H323 support.

    H323 SIP softswitch >>

  • VoIP calling

    Premium quality termination for wholesale carriers with their own VoIP switch.

    44Direct >>


    Our lowest rates for wholesale carriers with their own VoIP switch.

    44Mobile >>


    Our unique online callshop billing system.

    Bill My Calls >>

Erlang to minute conversion

Cplus - 8th January 2009  (15:21 GMT)

I would like to ask you a question.. I hope there is someone is able to help me thanks. .the question is :
Why do we use Erlang B tables and explain the reason of the 10 times more bandwidth than the average traffic..

thanks in advance...

pix - 28th November 2007  (19:55 GMT)

scor,

of course :) if you activate HR at 60% traffic load on a cell with 30 TS, the actual number of carriers in your cell is :
(60% of 30) + (40% of 30)*2
= 20 + 10*2 = 40 carriers

you can compute your capacity based on this input.

Pix

scor - 28th November 2007  (12:13 GMT)

Mr.Pix,

Is the same calculation holds good when we apply half rate erlang also.

Thanks

pix - 23rd November 2007  (08:38 GMT)

scor,

sdcch traffic is about 10 times smaller than tch traffic (approx.)

unsuccessful calls (mean there was a failure during the call setup) do not use a TCH carrier. The failure occurs while they are on the sdcch channel. therefore they simply cannot be counted in the tch traffic.

if the failure occurs after the callsetup, then it is called a call drop. A call which is dropped occupies a tch carrier for a while, therefore it is counted in the tch erlang.

scor - 23rd November 2007  (07:11 GMT)

Hello Mr.Pix,

IM into OMC Side.

What is the ratio between the TCH Erlangs & SDCCH Erlangs . Ideally the SDCCH Erlangs should be on the higher side. right

And the TCH Erlangs does capture the missed calls

Thanks

Arun - 23rd November 2007  (05:32 GMT)

Dear PIX,

Thx for clarifying the doubt.

regards
Arun

pix - 22nd November 2007  (21:53 GMT)

erlang is the amount of traffic really carried ! does an unsuccessful call put traffic on a carrier ?
- yes, on a SDCCH --> therefore unsuccesfull call increases the amount of SDCCH erlangs.

- no, not on TCH --> therefore the TCH erlangs are not impacted by unsuccesful calls.

Arun - 22nd November 2007  (12:03 GMT)

Dear Pix,

Does that one hour include the unsuccessful calls also or is the erlang calculated only for successful calls.

regds
Arun

pix - 22nd November 2007  (09:06 GMT)

the erlang is the cumulated time of traffic carried in the channels of the observed system.

1 erlang = 60 minutes
2 erlang = 120 minutes
3 erlangs = 180 minutes
4 erlangs = 240 minutes
40 erlangs = 2,400 minutes
400 erlangs= 24,000 minutes

and so on... there is no formula.

you measure 3 erlangs between 9am and 10am, it meands that there were 180 minutes of usage of your system at that hour.

latheef - 22nd November 2007  (05:11 GMT)

thanks pix...

any specific formula to do this Erlnag to minute calculation.

If the hourly traffic has been read are you saying the traffice carrried on that particular is an accumulated figue?

Thanks

Other messages

Other messages: [<<Previous 10] | [Next 10 >>]

Post a reply to this article

Name Enter your name.
Message Enter your message.
Email Optional -  If you enter your email address in this box, then you will automatically be notified if anyone replies to your message.  Your email address will only be published if you pay to post this message.
Verification
Please confirm you are human.
Press the button to post your message.
Home | Free online calculators | Products | Technical papers | Forum | Contact us | About us

Last modified: 17 May 2017

Copyright 2017. All rights reserved.