|
Home > Archive > CCNP > November 2004 > port numbers
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| carpediumtoday 2004-11-25, 2:26 am |
| How do you know or how would you find out what the port numbers used would be for a certain application or technology? For example, if I wanted to run voice over ip over a frame-relay site, and wanted to give a certain higher priority to that traffic, how would I know what ports voip uses? Or even a application, say if I wanted to run traffic for a certain application to have high priority? | |
| carpediumtoday 2004-11-25, 12:54 pm |
| I found that during my "search" before I posted this question. I was hoping to find the answer to my question with a little better explanation. My example that I was trying to look up was voice over ip, in particular. | |
| smrkdown 2004-11-25, 6:43 pm |
| VoIP is a broad category under which fall many standards, technologies, and applications and it depends on the specific implementation as to what port number is used. There is no "VoIP" port. The other applications you mentioned may use default ports or may not. Just because a default port exists for an application (ex. ssh - 22) doesn't mean that that application must use that port. Sometimes for security purposes, administrators will run services on an alternate port instead of the default. Also, if your product/application is proprietary, you might want to refer to its documentation. Also, depending on what equipment and software you're running, you can use characteristics other than port number to provide QOS. | |
| carpediumtoday 2004-11-26, 1:47 am |
| Thank you smrkdown, that is very helpful. I think I can use that information to help me decide what do do in upcoming situations. | |
| smrkdown 2004-11-26, 2:16 am |
| You're welcome. I'm working on the CCNP switching exam right now, but I haven't gotten to the QOS chapters in my materials. If I had, I could probably have offer better advice. | |
| carpediumtoday 2004-11-26, 12:32 pm |
| I have done the switching portion, and I probably dont remember much about what the book (cisco press) said about qos. I can tell you this for sure, that while alot of what I learned from the cisco book is useful, I have found that there is alot of real life that the book doesnt cover. As far a qos goes, I dont recall ever learning much about it, maybe just the very basics. But again, I believe that the books that we buy only give you the basics and really dont tie everything together in a proper manner. I have almost decided to write books myself on certain topics within the ccnp realm. I think it is like alot of things, you can go to school, read a book, whatever, but real life situations are very different that a controled environment. There is no real learning like real life learning, even in the cisco realm. Sure, just as waldoishere stated earlier, why dont we go look it up on the internet??? He is right in that that is what any good tech should do, but again, after we do that and exhaust all resources, sometimes the best advice and learning just comes from people who have experienced it. | |
| sandy7000 2004-11-28, 1:11 pm |
| quote:
How do you know or how would you find out what the port numbers used would be for a certain application or technology? For example, if I wanted to run voice over ip over a frame-relay site, and wanted to give a certain higher priority to that traffic, how would I know what ports voip uses? Or even a application, say if I wanted to run traffic for a certain application to have high priority?
Doesn't Server 2K3 have a new netstat option to display TCP port ownership?
Maybe TCP isn't the right protocol to answer this question. You probably want the router's ownership, not the server. | |
| 0zzie 2004-11-29, 12:56 am |
| netstat -an on any widoze or linux
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1439 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5679 0.0.0.0:0 LISTENING | |
| sandy7000 2004-11-29, 1:26 am |
| From the Microsoft book, "Introducing MS Windows Server 2K3" pg. 138
"New Netstat option to display TCP port ownership. A new option is added to the Netstat tool that allows you to display active TCP connections & that includes Process Identifier or PID for each connection. You can find the application based on the PID on the Processes tab in (Task Manager). By default, the PID is not displayed in taskmgr. To configure the Windows Task Manager to display the PID, click View>select columns>PID in the list of columns to display, then ok."
The book came from Microsoft, so I guess that means it's been done already by Linux.
They do it to me also, Carpe. Skin thicker than a gator's hide helps, I guess. Not very feminine, though.
Points to Ozzie! He wins. | |
| ZacDogg 2004-11-29, 12:15 pm |
| To answer you original question about what ports VoIP uses, the answer as previously stated is many. I am not a VoIP expert, but I know it can use at least the following protocols:
SIP
SCCP
MGCP
H.323
SGCP
RTP
I am sure there are more and am not willing to find look up which are UDP and TCP and what port. You can do that. 
Zac |
|
|
|
|