Introduction
This document describes the Cisco Intelligent Contact Management (ICM) rttest utility, which allows you to view and set various parameters on an ICM Call Router. You can run the rttest utility in one of three ways:
From a command prompt directly on one of the Cisco ICM Call Router nodes
From a Telnet session into one of the Cisco ICM Call Router nodes
From a command prompt using pcAnywhere to one of the Cisco ICM Call Router nodes
Components Used
The information in this document is based on these software and hardware versions:
All Cisco ICM versions
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
How to Run and Interpret rttest
Type rttest at a command prompt followed by /help or /?. This gives you a syntax usage statement. For example:
c:\icr\cicr1\ra\logfiles>rttest /?
Version: Release 4.0, Build 04624
Usage: rttest [/f InputFile] [/system SystemName]
[/cust Customer]
[/node ICRNode] [/pipe OutputPipe] [/debug] [/stop] [/help] [/?]
The command line options required to invoke rttest are:
/cust Customer
Where Customer is a three-, four-, or five-letter acronym signifying the ICM customer instance. Refer to ICM Server Naming Conventions.
/node ICRNode
Where ICRNode is either routera or routerb, depending on the router rttest to run. Refer to ICM Server Naming Conventions.
Once rttest is running, enter a ? or help at the rttest prompt to list all available rttest commands.
If the rttest command is run, you can quickly get a real time status of the entire ICM system.
At the rttest prompt, type status.
Press Enter at the rttest prompt.
The status directive returns the current state of each ICM central site process, ICM Peripheral Gateway (PG) server, and third-party automatic call distributor (ACD) and Voice Response Unit (VRU) peripheral.
c:\> rttest /cust csco /node routera
rttest:
rttest: status
Router Version: Release 2.5 (service pack 2), Build 03134
Release Date: 12/23/98 13:30:08
Current Time: 03/17 16:00:42
Local Time: 03/17 11:00:42 (-5.0 hr)
Router Up: 02/21 01:01:45 (24.6 day)
Router Sync: 03/11 11:06:20 (6.2 day) (A->B)
More Info please refer this link - http://www.cisco.com/en/US/partner/products/sw/custcosw/ps1001/products_tech_note09186a00800ac69b.shtml
Using the OPCTest Command-Line Utility - PG
Introduction
The Open Peripheral Controller (OPC) Test (opctest) command-line utility allows you to view and set various parameters in a Cisco Intelligent Contact Management (ICM) Peripheral Gateway (PG) OPC process. You can run opctest at a Microsoft Windows OS command prompt or from a Telnet session.
Note: Use a command prompt, either at a PC or through pcANYWHERE. Use of the command prompt is better because the columns of data often display more than Telnet can show.
Run opctest
Complete these steps in order to start opctest:
Issue the opctest /cust custname /node ICM node name command.
Note: custname indicates customer name, and ICM node name is the node name. An example is opctest /cust abc /node pgx.
Issue the opctest /? command at a command prompt.
This command shows you information on running opctest.
After you start opctest, type help or ? in order to view a list of all available commands.
The most common command is status, which displays the health and state of the PG.
Here is some sample output:
C:\> opctest /?
Version: Release 4.0, Build 04624
Usage: opctest [/f InputFile] [/system SystemName] [/cust Customer]
[/node ICRNode] [/pipe OutputPipe] [/debug] [/stop] [/help] [/?]
Figure 1 shows more detailed output for the status command:
Figure 1—OPCTest status Output
Note: In ICM version 4.1, the Peripheral Gateway Agent (PGAgent) section only displays Connect time for the current active side. In this example, PGAgent on PG5B is the active side. PG5A is idle:
PGAgent LastStateChangeTime ConnectATime Status ConnectBTime Status
SideA P-- 02/01 11:50:23 (3.2 hr) IDLE AGENT IDLE AGENT
SideB PIA 02/01 11:48:54 (3.2 hr) 02/01 11:48:54 (3.2 hr) CONNECTED 02/01 11:48:54 (3.2 hr) CONNECTED
opctest Commands
Type help or ? at the opctest command prompt in order to view a list of available commands.
Some of the opctest commands, such as List_Agents and List_Trunk_Group, require one or more additional command-line switches. Type command name /? in order to obtain the proper syntax. Here is an example:
opctest: la
list_agents: Error for PeripheralID: Missing argument.
opctest: la /?
Usage: list_agents PeripheralID [/agent AgentID] [/state AgentState]
[/group SkillGroupID] [/agpri SkillGroupPriority] [/logout]
[/help] [/?]
opctest: la 5004
SkillGroup= 0 Pri= 0 ----- LoggedOn=23 Avail=0 NotReady=4 Ready=19 TalkingIn=16
TalkingOut=0 TalkingOther=3 WorkRdy=0 WorkNRdy=0 Busy=0
Reserved=0 Hold=0
SkillGroup= 1 Pri= 0 ----- LoggedOn=9 Avail=0 NotReady=1 Ready=8 TalkingIn=7
TalkingOut=0 TalkingOther=1 WorkRdy=0 WorkNRdy=0 Busy=0
Reserved=0 Hold=0
SkillGroup= 2 Pri= 0 ----- LoggedOn=25 Avail=0 NotReady=4 Ready=21 TalkingIn=20
opctest: ltg
list_trunk_groups: Error for PeripheralID: Missing argument.
opctest: ltg 5004
Perph# SkTargetID NTGSkTargetID NumTrunks LastHHU Tracing Ext
ConfigParam
0 5057 5005 -1 02/01 14:30:00 0
1 5058 5005 -1 02/01 14:30:00 0
2 5059 5005 -1 02/01 14:30:00 0
3 5060 5005 -1 02/01 14:30:00 0
4 5061 5005 -1 02/01 14:30:00 0
5 5062 5005 -1 02/01 14:30:00 0
6 5063 5005 -1 02/01 14:30:00 0
7 5064 5005 -1 02/01 14:30:00 0
8 5065 5005 -1 02/01 14:30:00 0
9 5066 5005 -1 02/01 14:30:00 0
10 5067 5005 -1 02/01 14:30:00 0
12 5010 5005 -1 02/01 14:30:00 0
13 5011 5005 -1 02/01 14:30:00 0
14 5068 5005 -1 02/01 14:30:00 0
Debug Information
Issue the debug command in order to enable specific debugging within opctest. The debug command enables debug control by turning up tracing. An enablement of debug control is much more effective than if you adjust the registry or turn up the EMSTraceMask for the OPC process. The enablement of debug control turns up tracing on the part of OPC, for which you need additional tracing. The tracing result displays in the OPC Event Management System (EMS) log files. Use dumplog in order to view the output of the EMS logs. Refer to How to Use the Dumplog Utility for more information.
Here is an example:
opctest: debug /?
Usage: debug_control [/realtime] [/agent] [/halfhour] [/rcmeter] [/routing]
[/skillgroup] [/closedcalls] [/cstaecr] [/cstacer]
[/pimmsg] [/ctimsg] [/rcmsg] [/dmpmsg] [/icmsg] [/opcmsg]
[/mdsmsg] [/pdmsg] [/inrcmsg] [/passthru] [/tpmsg]
[/physctrlr] [/periph] [/all] [/help] [/?]
Issue the debug /routing command if you need to troubleshoot a translation route problem.
When you finish troubleshooting, use the /noall switch in order to turn off all OPC tracing. If you leave tracing turned up, performance problems can result.
Exit and Quit opctest
Issue the quit command in order to exit the opctest utility.
Caution: Use caution when you issue the exit_opc command. This command instructs the OPC process to exit on both sides of the PG, if duplexed. Node Manager forces the process to restart, which then forces a reload of the configuration for the Call Router. All internal peripheral and agent states are flushed. Then, OPC and Peripheral Interface Manager (PIM) relearn the PG and its configuration.
The Open Peripheral Controller (OPC) Test (opctest) command-line utility allows you to view and set various parameters in a Cisco Intelligent Contact Management (ICM) Peripheral Gateway (PG) OPC process. You can run opctest at a Microsoft Windows OS command prompt or from a Telnet session.
Note: Use a command prompt, either at a PC or through pcANYWHERE. Use of the command prompt is better because the columns of data often display more than Telnet can show.
Run opctest
Complete these steps in order to start opctest:
Issue the opctest /cust custname /node ICM node name command.
Note: custname indicates customer name, and ICM node name is the node name. An example is opctest /cust abc /node pgx.
Issue the opctest /? command at a command prompt.
This command shows you information on running opctest.
After you start opctest, type help or ? in order to view a list of all available commands.
The most common command is status, which displays the health and state of the PG.
Here is some sample output:
C:\> opctest /?
Version: Release 4.0, Build 04624
Usage: opctest [/f InputFile] [/system SystemName] [/cust Customer]
[/node ICRNode] [/pipe OutputPipe] [/debug] [/stop] [/help] [/?]
Figure 1 shows more detailed output for the status command:
Figure 1—OPCTest status Output
Note: In ICM version 4.1, the Peripheral Gateway Agent (PGAgent) section only displays Connect time for the current active side. In this example, PGAgent on PG5B is the active side. PG5A is idle:
PGAgent LastStateChangeTime ConnectATime Status ConnectBTime Status
SideA P-- 02/01 11:50:23 (3.2 hr) IDLE AGENT IDLE AGENT
SideB PIA 02/01 11:48:54 (3.2 hr) 02/01 11:48:54 (3.2 hr) CONNECTED 02/01 11:48:54 (3.2 hr) CONNECTED
opctest Commands
Type help or ? at the opctest command prompt in order to view a list of available commands.
Some of the opctest commands, such as List_Agents and List_Trunk_Group, require one or more additional command-line switches. Type command name /? in order to obtain the proper syntax. Here is an example:
opctest: la
list_agents: Error for PeripheralID: Missing argument.
opctest: la /?
Usage: list_agents PeripheralID [/agent AgentID] [/state AgentState]
[/group SkillGroupID] [/agpri SkillGroupPriority] [/logout]
[/help] [/?]
opctest: la 5004
SkillGroup= 0 Pri= 0 ----- LoggedOn=23 Avail=0 NotReady=4 Ready=19 TalkingIn=16
TalkingOut=0 TalkingOther=3 WorkRdy=0 WorkNRdy=0 Busy=0
Reserved=0 Hold=0
SkillGroup= 1 Pri= 0 ----- LoggedOn=9 Avail=0 NotReady=1 Ready=8 TalkingIn=7
TalkingOut=0 TalkingOther=1 WorkRdy=0 WorkNRdy=0 Busy=0
Reserved=0 Hold=0
SkillGroup= 2 Pri= 0 ----- LoggedOn=25 Avail=0 NotReady=4 Ready=21 TalkingIn=20
opctest: ltg
list_trunk_groups: Error for PeripheralID: Missing argument.
opctest: ltg 5004
Perph# SkTargetID NTGSkTargetID NumTrunks LastHHU Tracing Ext
ConfigParam
0 5057 5005 -1 02/01 14:30:00 0
1 5058 5005 -1 02/01 14:30:00 0
2 5059 5005 -1 02/01 14:30:00 0
3 5060 5005 -1 02/01 14:30:00 0
4 5061 5005 -1 02/01 14:30:00 0
5 5062 5005 -1 02/01 14:30:00 0
6 5063 5005 -1 02/01 14:30:00 0
7 5064 5005 -1 02/01 14:30:00 0
8 5065 5005 -1 02/01 14:30:00 0
9 5066 5005 -1 02/01 14:30:00 0
10 5067 5005 -1 02/01 14:30:00 0
12 5010 5005 -1 02/01 14:30:00 0
13 5011 5005 -1 02/01 14:30:00 0
14 5068 5005 -1 02/01 14:30:00 0
Debug Information
Issue the debug command in order to enable specific debugging within opctest. The debug command enables debug control by turning up tracing. An enablement of debug control is much more effective than if you adjust the registry or turn up the EMSTraceMask for the OPC process. The enablement of debug control turns up tracing on the part of OPC, for which you need additional tracing. The tracing result displays in the OPC Event Management System (EMS) log files. Use dumplog in order to view the output of the EMS logs. Refer to How to Use the Dumplog Utility for more information.
Here is an example:
opctest: debug /?
Usage: debug_control [/realtime] [/agent] [/halfhour] [/rcmeter] [/routing]
[/skillgroup] [/closedcalls] [/cstaecr] [/cstacer]
[/pimmsg] [/ctimsg] [/rcmsg] [/dmpmsg] [/icmsg] [/opcmsg]
[/mdsmsg] [/pdmsg] [/inrcmsg] [/passthru] [/tpmsg]
[/physctrlr] [/periph] [/all] [/help] [/?]
Issue the debug /routing command if you need to troubleshoot a translation route problem.
When you finish troubleshooting, use the /noall switch in order to turn off all OPC tracing. If you leave tracing turned up, performance problems can result.
Exit and Quit opctest
Issue the quit command in order to exit the opctest utility.
Caution: Use caution when you issue the exit_opc command. This command instructs the OPC process to exit on both sides of the PG, if duplexed. Node Manager forces the process to restart, which then forces a reload of the configuration for the Call Router. All internal peripheral and agent states are flushed. Then, OPC and Peripheral Interface Manager (PIM) relearn the PG and its configuration.
How to Use the Dumplog Utility
Introduction
This document describes the dumplog utility, which allows you to view a specified log file associated with a Cisco Intelligent Contact Management (ICM) process.
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
Readers of this document should be knowledgeable of the following:
Troubleshooting software issues
Cisco ICM
Components Used
The information in this document is based on the software and hardware versions below.
Cisco ICM
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
What Does the Dumplog Utility Do?
The dumplog utility converts binary log files written by Cisco ICM processes into readable format. Once converted, the log file contents can be referenced to gain insight into ICM operation. Typically, dumplog is used as a troubleshooting tool, but it can be educational as well.
The dumplog utility can be invoked from either a command prompt directly on the ICM server, or from a Telnet session to the ICM server.
Note: The following examples assume that ICM is installed on the C drive. If the ICM is installed on a different drive, then directory locations will change accordingly.
For server naming conventions used in this document please see ICM Server Naming Conventions.
How to Get to the Logfile Directory
The path to the Cisco ICM logfile directory is\icr\customer instance name\node name.
Where is the drive where ICM is installed, for example, C, D, or E.
For example, if you consider that Cisco ICM Call Router is installed on the C drive, the logfile directory on geocscortra would be located at: c:\icm\csco\rtra\logfiles.
Note: The following can be used as a shortcut to the logfiles directory: c:\>cdlog .
Usage
Below are command line options for the dumplog utility. They can help you solve problems by allowing you to view Cisco ICM log files within a specific time period. The time period is definable using the /bd, /bt, /ed, and /et switches. The user can also search for a specific string to further isolate and troubleshoot questionable ICM behavior.
This information can also be found in the "Cisco Intelligent Call Router Administrator Guide."
dumplog [ProcessName(s)] [/dir Dirs] [/if InputFile] [/o]
[/of OutputFile]
[/c] [/bd BeginDate(mm/dd/yyyy)] [/bt BeginTime(hh:mm:ss)]
[/ed EndDate(mm/dd/yyyy)] [/et EndTime(hh:mm:ss)] [/hr HoursBack]
[/all] [/last] [/prev] [bin] [/m MatchString] [/x ExcludeString] [/ms] [/debug]
[/help] [?]
Parameter Descriptions
ProcessName(s)
The command dumps the current day log for this process, unless you specify different dates or times with other arguments.
[/dir Dirs]
Directory specifies the location of the log files for any processes listed on the command line after the /dir switch. If no /dir switch is used, the current directory is used by default.
[/if]
InputFile specifies a specific .ems file to dump. The /if token is optional. If you specify an input file, the /bd, /bt, /ed, /et, /hr, and /all arguments are ignored.
/o
Writes output to a text file in the \logfiles directory. The filename is formed by adding the .txt suffix to the specified process prefix or input file name (without the .ems suffix). The file is written to the current directory.
/of
OutputFile specifies an output text file; for example, c:\temp\mylog.txt.
/c
Specifies continuous output. The command does not exit after reaching the end of the log. Instead, it waits and writes any further entries that appear in the log.
/bd
BeginDate(mm/dd/yyyy) specifies the begin date. If used with /bt, this specifies a range of dates. Otherwise, dumplog dumps events for only the specified date.
/bt
BeginTime(hh:mm:ss) specifies the begin time. Use with /et to specify a range of time.
/ed
EndDate(mm/dd/yyyy) specifies the end date. Use with /bd to specify a range of days.
/et
EndTime(hh:mm:ss) specifies the end time. Use with /bt to specify a range of time.
/hr
HoursBack specifies a number of hours back from the current time.
/all
Displays all information from the specified process log files.
/last
Displays information from the most recent log file for the process.
/prev
Displays information from the next to last log file for the process.
/m
MatchString displays only events that contain a match for the specified string.
/x
ExcludeString displays only events that do not contain a match for the specified string.
[/ms]
Displays milliseconds in time stamps.
[/mc]
Use multiple colors when dumping merged logs. Each process is given a different color. You must specify either a ProcessPrefix or an InputFile. If you give only a ProcessPrefix value (for example, rtr, nm, or lgr), dumplog displays the current day log for that process by default.
Note: To view redirected log files using Microsoft Notepad, save the log file to a text file (using the dumplog /of argument), and open the text file from the command prompt by issuing the: notepad filename command.
Sample Dumplog Usage
The following example shows the dumping of the rtr log file on the router from the beginning of April 29, 1999 until April 30, 1999. It outputs to a log file called rtr.txt. The file rtr.txt can now be viewed using a standard text editor such as Notepad.
c:\icm\csco\rtra\logfiles dumplog rtr /bd 04/29/1999 /ed 04/30/1999 /o
The following command dumps the pgag log file from a peripheral gateway (PG) beginning at the last time a new log file was open for output.
c:\icm\csco\rtra\logfiles dumplog pgag /last
This document describes the dumplog utility, which allows you to view a specified log file associated with a Cisco Intelligent Contact Management (ICM) process.
Before You Begin
Conventions
For more information on document conventions, see the Cisco Technical Tips Conventions.
Prerequisites
Readers of this document should be knowledgeable of the following:
Troubleshooting software issues
Cisco ICM
Components Used
The information in this document is based on the software and hardware versions below.
Cisco ICM
The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If you are working in a live network, ensure that you understand the potential impact of any command before using it.
What Does the Dumplog Utility Do?
The dumplog utility converts binary log files written by Cisco ICM processes into readable format. Once converted, the log file contents can be referenced to gain insight into ICM operation. Typically, dumplog is used as a troubleshooting tool, but it can be educational as well.
The dumplog utility can be invoked from either a command prompt directly on the ICM server, or from a Telnet session to the ICM server.
Note: The following examples assume that ICM is installed on the C drive. If the ICM is installed on a different drive, then directory locations will change accordingly.
For server naming conventions used in this document please see ICM Server Naming Conventions.
How to Get to the Logfile Directory
The path to the Cisco ICM logfile directory is
Where
For example, if you consider that Cisco ICM Call Router is installed on the C drive, the logfile directory on geocscortra would be located at: c:\icm\csco\rtra\logfiles.
Note: The following can be used as a shortcut to the logfiles directory: c:\>cdlog
Usage
Below are command line options for the dumplog utility. They can help you solve problems by allowing you to view Cisco ICM log files within a specific time period. The time period is definable using the /bd, /bt, /ed, and /et switches. The user can also search for a specific string to further isolate and troubleshoot questionable ICM behavior.
This information can also be found in the "Cisco Intelligent Call Router Administrator Guide."
dumplog [ProcessName(s)] [/dir Dirs] [/if InputFile] [/o]
[/of OutputFile]
[/c] [/bd BeginDate(mm/dd/yyyy)] [/bt BeginTime(hh:mm:ss)]
[/ed EndDate(mm/dd/yyyy)] [/et EndTime(hh:mm:ss)] [/hr HoursBack]
[/all] [/last] [/prev] [bin] [/m MatchString] [/x ExcludeString] [/ms] [/debug]
[/help] [?]
Parameter Descriptions
ProcessName(s)
The command dumps the current day log for this process, unless you specify different dates or times with other arguments.
[/dir Dirs]
Directory specifies the location of the log files for any processes listed on the command line after the /dir switch. If no /dir switch is used, the current directory is used by default.
[/if]
InputFile specifies a specific .ems file to dump. The /if token is optional. If you specify an input file, the /bd, /bt, /ed, /et, /hr, and /all arguments are ignored.
/o
Writes output to a text file in the \logfiles directory. The filename is formed by adding the .txt suffix to the specified process prefix or input file name (without the .ems suffix). The file is written to the current directory.
/of
OutputFile specifies an output text file; for example, c:\temp\mylog.txt.
/c
Specifies continuous output. The command does not exit after reaching the end of the log. Instead, it waits and writes any further entries that appear in the log.
/bd
BeginDate(mm/dd/yyyy) specifies the begin date. If used with /bt, this specifies a range of dates. Otherwise, dumplog dumps events for only the specified date.
/bt
BeginTime(hh:mm:ss) specifies the begin time. Use with /et to specify a range of time.
/ed
EndDate(mm/dd/yyyy) specifies the end date. Use with /bd to specify a range of days.
/et
EndTime(hh:mm:ss) specifies the end time. Use with /bt to specify a range of time.
/hr
HoursBack specifies a number of hours back from the current time.
/all
Displays all information from the specified process log files.
/last
Displays information from the most recent log file for the process.
/prev
Displays information from the next to last log file for the process.
/m
MatchString displays only events that contain a match for the specified string.
/x
ExcludeString displays only events that do not contain a match for the specified string.
[/ms]
Displays milliseconds in time stamps.
[/mc]
Use multiple colors when dumping merged logs. Each process is given a different color. You must specify either a ProcessPrefix or an InputFile. If you give only a ProcessPrefix value (for example, rtr, nm, or lgr), dumplog displays the current day log for that process by default.
Note: To view redirected log files using Microsoft Notepad, save the log file to a text file (using the dumplog /of argument), and open the text file from the command prompt by issuing the: notepad filename command.
Sample Dumplog Usage
The following example shows the dumping of the rtr log file on the router from the beginning of April 29, 1999 until April 30, 1999. It outputs to a log file called rtr.txt. The file rtr.txt can now be viewed using a standard text editor such as Notepad.
c:\icm\csco\rtra\logfiles dumplog rtr /bd 04/29/1999 /ed 04/30/1999 /o
The following command dumps the pgag log file from a peripheral gateway (PG) beginning at the last time a new log file was open for output.
c:\icm\csco\rtra\logfiles dumplog pgag /last
Protocols-Port-Numbers
What is Port number ?
Port number is part of the addressing information used to identify the senders and receivers of messages. Port numbers are most commonly used with TCP/IP connections. Home network routers and computer software work with ports and sometimes allow you to configure port number settings. These port numbers allow different applications on the same computer to share network resources simultaneously. Port number is a 16 bit binary number in the TCP. Therefore the port number is in the range of 0-65535.The port numbers are divided into three ranges.
1.Well Known ports
2.Registered Ports
3.Dynamic Ports/Ephemeral ports
How Port Numbers Work ?
Port numbers are associated with network addresses. For example, in TCP/IP networking, both TCP and UDP utilize their own set of ports that work together with IP addresses.
Port numbers work like telephone extensions. Just as a business telephone switchboard can use a main phone number and assign each employee and extension number (like x100, x101, etc.), so a computer has a main address and a set of port numbers to handle incoming and outgoing connections.
In both TCP and UDP, port numbers start at 0 and go up to 65535. Numbers in the lower ranges are dedicated to common Internet protocols.
When You May Need to Take Action with Port Numbers:
Port numbers are typically processed by network hardware and software automatically. Normally you will not see them while casually using a network nor need to take any action involving them. However, in these special cases you can work with network port numbers:
* Network administrators may need to set up port forwarding to allow the port numbers of specific applications to pass through a firewall. On home networks, broadband routers support port forwarding on their configuration screens.
* Network programmers sometimes need to specify port numbers in their code, such as in socket programming.
* Sometimes, a Web site URL will require a specific TCP port number be included. For example, http://localhost:8080/ uses TCP port 8080. Again, this is more usually seen in software development environments than on the Internet.
Protocols port numbers:
Port number is part of the addressing information used to identify the senders and receivers of messages. Port numbers are most commonly used with TCP/IP connections. Home network routers and computer software work with ports and sometimes allow you to configure port number settings. These port numbers allow different applications on the same computer to share network resources simultaneously. Port number is a 16 bit binary number in the TCP. Therefore the port number is in the range of 0-65535.The port numbers are divided into three ranges.
1.Well Known ports
2.Registered Ports
3.Dynamic Ports/Ephemeral ports
How Port Numbers Work ?
Port numbers are associated with network addresses. For example, in TCP/IP networking, both TCP and UDP utilize their own set of ports that work together with IP addresses.
Port numbers work like telephone extensions. Just as a business telephone switchboard can use a main phone number and assign each employee and extension number (like x100, x101, etc.), so a computer has a main address and a set of port numbers to handle incoming and outgoing connections.
In both TCP and UDP, port numbers start at 0 and go up to 65535. Numbers in the lower ranges are dedicated to common Internet protocols.
When You May Need to Take Action with Port Numbers:
Port numbers are typically processed by network hardware and software automatically. Normally you will not see them while casually using a network nor need to take any action involving them. However, in these special cases you can work with network port numbers:
* Network administrators may need to set up port forwarding to allow the port numbers of specific applications to pass through a firewall. On home networks, broadband routers support port forwarding on their configuration screens.
* Network programmers sometimes need to specify port numbers in their code, such as in socket programming.
* Sometimes, a Web site URL will require a specific TCP port number be included. For example, http://localhost:8080/ uses TCP port 8080. Again, this is more usually seen in software development environments than on the Internet.
Protocols port numbers:
