Neccessity of ISUP Release Cause Values,Codes and Class

Neccessity of ISUP Release Cause Values,Codes and Class

Abstract: Implementation of peer to peer office Interconnectivities based on TDM is often carried out using the concept of the SS7 protocol layers from MTP1 (physical), MTP2(Data link), MTP3 (Network) and Transport  to application layer (ISUP). This however doesn’t end there as soon as this is achieved and the ISUP route opened for trunks, there follows a lot of release causes as displayed by the realtime trace and identified by the H1/H0 header code REL . This header code when queried further contained the release cause values showing exactly what release type it is may be normal release or abnormal release and where it seemed abnormal then proceed for further troubleshooting.   This article puts together specifically the cause values,codes classes, data analysis and how it helps in evaluating probable call related failures.

Advertisements

One thought on “Neccessity of ISUP Release Cause Values,Codes and Class

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s