Powered by Blogger.

Default SIP-to-SS7 ISUP Cause Codes

Hello Guys, today i am going to share a very informative chart with you. Most of you, who are in VoIP or Telecommunications field, they would know how helpful this chart is. Most of the time, we VoIP engineers need this chart to dig different sort of problem in VoIP/ Telecom Network. This chart is the property of http://www.dialogic.com

Please feel free to let me know your questions and confusions.

Default SIP-to-SS7 ISUP Cause Codes


ISUP Cause Value
SIP Response
Normal event
1 – unallocated number
404 Not Found
2 – no route to network
404 Not Found
3 – no route to destination
404 Not Found
16 –  normal call clearing
--- (*)
17 – user busy
486 Busy here
18 – no user responding
408 Request Timeout
19 – no answer from the user
480 Temporarily unavailable
20 – subscriber absent
480 Temporarily unavailable
21 – call rejected
403 Forbidden (+)
22 – number changed (s/ o diagnostic)
410 Gone
22 – number changed ( w/ diagnostic)
301 Moved permanently
23 – redirection to new destination
 410 Gone
26 – non-selected user clearing
404 Not Found (=)
27 – destination out of order
502 Bad Gateway
28 – address incomplete
484 Address incomplete
29 – facility rejected
510 Not implemented
31 – normal unspecified
480 Temporarily unavailable Resource unavailable
34 – no circuit available
503 Service unavailable
38 – network out of order
503 Service unavailable
41 – temporary failure
503 Service unavailable
42 – switching equipment congestion
503 Service unavailable
47 – resource unavailable
 503 Service unavailable Service or option not available
55 – incoming calls barred within CUG
403 Forbidden
57 – bearer capability not authorized
403 Forbidden
58 – bearer capability not presently available
503 Service unavailable
65 – bearer capability not implemented
488 Not Acceptable here
70 – Only restricted digital information bearer capability is available (National use)
488 Not Acceptable here
79 – service or option not implemented
501 Not implemented
Invalid message

87 – user not member of CUG
403 Forbidden
88 – incompatible destination
503 Service unavailable


102 – Call Setup Time-out Failure
504 Gateway timeout
111 – Protocol Error  Unspecified
500 Server internal error Interworking
127 – Internal Error - interworking unspecified
500 Server internal error



500 – Server internal error (default)







(*) ISDN Cause 16 will usually result in a BYE or CANCEL
(+) If the cause location is ‘user’ than the 6xx code could be given rather than the 4xx code. the cause value received in the H.225.0 message is unknown in ISUP, the unspecified cause value of the class is sent.
(=) ANSI procedure

SIP Status Code to ISDN Cause Code Mapping


Response received Cause value in the REL

400 –  Bad Request 41 – Temporary failure
401 –  Unauthorized 21 – Call rejected (*)
402 –  Payment required 21 – Call rejected
403 –  Forbidden 21 – Call rejected
404 –  Not Found 1   – Unallocated number
405 –  Method not allowed 63 –  Service or option unavailable
406 – Not acceptable 79 – Service/option not implemented (+)
407 – Proxy authentication required 21 – Call rejected (*)
408 – Request timeout 102 – Recovery on timer expiry
410 – Gone 22  –  Number changed (w/o diagnostic)
413 – Request Entity too long 127 – Interworking (+)
414 – Request –URI too long 127 – Interworking (+)
415 – Unsupported media type 79 – Service/option not implemented (+)
416 – Unsupported URI Scheme 127 – Interworking (+)
402 – Bad extension 127 – Interworking (+)
421 – Extension Required 127 – Interworking (+)
423 – Interval Too Brief 127 – Interworking (+)
480 – Temporarily unavailable 18 – No user responding
481 – Call/Transaction Does not Exist 41 – Temporary Failure
482 – Loop Detected 25 – Exchange – routing error
483 – Too many hops 25 – Exchange – routing error
484 – Address incomplete 28 – Invalid Number Format (+)
485 – Ambiguous 1 – Unallocated number
486 – Busy here 17 – User Busy
487 – Request Terminated --- (no mapping)
488 – Not Acceptable here --- by warning header
500 – Server internal error 41 – Temporary Failure
501 – Not implemented 79 – Not implemented, unspecified
502 – Bad gateway 38 – Network out of order
503 – Service unavailable 41 – Temporary Failure
504 – Service time-out 102 – Recovery on timer expiry
505 – Version Not supported 127 – Interworking (+)
513 – Message Too Large 127 – Interworking (+)
600 – Busy everywhere 17 – User busy
603 – Decline 21 – Call rejected
604 – Does not exist anywhere 1 – Unallocated number
606 – Not acceptable --- by warning header

SYSLOGs


SYSLOG or system logging is one of many interesting concepts in Cisco world. Log messages monitoring and audit is one of the main parts of a network engineer life. Log messages are displayed in real time on the route, once we make some changes in the network, or if any issue happens to our network devices. We can also send these log messages from the router to a centralized NMS for monitoring in a Network Operations Center.  IOS can log messages to :

  • Console
  • Monitor (VTY, AUX) usually enabled via terminal monitor command in global config mode.
  • Buffer
  • Trap (SYSLOG) to send logs to an NMS


One important thing to understand is the concept of logging levels. Logging levels simply specify the type of log messages we want to send to our desired logging buffer/terminal/server.  Different logging levels can be set via logging console command:



Let understand severity level concept:


Severity level 3 means 0, 1 , 2, 3 ( severity level  0/1/2/3 enabled), and the router will send all corresponding severity level log messages to our desired destinations.
If we don’t want to mention the severity level # , we can specifity the name of the logging severity, for which we want the router to send all updates, for example if we want to send all Critical Condition logs, we can enable it via the following command :

