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 >>

NW Release

Sanjeenth - 13th July 2017  (04:04 GMT)

Dear All.

Any Idea about what is the cause of Droped Call with this?

MS1
Disconnect

Time : 22:08:03.743
Vendor Header
Length : 22
Log Code (Hex) : 0x713A
HW Timestamp : (46650473.75 ms) 12:57:30.474
1.25 ms fraction : 0.00
CFN : 0
1.25 ms counter : 937097160379
Direction : (0) From network
Message length : 5
Transaction Identifier : 8
Protocol Discriminator : (3) Call control; call related SS messages
Message Type : 37
Cause
Coding standard : (3) Standard defined for the GSM PLMNS
Location : (2) public network serving the local user
cause value : (41) Temporary failure


Message dump (Hex):
83 25 02 E2 A9

Mohamed Riad - 8th August 2016  (12:55 GMT)

Datalink Failure
DL Event: N200_Timeout
SAPI: 0

vivek anand - 24th July 2012  (05:59 GMT)

Call blocked due to no alerting and connecting.plz suggest the cause or reason and how to solve

anh - 30th December 2010  (10:31 GMT)

MS1 call MS2 (same network).
MS1 has:
Channel Request
Immediate Assignment
Setup
Call Proceeding
Assignment Command
Assignment Complete
Alerting (DL)
Call Setup
Disconnect
(Setup time~18.5s)
while MS2 has no Call Attemp (no Channel Request, just Cell Reselection).
In this case, call failed.
Anyone let me know the cause and solution.
Disconnect msg:
Time: 09:27:11.98
Frame number: 372727

MsgCtrlOperation :
Transaction identifier : 8
Protocol discriminator : (3) Call control; call related SS messages
Message type : 37
Cause
Coding standard : (3) Standard defined for the GSM PLMNS
Location : (0) user
cause value : (16) Normal call clearing

sonny - 16th March 2009  (03:38 GMT)

Any Idea what cause Blocked Call with this?

MS1
Disconnect

Time: 10:58:26.95
Transaction identifier : 8
Protocol discriminator : (3) Call control; call related SS messages
Message type : 37
Cause
Coding standard : (3) Standard defined for the GSM PLMNS
Location : (2) public network serving the local user
cause value : (41) Temporary failure


Message dump (Hex):
83 25 02 E2 A9

MS Tick: 903237

MS1
Time: 10:58:26.95

Blocked Call
Block type: No Alerting or Connect
CC Cause:Temporary failure
, call time: 266 ms

ms - 18th September 2008  (13:01 GMT)

Hi all,

Finally, the problem was fixed.

We talked with core administrators, and the problem was a malfunction in a SS7 signaling E1.

When the mobile sent the Setup msg, there was no response from de network, because of lack of signaling frames.

Best Regards,

ms

Ayat - 17th September 2008  (10:05 GMT)

Dear , All

I am responsible to monitor the KPI for each office. During the three last months we launched the CRBT service, and during the monitor processing I notice some value in Call drop rate (%).
We connect to CRBT service center By GMSC (Gateway) BSC.... VMSC,,,,,, GMSC,,, CRBT.
We found High call drop rate in GMSC office, but this value with no sense, because according to our customer this service are ok.


The reason was:


After normal signaling interact, if called number has CRBT service, VMSC send IAM(include called number xxxxxxxxxxxxxxxxx),SAM to CRBT by GMSC,and CRBT return ACM,ANM back to VMSC.

Now you can hear color ring. Before called party answer, you or called party release call , release cause value is "normal, unspecified" and GMSC think it as call drop rate.

Why call release cause ???

Could you help me to simplified this reason

ms - 2nd September 2008  (00:05 GMT)

Pan & Pix,

The destination number is within PSTN.

Pix, the Assignment Complete msg is as follows:
------------------------
MS2
Assignment Complete
Time: 12:21:16.54
Frame number: 2194570
Skip indicator : 0
Protocol discriminator : (6) Radio resources management messages
Message type : 41
RR cause
Value : (0) Normal event
------------------------

There's no Alerting msg in this cases, and this is the main problem (after the Assignment, we receive a Relesease from the Network).

The Disconnect msg from the Networks is as follows:

-----------------------
Transaction identifier : 8
Protocol discriminator : (3) Call control; call related SS messages
Message type : 37
Cause
Coding standard : (3) Standard defined for the GSM PLMNS
Location : (2) public network serving the local user
cause value : (31) Normal, unspecified
-----------------------

Tomorrow we're going to perform a Drive Test, but in this case it'll be complemented with a MSS trace, so I'll keep you posted.

BR.

Pan - 30th August 2008  (05:06 GMT)

and else.. What is the cause value in disconnect message?

Pan - 30th August 2008  (04:33 GMT)

Dear Ms! Perhaps you must to search your Alert on destination side? What kind of call is it? MOC or MMC? Is destination number within PLMN or PSTN? In latter case: Is your PSTN completely digital network or there are many analog exchanges in PSTN? Tell your NSS engineer to analyse the trace record on E-interface between your MSC and PSTN if destination number is located within PSTN.

Other messages

Other messages: [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.