📄 ch04s06.html
字号:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!-- saved from url=(0077)http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s06.html -->
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?><HTML
xmlns="http://www.w3.org/1999/xhtml"><HEAD><TITLE>4.6.燬etting up SIP services</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1"><LINK
href="ch04s06.files/terena.css" type=text/css rel=stylesheet>
<META content="MSHTML 6.00.2800.1106" name=GENERATOR><LINK
title="IP Telephony Cookbook" href="index.html" rel=home><LINK
title="Chapter 4. Setting up basic services" href="ch04.html"
rel=up><LINK title="4.5. Setting up H.323 services" href="ch04s05.html"
rel=previous><LINK title="4.7. Firewalls and NAT" href="ch04s07.html"
rel=next><LINK title=Chapter 1. Introduction href="ch01.html"
rel=chapter><LINK title="Chapter 2. Technology Background"
href="ch02.html" rel=chapter><LINK
title="Chapter 3. IP Telephony Scenarios" href="ch03.html"
rel=chapter><LINK title="Chapter 4. Setting up basic services"
href="ch04.html" rel=chapter><LINK
title="Chapter 5. Setting up Advanced Services" href="ch05.html"
rel=chapter><LINK title="Chapter 6. Setting up Value-Added Services"
href="ch06.html" rel=chapter><LINK
title="Chapter 7. Global telephony integration" href="ch07.html"
rel=chapter><LINK title="Chapter 8. Regulatory / Legal considerations"
href="ch08.html" rel=chapter><LINK
title="Appendix A. European IP Telephony Projects" href="apa.html"
rel=appendix><LINK title="Appendix B. IP Telephony Hardware/Software"
href="apb.html" rel=appendix><LINK title=Glossary href="go01.html"
rel=glossary><LINK title="4.6.1. Operation of SIP Servers"
href="ch04s06.html#d0e3782" rel=subsection><LINK
title="4.6.2. SIP Express Router" href="ch04s06.html#sec-ser"
rel=subsection><LINK title=4.6.3. Asterisk href="ch04s06.html#d0e4611"
rel=subsection><LINK title=4.6.4. VOCAL href="ch04s06.html#d0e4744"
rel=subsection></HEAD>
<BODY>
<DIV class=navheader>
<TABLE width="100%" summary="Navigation header">
<TBODY>
<TR>
<TH align=middle colSpan=3>4.6. Setting up SIP services</TH></TR>
<TR>
<TD align=left width="20%"><A accessKey=p
href="http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s05.html">Prev</A> </TD>
<TH align=middle width="60%">Chapter 4. Setting up basic
services</TH>
<TD align=right width="20%"> <A accessKey=n
href="http://www.informatik.uni-bremen.de/~prelle/terena/cookbook/main/ch04s07.html">Next</A></TD></TR></TBODY></TABLE></DIV>
<DIV class=sect1 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H2 class=title style="CLEAR: both"><A
id=sec-setting-sip-services>4.6. Setting up SIP services</H2></DIV></DIV>
<DIV></DIV>
<DIV class=sect2 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H3 class=title><A id=d0e3782>4.6.1. Operation of <SPAN
class=acronym>SIP</SPAN> Servers</H3></DIV></DIV>
<DIV></DIV>
<DIV class=sect3 lang=en>
<DIV class=titlepage>
<DIV>
<DIV>
<H4 class=title><A id=operationalpractices>4.6.1.1. Recommended Operational
Practices</H4></DIV></DIV>
<DIV></DIV>
<P>Operation of a <SPAN class=acronym>SIP</SPAN> server is not always an easy
task. Server administrators face many challenges of broken or misconfigured user
agents, network and host failures, hostile attacks and other stress-makers. All
such situations may lead to an operational failure. It is sometimes very
difficult to figure out the root reason of a failure, particularly in a
distributed environment with many <SPAN class=acronym>SIP</SPAN> components
involved. In this section, we share some of our practices and refer to tools
which have proven to make the life of administrators easier. </P>
<DIV class=qandaset>
<TABLE summary="Q and A Set" border=0>
<COLGROUP>
<COL align=left width="1%">
<TBODY>
<TR class=question>
<TD vAlign=top align=left><A id=d0e3800><A id=d0e3801><B>4.6.1.1.1.
</B></A></TD>
<TD vAlign=top align=left>
<P>Message logging. </P></TD></TR>
<TR class=answer>
<TD vAlign=top align=left><B></B></TD>
<TD vAlign=top align=left>
<P>Frequently, operational errors are discovered or reported with a delay.
Users frustrated by an error frequently approach administrators and scream
"even though my <SPAN class=acronym>SIP</SPAN> requests were absolutely OK
yesterday, they were mistakenly denied by your server". If administrators
do not record all <SPAN class=acronym>SIP</SPAN> traffic at their site,
they will not be able to identify the reason of the problem. We thus
recommend that site operators record all messages passing their site and
keep them stored for some period of time. They may use utilities such as
<SPAN class=application>ngrep </SPAN>or <SPAN class=application>tcpdump
</SPAN>. </P></TD></TR>
<TR class=question>
<TD vAlign=top align=left><A id=d0e3819><A id=d0e3820><B>4.6.1.1.2.
</B></A></TD>
<TD vAlign=top align=left>
<P>Real-time Traffic Watching. </P></TD></TR>
<TR class=answer>
<TD vAlign=top align=left><B></B></TD>
<TD vAlign=top align=left>
<P>Looking at <SPAN class=acronym>SIP</SPAN> messages in real-time may
help to gain understanding of problems. Though there are commercial tools
available, using a simple, text-oriented tool such as <SPAN
class=application>ngrep</SPAN> is sufficient for the job, thanks to <SPAN
class=acronym>SIP</SPAN>'s textual nature. </P>
<DIV class=example><A id=usingngrep>
<P class=title><B>Example 4.1. Using <SPAN
class=application>ngrep</SPAN> </B></P>
<P>In this example, all messages at port 5060 which include the string
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -