| Port | Protocol | Network Service | System Service | System Service Logical Name |
| 7 | TCP | Echo | Simple TCP/IP Services | SimpTcp |
| 7 | UDP | Echo | Simple TCP/IP Services | SimpTcp |
| 9 | TCP | Discard | Simple TCP/IP Services | SimpTcp |
| 9 | UDP | Discard | Simple TCP/IP Services | SimpTcp |
| 13 | TCP | Daytime | Simple TCP/IP Services | SimpTcp |
| 13 | UDP | Daytime | Simple TCP/IP Services | SimpTcp |
| 17 | TCP | Quotd | Simple TCP/IP Services | SimpTcp |
| 17 | UDP | Quotd | Simple TCP/IP Services | SimpTcp |
| 19 | TCP | Chargen | Simple TCP/IP Services | SimpTcp |
| 19 | UDP | Chargen | Simple TCP/IP Services | SimpTcp |
| 20 | TCP | FTP default data | FTP Publishing Service | MSFtpsvc |
| 21 | TCP | FTP control | FTP Publishing Service | MSFtpsvc |
| 21 | TCP | FTP control | Application Layer Gateway Service | ALG |
| 23 | TCP | Telnet | Telnet | TlntSvr |
| 25 | TCP | SMTP | Simple Mail Transport Protocol | SMTPSVC |
| 25 | UDP | SMTP | Simple Mail Transport Protocol | SMTPSVC |
| 25 | TCP | SMTP | Exchange Server | |
| 25 | UDP | SMTP | Exchange Server | |
| 42 | TCP | WINS Replication | Windows Internet Name Service | WINS |
| 42 | UDP | WINS Replication | Windows Internet Name Service | WINS |
| 53 | TCP | DNS | DNS Server | DNS |
| 53 | UDP | DNS | DNS Server | DNS |
| 53 | TCP | DNS | Internet Connection Firewall/Internet Connection Sharing | SharedAccess |
| 53 | UDP | DNS | Internet Connection Firewall/Internet Connection Sharing | SharedAccess |
| 67 | UDP | DHCP Server | DHCP Server | DHCPServer |
| 67 | UDP | DHCP Server | Internet Connection Firewall/Internet Connection Sharing | SharedAccess |
| 69 | UDP | TFTP | Trivial FTP Daemon Service | tftpd |
| 80 | TCP | HTTP | Windows Media Services | WMServer |
| 80 | TCP | HTTP | World Wide Web Publishing Service | W3SVC |
| 80 | TCP | HTTP | SharePoint Portal Server | |
| 88 | TCP | Kerberos | Kerberos Key Distribution Center | Kdc |
| 88 | UDP | Kerberos | Kerberos Key Distribution Center | Kdc |
| 102 | TCP | X.400 | Microsoft Exchange MTA Stacks | |
| 110 | TCP | POP3 | Microsoft POP3 Service | POP3SVC |
| 110 | TCP | POP3 | Exchange Server | |
| 119 | TCP | NNTP | Network News Transfer Protocol | NntpSvc |
| 123 | UDP | NTP | Windows Time | W32Time |
| 123 | UDP | SNTP | Windows Time | W32Time |
| 135 | TCP | RPC | Message Queuing | msmq |
| 135 | TCP | RPC | Remote Procedure Call | RpcSs |
| 135 | TCP | RPC | Exchange Server | |
| 135 | TCP | RPC | Certificate Services | CertSvc |
| 135 | TCP | RPC | Cluster Service | ClusSvc |
| 135 | TCP | RPC | Distributed File System | DFS |
| 135 | TCP | RPC | Distributed Link Tracking | TrkSvr |
| 135 | TCP | RPC | Distributed Transaction Coordinator | MSDTC |
| 135 | TCP | RPC | Event Log | Eventlog |
| 135 | TCP | RPC | Fax Service | Fax |
| 135 | TCP | RPC | File Replication | NtFrs |
| 135 | TCP | RPC | Local Security Authority | LSASS |
| 135 | TCP | RPC | Remote Storage Notification | Remote_Storage_User_Link |
| 135 | TCP | RPC | Remote Storage Server | Remote_Storage_Server |
| 135 | TCP | RPC | Systems Management Server 2.0 | |
| 135 | TCP | RPC | Terminal Services Licensing | TermServLicensing |
| 135 | TCP | RPC | Terminal Services Session Directory | Tssdis |
| 137 | UDP | NetBIOS Name Resolution | Computer Browser | Browser |
| 137 | UDP | NetBIOS Name Resolution | Server | lanmanserver |
| 137 | UDP | NetBIOS Name Resolution | Windows Internet Name Service | WINS |
| 137 | UDP | NetBIOS Name Resolution | Net Logon | Netlogon |
| 137 | UDP | NetBIOS Name Resolution | Systems Management Server 2.0 | |
| 138 | UDP | NetBIOS Datagram Service | Computer Browser | Browser |
| 138 | UDP | NetBIOS Datagram Service | Messenger | Messenger |
| 138 | UDP | NetBIOS Datagram Service | Server | lanmanserver |
| 138 | UDP | NetBIOS Datagram Service | Net Logon | Netlogon |
| 138 | UDP | NetBIOS Datagram Service | Distributed File System | Dfs |
| 138 | UDP | NetBIOS Datagram Service | Systems Management Server 2.0 | |
| 138 | UDP | NetBIOS Datagram Service | License Logging Service | LicenseService |
| 139 | TCP | NetBIOS Session Service | Computer Browser | Browser |
| 139 | TCP | NetBIOS Session Service | Fax Service | Fax |
| 139 | TCP | NetBIOS Session Service | Performance Logs and Alerts | SysmonLog |
| 139 | TCP | NetBIOS Session Service | Print Spooler | Spooler |
| 139 | TCP | NetBIOS Session Service | Server | lanmanserver |
| 139 | TCP | NetBIOS Session Service | Net Logon | Netlogon |
| 139 | TCP | NetBIOS Session Service | Remote Procedure Call Locator | RpcLocator |
| 139 | TCP | NetBIOS Session Service | Distributed File System | Dfs |
| 139 | TCP | NetBIOS Session Service | Systems Management Server 2.0 | |
| 139 | TCP | NetBIOS Session Service | License Logging Service | LicenseService |
| 143 | TCP | IMAP | Exchange Server | |
| 161 | UDP | SNMP | SNMP Service | SNMP |
| 162 | UDP | SNMP Traps Outbound | SNMP Trap Service | SNMPTRAP |
| 270 | TCP | MOM 2004 | Microsoft Operations Manager 2004 | MOM |
| 389 | TCP | LDAP Server | Local Security Authority | LSASS |
| 389 | UDP | LDAP Server | Local Security Authority | LSASS |
| 389 | TCP | LDAP Server | Distributed File System | Dfs |
| 389 | UDP | LDAP Server | Distributed File System | Dfs |
| 443 | TCP | HTTPS | HTTP SSL | HTTPFilter |
| 443 | TCP | HTTPS | World Wide Web Publishing Service | W3SVC |
| 443 | TCP | HTTPS | SharePoint Portal Server | |
| 445 | TCP | SMB | Fax Service | Fax |
| 445 | TCP | SMB | License Logging Service | LicenseService |
| 445 | TCP | SMB | Print Spooler | Spooler |
| 445 | TCP | SMB | Server | lanmanserver |
| 445 | TCP | SMB | Remote Procedure Call Locator | RpcLocator |
| 445 | TCP | SMB | Distributed File System | Dfs |
| 445 | TCP | SMB | Net Logon | Dfs |
| 500 | UDP | IPSec ISAKMP | Local Security Authority | LSASS |
| 515 | TCP | LPD | TCP/IP Print Server | LPDSVC |
| 548 | TCP | File Server for Macintosh | File Server for Macintosh | MacFile |
| 554 | TCP | RTSP | Windows Media Services | WMServer |
| 563 | TCP | NNTP over SSL | Network News Transfer Protocol | NntpSvc |
| 593 | TCP | RPC over HTTP | Remote Procedure Call | RpcSs |
| 593 | TCP | RPC over HTTP | Exchange Server | |
| 636 | TCP | LDAP SSL | Local Security Authority | LSASS |
| 636 | UDP | LDAP SSL | Local Security Authority | LSASS |
| 993 | TCP | IMAP over SSL | Exchange Server | |
| 995 | TCP | POP3 over SSL | Exchange Server | |
| 1270 | TCP | MOM-Encrypted | Microsoft Operations Manager 2000 | one point |
| 1433 | TCP | SQL over TCP | Microsoft SQL Server | SQLSERVR |
| 1433 | TCP | SQL over TCP | MSSQL$UDDI | SQLSERVR |
| 1434 | UDP | SQL Probe | Microsoft SQL Server | SQLSERVR |
| 1434 | UDP | SQL Probe | MSSQL$UDDI | SQLSERVR |
| 1645 | UDP | Legacy RADIUS | Internet Authentication Service | IAS |
| 1646 | UDP | Legacy RADIUS | Internet Authentication Service | IAS |
| 1701 | UDP | L2TP | Routing and Remote Access | RemoteAccess |
| 1723 | TCP | PPTP | Routing and Remote Access | RemoteAccess |
| 1755 | TCP | MMS | Windows Media Services | WMServer |
| 1755 | UDP | MMS | Windows Media Services | WMServer |
| 1801 | TCP | MSMQ | Message Queuing | msmq |
| 1801 | UDP | MSMQ | Message Queuing | msmq |
| 1812 | UDP | RADIUS Authentication | Internet Authentication Service | IAS |
| 1813 | UDP | RADIUS Accounting | Internet Authentication Service | IAS |
| 1900 | UDP | SSDP | SSDP Discovery Service | SSDPRSRV |
| 2101 | TCP | MSMQ-DCs | Message Queuing | msmq |
| 2103 | TCP | MSMQ-RPC | Message Queuing | msmq |
| 2105 | TCP | MSMQ-RPC | Message Queuing | msmq |
| 2107 | TCP | MSMQ-Mgmt | Message Queuing | msmq |
| 2393 | TCP | OLAP Services 7.0 | SQL Server: Downlevel OLAP Client Support | |
| 2394 | TCP | OLAP Services 7.0 | SQL Server: Downlevel OLAP Client Support | |
| 2460 | UDP | MS Theater | Windows Media Services | WMServer |
| 2535 | UDP | MADCAP | DHCP Server | DHCPServer |
| 2701 | TCP | SMS Remote Control (control) | SMS Remote Control Agent | |
| 2701 | UDP | SMS Remote Control (control) | SMS Remote Control Agent | |
| 2702 | TCP | SMS Remote Control (data) | SMS Remote Control Agent | |
| 2702 | UDP | SMS Remote Control (data) | SMS Remote Control Agent | |
| 2703 | TCP | SMS Remote Chat | SMS Remote Control Agent | |
| 2703 | UDP | SMS Remote Chat | SMS Remote Control Agent | |
| 2704 | TCP | SMS Remote File Transfer | SMS Remote Control Agent | |
| 2704 | UDP | SMS Remote File Transfer | SMS Remote Control Agent | |
| 2725 | TCP | SQL Analysis Services | SQL 2000 Analysis Server | |
| 2869 | TCP | UPNP | Universal Plug and Play Device Host | UPNPHost |
| 2869 | TCP | SSDP event notification | SSDP Discovery Service | SSDPRSRV |
| 3268 | TCP | Global Catalog Server | Local Security Authority | LSASS |
| 3269 | TCP | Global Catalog Server | Local Security Authority | LSASS |
| 3343 | UDP | Cluster Services | Cluster Service | ClusSvc |
| 3389 | TCP | Terminal Services | NetMeeting Remote Desktop Sharing | mnmsrvc |
| 3389 | TCP | Terminal Services | Terminal Services | TermService |
| 3527 | UDP | MSMQ-Ping | Message Queuing | msmq |
| 4011 | UDP | BINL | Remote Installation | BINLSVC |
| 4500 | UDP | NAT-T | Local Security Authority | LSASS |
| 5000 | TCP | SSDP legacy event notification | SSDP Discovery Service | SSDPRSRV |
| 5004 | UDP | RTP | Windows Media Services | WMServer |
| 5005 | UDP | RTCP | Windows Media Services | WMServer |
| 42424 | TCP | ASP.Net Session State | ASP.NET State Service | aspnet_state |
| 51515 | TCP | MOM-Clear | Microsoft Operations Manager 2000 | one point |
Friday, September 19, 2008
Friday, August 1, 2008
Managing MYSL on Linux
Field Types in SQL
INTEGER - A whole number
VARCHAR(10) - Up to 10 characters.
CHAR(10) - Fixed number of characters
DATE - A date
DATETIME - Date and time
FLOAT - Floating point numbers
Field Types specific to MySQL
TEXT - Allows up to 65535 characters
DECIMAL(10,2) - Up to 10 digits before the point, 2 after.
Field Types specific to MySQL
TEXT - Allows up to 65535 characters
DECIMAL(10,2) - Up to 10 digits before the point, 2 after.
TO create the Database
$ mysqladmin --user=ravi --password=xxx create database addressdbList the tables in the database "addressdb"
To use the Database$ mysql --user=ravi --password=xxx
mysql> USE addressdb,
To create Table
mysql> CREATE TABLE p_addr (i INTEGER PRIMARY KEY,address TEXT,email VARCHAR(30),pincode DECIMAL(10),phone DECIMAL(15),website TEXT);
To add a column "india" to the table
mysql> ALTER TABLE p_addr ADD india VARCHAR(30);
To insert value in Table
mysql> INSERT INTO p_addr VALUES (1,"My, present, address","prakash@xyz.com",681024,2122536, "http://gadbu.blogspot.com","Prakash");
To List the contents of the Table
mysql> SELECT * FROM p_addr;
To delete a row from Table
mysql> DELETE FROM p_addr WHERE i=1;
To Rename a column in the table from "address" to "home_address"
mysql> ALTER TABLE p_addr CHANGE address home_address INTEGER;
Note: You cannot use this method to rename a column which is a primary key.
Change an existing record in the table
mysql> UPDATE p_addr SET name="Sumitra" WHERE i=2;
Delete the table from the database
mysql> DROP TABLE p_addr;
List the databases
$ mysqlshow --user=ravi --password=xxx
$ mysqlshow --user=ravi --password=xxx addressdb
Tuesday, July 8, 2008
TCP DUMP TIPS
tcpdump -w trace.cap -p -n -s 0 "udp”- -p : doesn’t start in promiscuous mode, only frames from or to the Asterisk node will be captured,-n : no name resolution, otherwise we will have a lot of DNS queries which is not useful at that stage, we could do name resolution afterwards if needed,
- -s 0 : we get the full frame, not only the first bytes. When working only at the protocol level it is enough to get only the start of each frames, in our case we are requiring the content of the SIP and RTP frames. 0 means getting the whole frame,
- -w output file : all the captured frames will be stored in the file. That way we will be able, afterwards, to analyze the frames from the file. If using ‘-’ as the name of the file, the output is send to the standard output, we will use this afterwards.
- tcpdump not port 22 (to exclude port 22)
- tcpdump not port 143 and not port 25 and not port 22
- tcpdump port 143
- tcpdump host hal9000 (to get data from a specific host on the network)
- tcpdump -i eth1
- tcpdump udp (to specify a protocol )
- tcpdump -l | tee tcpdump_`date +%Y%m%e-%k.%M` (to Save Output for Later)
To dump its output into a binary format which it can read later.
To create a binary file
- tcpdump -w tcpdump_raw_`date +%Y%m%e-%k.%M` ( To create a binary file)
- tcpdump -r tcpdump_raw_YYYMMDD-H.M (To read the created file)
- all packets arriving at or departing from 192.168.0.2
- # tcpdump -n host 192.168.0.2
- To print traffic between 192.168.0.2 and either 10.0.0.4 or 10.0.0.5:
- # tcpdump -n host 192.168.0.2 and \( 10.0.0.4 or 10.0.0.5 \)
- To print all IP packets between 192.168.0.2 and any host except 10.0.0.5:
- # tcpdump ip -n host 192.168.0.2 and not 10.0.0.5
- To print all ftp traffic through internet gateway xx:
- # tcpdump 'gateway xx and (port ftp or ftp-data)'
- To print traffic neither sourced from nor destined for local hosts (if you gateway to one other net, this stuff should never make it onto your local net).
- # tcpdump ip and not net localnet
- To print the start and end packets (the SYN and FIN packets) of each TCP conversation that involves a non-local host.
- # tcpdump 'tcp[13] & 3 != 0 and not src and dst net localnet'
- To print IP packets longer than 576 bytes sent through gateway xx:
- # tcpdump 'gateway xx and ip[2:2] > 576'
- To print IP broadcast or multicast packets that were not sent via ethernet broadcast or multicast:
- # tcpdump 'ether[0] & 1 = 0 and ip[16] >= 224'
- To print all ICMP packets that are not echo requests/replies (i.e., not ping packets):
- # tcpdump 'icmp[0] != 8 and icmp[0] != 0"
Saturday, June 14, 2008
Friday, June 6, 2008
Hard Disk Cloning in Linux
To make a clone of a hard disk /dev/sda on an empty hard disk /dev/sdb type the following command
dd if=/dev/sda of=/dev/sdb
Note:-
- here if specifies input file and of specifies output file.
- Wait untill the command is finished.
- Finally you will have an exact copy of the hard disk.
Thursday, June 5, 2008
command to replace a word from a file.
Friday, May 30, 2008
Change Speed & Duplex settings of LAN card
- mii-tool or mii-tool eth0
- ethtool eth0
ethtool -s eth0 speed 100 duplex fullethtool -s eth0 speed 10 duplex halfmii-tool -F 100baseTx-FD (toforce a particular speed and duplex settings)
- Go to this file /etc/sysconfig/network-scripts/ifcfg-eth0 & then and put this entry in the file
ETHTOOL_OPTS="speed 100 duplex full autoneg off"
service network restart
Tuesday, May 27, 2008
Internet Sharing in Linux using IPTABLES
Enable IP forwarding
sysctl -w net.ipv4.ip_forward=1
To enable it in system startup, edit the file /etc/sysctl.conf and set
net.ipv4.ip_forward = 1
iptables
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
service iptables save
Network Configuration
The configuration should be like this
Router:-Connected to the internet provider
IP : 192.168.1.1
Internet Connected System
eth0 (LAN Card 1):-Connected to router
- IP : 192.168.1.10
- Netmask : 255.255.255.0
- Gateway : 192.168.1.1 (IP of the router)
eth1 (LAN Card 2):-Connected to the other system
- IP : 192.168.0.20 (Not the same network as the first card)
- Netmask : 255.255.255.0
- Gateway : 192.168.1.1 (IP of the router)
Second System
LAN Card connected to the first system
- IP : 192.168.0.30
- Netmask : 255.255.255.0
- Gateway : 192.168.0.20 (IP of the second Card in the first system)
Thursday, May 22, 2008
SIP EVENTS
| SIP event | Decimal Cause number (DSS1) | Hex.Cause number (DSS1) | Cause |
| 400 Bad request | 127 | 7f | Interworking, unspecified |
| 401 Unauthorized | 57 | 39 | Bearer capability not authorized |
| 402 Payment required | 21 | 15 | Call rejected |
| 403 Forbidden | 57 | 39 | Bearer capability not authorized |
| 404 Not found | 1 | 01 | Unallocated (unassigned) number |
| 405 Method not allowed | 127 | 7f | Interworking, unspecified |
| 406 Not acceptable | 127 | 7f | Interworking, unspecified |
| 407 Proxy authent. required | 21 | 15 | Call rejected |
| 408 Request timeout | 102 | 66 | Recover on Expires timeout |
| 409 Conflict | 41 | 29 | Temporary failure |
| 410 Gone | 1 | 01 | Unallocated (unassigned) number |
| 411 Length required | 127 | 7f | Interworking, unspecified |
| 413 Request entity too long | 127 | 7f | Interworking, unspecified |
| 414 Request URI (URL) too long | 127 | 7f | Interworking, unspecified |
| 415 Unsupported media type | 79 | 4f | Service or option not available |
| 420 Bad extension | 127 | 7f | Interworking, unspecified |
| 480 Temporarily unavailable | 18 | 12 | No user response |
| 481 Call leg does not exist | 127 | 7f | Interworking, unspecified |
| 482 Loop detected | 127 | 7f | Interworking, unspecified |
| 483 Too many hops | 127 | 7f | Interworking, unspecified |
| 484 Address incomplete | 28 | 1c | Address incomplete (invalid number format) |
| 485 Address ambiguous | 1 | 01 | Unallocated (unassigned) number |
| 486 Busy here | 17 | 11 | User busy |
| 487 Request cancelled | 127 | 7f | Interworking, unspecified |
| 488 Not acceptable here | 127 | 7f | Interworking, unspecified |
| 500 Internal server error | 41 | 29 | Temporary failure |
| 501 Not implemented | 79 | 4f | Service or option not implemented |
| 502 Bad gateway | 38 | 26 | Network out of order |
| 503 Service unavailable | 63 | 3f | Service or option unavailable |
| 504 Gateway timeout | 102 | 66 | Recover on Expires timeout |
| 505 Version not implemented | 127 | 7f | Interworking, unspecified |
| 603 Decline | 21 | 15 | Call rejected |
| 604 Does not exist anywhere | 1 | 01 | Unallocated (unassigned) number |
| 606 Not acceptable | 58 | 3a | Bearer capability not presently available |
ISDN CAUSE CODES
Detailed ISDN Cause Codes
Cause No. l - Unallocated (unassigned) number [Q.850]
This cause indicates that the called party cannot be reached recluses although the called party number is in a valid format. It is not currently allocated (assigned).
Cause No. 2 - No route to specified transit network (national use) [Q.850]
This cause indicates that the equipment sending this cause has received a request to route the call through a particular transit network which it does not recognize. The equipment sending this cause does not recognize the transit network either because the transit network does not exist or because that particular transit network. While it does exist. does not serve the equipment which is sending this cause.
Cause No. 3 - No route to destination [Q.850]
This cause indicates that the called party cannot be reached because the network through which the call has been routed does not serve the destination desired. This cause is supported on a network dependent basis.
Cause No. 4 - send special information tone [Q.850]
This cause indicates that the called party cannot be reached for reasons that are of a long term nature and that the special information tone should be returned to the calling party.
Cause No. 5 - misdialed trunk prefix (national use) [Q.850]
This cause indicates the erroneous inclusion of a trunk prefix in the called party number. This number is to sniped from the dialed number being sent to the network by the customer premises equipment.
Cause No. 6 - channel unacceptable [Q.850]
This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call.
Cause No. 7 - call awarded. being delivered in an established channel [Q.850]
This cause indicates that the user has been awarded the incoming call and that the incoming call is being connected to a channel already established to that user for similar calls (e.g. packet-mode x.25 virtual calls).
Cause No. 8 - preemption [Q.850]
This cause indicates the call is being preempted.
Cause No. 9 - preemption - circuit reserved for reuse [Q.850]
This cause indicates that the call is being preempted and the circuit is reserved for reuse by the preempting exchange.
Cause No. 10 - normal call clearing [Q.850]
This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network.
Cause No. 17 - user busy [Q.850]
This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy it is noted that the user equipment is compatible with the call.
Cause No. 18 - no user responding [Q.850]
This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated.
Cause No. 19 - no answer from user (user alerted) [Q.850]
This cause is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time. Note - This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.
Cause No. 20 - subscriber absent [Q.850]
This cause value is used when a mobile station has logged off. radio contact is not obtained with a mobile station or if a personal telecommunication user is temporarily not addressable at any user-network interface.
Cause No. 21 - call rejected [Q.850]
This cause indicates that the equipment sending this cause does not wish to accept this call. although it could have accepted the call because the equipment sending this cause is neither busy nor incompatible. This cause may also be generated by the network, indicating that the call was cleared due to a supplementary service constraint. The diagnostic field may contain additional information about the supplementary service and reason for rejection.
Cause No. 22 - number changed [Q.850]
This cause is returned to a calling party when the called party number indicated by the calling party is no longer assigned. The new called party number may optionally be included in the diagnostic field. If a network does not support this cause, cause no. 1, unallocated (unassigned) number shall be used.
Cause No. 26 - non-selected user clearing [Q.850]
This cause indicates that the user has not been awarded the incoming call.
Cause No. 27 - destination out of order [Q.850]
This cause indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signal message was unable to be delivered to the remote party; e.g., a physical layer or data link layer failure at the remote party or user equipment off-line.
Cause No. 28 - invalid number format (address incomplete) [Q.850]
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete.
Cause No. 29 - facilities rejected [Q.850]
This cause is returned when a supplementary service requested by the user cannot be provide by the network.
Cause No. 30 - response to STATUS INQUIRY [Q.850]
This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY.
Cause No. 31 - normal. unspecified [Q.850]
This cause is used to report a normal event only when no other cause in the normal class applies.
Cause No. 34 - no circuit/channel available [Q.850]
This cause indicates that there is no appropriate circuit/channel presently available to handle the call.
Cause No. 35 - Call Queued [Q.850]
Cause No. 38 - network out of order [Q.850]
This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time e.g., immediately re-attempting the call is not likely to be successful.
Cause No. 39 - permanent frame mode connection out-of-service [Q.850]
This cause is included in a STATUS message to indicate that a permanently established frame mode connection is out-of-service (e.g. due to equipment or section failure) (see Annex A/Q.933)
Cause No. 40 - permanent frame mode connection operational [Q.850]
This cause is included in a STATUS message to indicate that a permanently established frame mode connection is operational and capable of carrying user information.
Cause No. 41 - temporary failure [Q.850]
This cause indicates that the network is not functioning correctly and that the condition is no likely to last a long period of time; e.g., the user may wish to try another call attempt almost immediately.
Cause No. 42 - switching equipment congestion [Q.850]
This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic.
Cause No. 43 - access information discarded [Q.850]
This cause indicates that the network could not deliver access information to the remote user as requested. i.e., user-to-user information, low layer compatibility, high layer compatibility or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic.
Cause No. 44 - requested circuit/channel not available [Q.850]
This cause is returned when the circuit or channel indicated by the requesting entity cannot be provided by the other side of the interface.
Cause No. 46 - precedence call blocked [Q.850]
This cause indicates that there are no predictable circuits or that the called user is busy with a call of equal or higher preventable level.
Cause No. 47 - resource unavailable, unspecified [Q.850]
This cause is used to report a resource unavailable event only when no other cause in the resource unavailable class applies.
Cause No. 49 - Quality of Service not available [Q.850]
This cause is used to report that the requested Quality of Service. as defined in Recommendation X.213. cannot be provided (e.g., throughput of transit delay cannot be supported).
Cause No. 50 - requested facility not subscribed [Q.850]
This cause indicates that the user has requested a supplementary service which is implemented by the equipment which generated this cause but the user is not authorized to use.
Cause No. 52 - outgoing calls barred
Cause No. 53 - outgoing calls barred within CUG [Q.850]
This cause indicates that although the calling party is a member of the CUG for the outgoing CUG call. Outgoing calls are not allowed for this member of the CUG.
Cause No. 54 - incoming calls barred
Cause No. 55 - incoming calls barred within CUG [Q.850]
This cause indicates that although the calling party is a member of the CUG for the incoming CUG call. Incoming calls are not allowed for this member of the CUG.
Cause No. 57 - bearer capability not authorized [Q.850]
This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but the user is not authorized to use.
Cause No. 58 - bearer capability not presently available [Q.850]
This cause indicates that the user has requested a bearer capability which is implemented by the equipment which generated this cause but which is not available at this time.
Cause No. 62 - inconsistency in outgoing information element. [Q.850]
This cause indicates an inconsistency in the designated outgoing access information and subscriber class
Cause No. 63 - service or option not available. unspecified [Q.850]
This cause is used to report a service or option not available event only when no other cause in the service or option not available class applies.
Cause No. 65 - bearer capability not implemented [Q.850]
This cause indicates that the equipment sending this cause does not support the bearer capability requested.
Cause No. 66 - channel type not implemented [Q.850]
This cause indicates that the equipment sending this cause does not support the channel type requested
Cause No. 69 - requested facility not implemented [Q.850]
This cause indicates that the equipment sending this cause does not support the requested supplementary services.
Cause No. 70 - only restricted digital information bearer capability is available (national use) [Q.850]
This cause indicates that the calling party has requested an unrestricted bearer service but the equipment sending this cause only supports the restricted version of the requested bearer capability.
Cause No. 79 - service or option not implemented unspecified [Q.850]
This cause is used to report a service or option not implemented event only when no other cause in the service or option not implemented class applies.
Cause No. 81 - invalid call reference value [Q.850]
This cause indicates that the equipment sending this cause has received a message with a call reference which is not currently in use on the user-network interface.
Cause No. 82 - identified channel does not exist [Q.850]
This cause indicates that the equipment sending this cause has received a request to use a channel not activated on the interface for a call. For example. if a user has subscribed to those channels on a primary rate interface numbered from l to 12 and the user equipment or the network attempts to use channels l 3 through 23, this cause is generated.
Cause No. 83 - a suspended call exists, but this call identify does not [Q.850]
This cause indicates that a call resume has been attempted with a call identity which differs from that in use for any presently suspended call(s).
Cause No. 84 - call identity in use [Q.850]
This cause indicates that the network has received a call suspended request containing a call identity (including the null call identity) which is already in use for a suspended call within the domain of interfaces over which the call might be resumed.
Cause No. 85 - no call suspended [Q.850]
This cause indicates that the network has received a call resume request containing a Call identity information element which presently does not indicate any suspended call within the domain of interfaces over which calls may be resumed.
Cause No. 86 - call having the requested call identity has been cleared [Q.850]
This cause indicates that the network has received a call resume request containing a Call identity information element indicating a suspended call that has in the meantime been cleared while suspended (either by network time-out or by the remote user).
Cause No. 87 - user not a member of CUG [Q.850]
This cause indicates that the called user for the incoming CUG call is not a member of the specified CUG or that the calling user is an ordinary subscriber calling a CUG subscriber.
Cause No. 88 - incompatible destination [Q.850]
This cause indicates that the equipment sending this cause has received a request to establish a call which has low layer compatibility. high layer compatibility or other compatibility attributes (e.g., data rate) which cannot be accommodated.
Cause No. 90 - non-existent CUG [Q.850]
This cause indicates that the specified CUG does not exist.
Cause No. 91 - invalid transit network selection (national use) [Q.850]
This cause indicates that a transit network identification was received which is of an incorrect format as defined in Annex C/Q.931
Cause No. 95 - invalid message, unspecified [Q.850]
This cause is used to report an invalid message event only when no other cause in the invalid message class applies.
Cause No. 96 - mandatory information element is missing [Q.850]
This cause indicates that the equipment sending this cause has received a message which is missing an information element which must be present in the message before that message can be processed.
Cause No. 97 - message type non-existent or not implemented [Q.850]
This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined of defined but not implemented by the equipment sending this cause.
Cause No. 98 - message not compatible with call state or message type non-existent or not implemented. [Q.850]
This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state. or a STATUS message was received indicating an incompatible call state.
Cause No. 99 - Information element / parameter non-existent or not implemented [Q.850]
This cause indicates that the equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.
Cause No. 100 - Invalid information element contents [Q.850]
This cause indicates that the equipment sending this cause has received and information element which it has implemented; however, one or more Gelds in the I.E. are coded in such a way which has not been implemented by the equipment sending this cause.
Cause No. 101 - message not compatible with call state [Q.850]
This cause indicates that a message has been received which is incompatible with the call state.
Cause No. 102 - recovery on timer expiry [Q.850]
This cause indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures.
Cause No. 103 - parameter non-existent or not implemented - passed on (national use) [Q.850]
This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged.
Cause No. 110 - message with unrecognized parameter discarded [Q.850]
This cause indicates that the equipment sending this cause has discarded a received message which includes a parameter that is not recognized.
Cause No. 111 - protocol error, unspecified [Q.850]
This cause is used to report a protocol error event only when no other cause in the protocol error class applies.
Cause No. 127 - Intel-working, unspecified [Q.850]
This cause indicates that an interworking call (usually a call to 5W56 service) has ended.
Notes about Cause Codes over 128
Cause code values of 128 and higher aren't sent over the network. and aren't defined in Rec. [Q.850]. A terminal displaying a value 128 or higher and claiming it is a cause code arguably has a bug or is implementing some proprietary diagnostic code (not necessarily bad). Some commendation has cause codes listed with numbers higher than 128, but at this time they are proprietary in nature. The PRI equipment vendors are the most likely to use these codes as they have been using proprietary messages in the facilities data link for some time now (there is an as yet undefined area in the FDL which is big enough to carry small datagrams or messages). It is typically used to pass proprietary control or maintenance messages between multiplexers.
Thursday, May 8, 2008
Multiple Yahoo Messanger Logins
1. Go to Start --> Run . Type regedit, then enter.
2. Go to HKEY_CURRENT_ USER --> Software -->yahoo -->pager-->Test
3. On the right page , right-click and choose new Dword value .
4. Rename it as Plural.
5. Double click and assign a decimal value of 1.
now close is and start yahoomessanger.
Disable USB storage devices (in windows XP and 2000)
Follow the instructions to Disable the access to USB port, in windows XP and 2000
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor
4. In the right pane, double-click Start.
5. In the Value data box, type 4, click Hexadecimal (if it is not already selected), and then click OK.
6. Quit Registry Editor.
Sunday, May 4, 2008
Recovering MYSQL's root's password in Linux
Type the following commands at linux prompt
1. Type /etc/init.d/mysql stop
2. /usr/bin/killall mysqld
3. mysqld --skip-grant-tables -u root &
4. mysql
5. mysql> use mysql;
6. mysql> UPDATE user
7. -> SET password=password("putyourpasswordhere")
8. -> WHERE user="root";
9. mysql> flush privileges;
10. mysql> exit
11. /etc/init.d/mysql start
Thursday, May 1, 2008
Enable Hiiden Folder in Windows XP
1. Go to Start ==> Run ==> type regedit and then press enter
2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
Explorer\Advanced\Folder\Hidden\SHOWALL
Double click on CheckedValue being shown on the right hand side of the page.
Just change the value of 'Value Data' from 0 to 1 .
A virus must have altered it to 0.
Now u will be able to see the hideen files will show on enabling the folder options.
2. Then go to User Configuration ->Administrative Templates --> Windows Components --> Windows Explorer-> Removes the Folder Options menu item from the Tools menu.
Right click:-> Properties -> Disable ->Apply -> Again set it to not configured