Free Erlang traffic calculators

The world's first online Erlang traffic calculators

Telecom Traffic Online
  Home | Free calculators | Products | Tech. papers | Forum | About us
A-Z termination - click here
A-Z termination - CLICK HERE
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 >>

CAMEL roaming

  • Erlang for Excel

    An Add-In for Microsoft Excel that lets you use Erlang B and C functions in your own Excel spreadsheets.

    The ultimate in Erlang traffic modelling flexibility and data sharing.

  • Erlang Calculators

    An easy to use and fast Windows product offering Erlang B, Extended Erlang B, Erlang C and Call Minutes calculators.

    Four products in one, plus Erlang for Excel free.

  • VoIP Calculator

    Our entry level VoIP calculator allowing you to easily calculate your Voice over IP bandwidth requirements.

    Supports multiple codecs and packet intervals and RTP header compression.

Wallis Dudhnath - 27th September 2016  (10:31 GMT)

Hi Eleni,

In the past I have used a Protocol Analyser to check the contents of INAP / CAP (CAMEL) methods(). You can look at Layer 3 to see the parameters that are being sent by the gsmSSF entity. Your vendor's gsmSSF/MSC should support traces that can be activated via MML.

VBR/ Wallis Dudhnath

ELENi - 26th September 2016  (08:29 GMT)

HOW CAN I CHECK THAT OUR VLR send TO RP's SCP the Initial DP with service key xxxxx


Wallis Dudhnath - 4th July 2015  (19:47 GMT)

Due to the close interaction with the MSC and VLR most vendors will have the MSC/VLR configuration.
Having a separation via ss7 links will be a real bottleneck.

CAMEL (e.g. Phase) is a well defined Standard that brings on board MAP V3 and CAP V2.

Dragan - 16th April 2013  (13:01 GMT)

The VLR and MSC have the same address!
I did not see one operator so far to have these addresses separate

Pan - 12th February 2009  (07:28 GMT) may see more about Camel procedures in 23.078.

Pan - 12th February 2009  (07:21 GMT)

Dear, RASH!

1. Your SCP will send response on Initial_DP from SSP (i.e. MSC). This response is routed by using Global Tytle in SCCP_Called Party Addres.
2. SCCP_Called party address of response is derived from SCCP_Calling Party Addres of Initial DP.

RASH - 11th February 2009  (14:30 GMT)


we didn't found MSC address, our problem as following;

1. roaming partner send initiaDP to our IN.
2.our SCP will reply to their MSC, with continue message.
3.we configure our SCP to reply to VLR. (by using VLR number in initiDP message) is this right????

My question is;

1.our SCP will reply to their MSC, with continue message. is this right??
2. if yes from where our SCP can know the MSC number.
3. if no, our SCP will reply to VLR. then VLR will forward this message?????

in brief,,what is the exact scenario , and how we must configure our SCPs.


Pan - 10th February 2009  (04:14 GMT)

Dear, RASH!
There is only VLR-address (not MSC-address) in LocationInformation parameter. In which information element of Initial DP for MO call you found out MSC-address?

RASH - 9th February 2009  (13:29 GMT)

CAMEL roaming
I want to know what is the standred in this case in 3GPP;

When receiving an InitialDP message with the Event Type Bcsm “collectedInfo” (TDP-2), the SCP differentiates an InitialDP for an MO call from an InitialDP for an MF call by means of the following criteria:

-The InitialDP for an MO call must include the parameter Called Party BCD Number.

-When recognizing an InitialDP message for an MO call, the SCP uses the LocationInformation/vlr-number or MSC number parameter in the InitialDP for identifying the calling subscriber’s serving network and reply??

in case the vlr number equal to MSC number , we don’t face any problem, but in case the vlr number is not equal MSC number we face a problem that we don’t reply to the MSC.

we must care about vlr number or MSC number. do you have any idea about this or how we can fix this problem.

Post a reply to this article

Important notice

This forum is rapidly turning into a document exchange medium.  It was intended as an area for open discussion.  Please restrict your postings to open discussions.  Requests for documents are now being removed from this forum.

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 code
Verification code Enter this verification code into the box.
Press the button to post your message.
Home | Free online calculators | Products | Technical papers | Forum | Contact us | About us

Last modified: 26 November 2014

Copyright © 2014. All rights reserved.