R1(config)#logging console critical

The severity level command comes in handy, when we want to enable different types of logging in one go. 

In the second part of this article, i will discuss the practical implementation of SysLog in GNS3.


SNMP: Simple Network Management Protocol


SNMP: Simple Network Management Protocol

SNMP is used for monitoring of network devices, collects logs and health statistics of different device nodes. SNMP data can be collected on a centralized NMS (Network Management System), the collected data can be plotted for a better representation of the overall network health. SNMP collects all of its data via SNMP Pooling and SNMP traps. Some famous SNMP supported NMSs are IBM Tivoli, PRTG and MRTG grapher. Many free SNMP based software is also available in the open source community.

Quick Facts about SNMP:
  • SNMP Poll uses UDP 161
  • SNMP Trap uses UDP 162
  • SNMPv3 allows username authentication and packet encryption
  • SNMP Inform requires packet acknowledgement, while SNMP Trap does not
  • SNMP versions: SNMPv1, SNMPv2c & SNMPv3
SNMP Configuration in GNS3

Suppose, we are setting in a NOC (Network Operations Center). Our network is up and running, our task is to configure an SNMP based NMS to monitor our Core Network Router (R1), which is critical for our network operations. We are using a very popular NMS, known as PRTG (Packet router traffic Grapher). PRTG is a very popular used NMS, very good, efficient and excellent graphical interface, which gives us a very remarkable view of our critical network elements.

The simple flow of the topology is as follows:

A 2691 router is connected to a cloud (in GNS3, Cloud is used to connect the router to our PC physical interface). PRTG NMS has been configured on PC1 (local host). The topology is given below:


The IPs used:

  • Fast Ethernet 0/0 ( R1) : 192.168.0.99/24
  • NMS PC1 IP : 192.168.0.100/24
SNMP enabled via the following commands on R1:

We need to configure a community string (community string is a sort of snmp password) for our snmp server on the router, in our case as we are using community string “PRTG” (using PRTG as the community string for simplicity):

snmp-server community PRTG RW

Above command, simply means that we have enabled PRTG as a password for our snmp-server. You need to use this password while configuring the SNMP settings on your NMS, in our case its PRTG. In the next step we are going to set our SNMP server host address:











Host means our SNMP server IP address, in our case it is: 192.168.0.101/24.

And you can also select which version of SNMP you want to use by:











We have done our configuration on PRTG server and have enabled the monitoring of Fast Ethernet 0/0 interface of R1. The NMS output can be shown as:



In the above example we have configured our NMS to monitor R1 Health and R1 Fast Ethernet 0/0 interface status. The sample outputs from NMS are:




Some more amazing graphs:



All the logs related to our above simple network are maintained:




SNMP Packets:

To check SNMP in action, we can use: debug snmp packets command. The sample debug output for above network is:




SNMP is the most interesting topic to study and configure, you can download many propriety and open source SNMP based NMS tools from internet to experiment with.

Shah Hussain (c) 






Changes made to ICND1 and ICND2 Exams

List of Changes in ICND1 and ICND2 exams


A comprehensive analysis of changes made to ICND1 and ICND2 exams. Please follow these guidelines, if you are going to prepare for your ICND1 and ICND2 exams.

Changes in ICND1:


Candidates who currently have a CCENT or have passed 640-820 ICND1 exam and would like to pursue a CCNA Routing and Switching certification using the 200-101 ICND2 exam or any of the other Associate-level exams, the following shows content that has been added to the new curriculum and exam for 100-101 ICND1. Candidates are  encouraged to gain the knowledge difference before attempting to take the Associate-level exams.

Topics Removed from the ICND1 Exam: 

• Securing the Network 
• Understanding the Challenges of Shared LANs 
• Solving Network Challenges with Switched LAN Technologies 
• Wireless LANs 
• Using Cisco SDM 
• Configuring Serial Encapsulation 
• Enabling RIP 

Topics Added to the ICND1 Exam: 

• Implementing VLSM 
• Scaling the Network with NAT and PAT 
• Managing Traffic Using ACLs 
• Implementing VLANs and Trunks 
• Routing Between VLANs 
• Implementing single area OSPF 
• Introducing Basic IPv6 
• Understanding IPv6 
• Configuring IPv6 Routing 


Changes in ICND2:


Candidates who currently have a CCNA Routing and Switching certification and are preparing to recertify, should be made aware that the 200-101 ICND2 exam has been redesigned. Candidates are encouraged to review the topic modifications before attempting to take the 200-101 ICND2 exam.

Topics Removed from the ICND2 Exam: 

• Routing Between VLANs 
• Securing the Expanded Network 
• Implementing VLSM 
• Scaling the Network with NAT and PAT 

Topics Added to the ICND2 Exam: 

• Troubleshooting VLAN Connectivity 
• Understand Spanning Tree Protocol 
• Understand and configure Etherchannel 
• Understand Layer 3 Redundancy Protocols 
• Troubleshooting IPv4 Network Connectivity 
• Troubleshooting IPv6 Network Connectivity 
• Implementing EIGRP 
• Troubleshooting EIGRP 
• Implementing EIGRP for IPv6 
• Multi-area OSPF IPv4 Implementation 
• Understanding and configuring OSPFv3 
• Understanding and configuring clients for SNMP, Syslog and Netflow 
• Managing Cisco devices 
• Understanding and verifying Cisco licensing

Well, please prepare all these topics before appearing for your CCNA/ICND exams.