ÿþ<html> <head> <meta http-equiv=Content-Type content="text/html; charset=unicode"> <meta name=Generator content="Microsoft Word 12 (filtered)"> <style> <!-- DIV[class="Part"] { text-align:left; margin-bottom:0px; margin-top:0px; margin-right:0px; text-indent:0px; direction:ltr } DIV[class="Sect"] { text-align:left; margin-bottom:0px; margin-top:0px; margin-right:0px; text-indent:0px; direction:ltr } table {display:table; float:none;} /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} h3 {mso-style-link:"Überschrift 3 Zchn"; margin-top:0cm; margin-right:0cm; margin-bottom:3.75pt; margin-left:0cm; line-height:18.0pt; font-size:13.5pt; font-family:"Times New Roman","serif"; color:black; font-weight:bold;} h4 {mso-style-link:"Überschrift 4 Zchn"; margin-top:0cm; margin-right:0cm; margin-bottom:3.75pt; margin-left:0cm; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black; font-weight:bold;} h5 {mso-style-link:"Überschrift 5 Zchn"; margin:0cm; margin-bottom:.0001pt; line-height:12.75pt; font-size:10.0pt; font-family:"Times New Roman","serif"; color:black; font-weight:bold;} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} p {margin:0cm; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst {margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle {margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:36.0pt; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif"; color:black;} span.berschrift3Zchn {mso-style-name:"Überschrift 3 Zchn"; mso-style-link:"Überschrift 3"; font-family:"Cambria","serif"; color:#4F81BD; font-weight:bold;} span.berschrift4Zchn {mso-style-name:"Überschrift 4 Zchn"; mso-style-link:"Überschrift 4"; font-family:"Cambria","serif"; color:#4F81BD; font-weight:bold; font-style:italic;} span.berschrift5Zchn {mso-style-name:"Überschrift 5 Zchn"; mso-style-link:"Überschrift 5"; font-family:"Cambria","serif"; color:#243F60;} .MsoChpDefault {font-size:10.0pt;} @page Section1 {size:595.3pt 841.9pt; margin:70.85pt 70.85pt 2.0cm 70.85pt;} div.Section1 {page:Section1;} /* List Definitions */ ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} --> </style> <meta name=dc.date content="2009-01-28T13:39:53Z"> <meta name=dc.date.modified content="2009-01-28T13:39:53+01:00"> </head> <body bgcolor=white lang=DE link=blue vlink=purple alink=fushia> <div class=Section1> <p class=MsoNormal><b><span lang=EN-US style='font-size:14.0pt;font-family: "Arial","sans-serif"'>Gigaset VoIP telephones behind various routers with Network Address Translation (NAT) </span></b></p> <p class=MsoNormal><b><span lang=EN-US style='font-size:14.0pt;font-family: "Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>NAT constitutes a basic obstacle to VoIP telephony. Typical error patterns caused by NAT are: </span></p> <p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Absence of speech paths, sometimes partial paths </span></p> <p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Incoming calls not possible </span></p> <p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Outgoing calls unsuccessful </span></p> <p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <div> <p class=MsoNormal><b><span lang=EN-US style='font-family:"Arial","sans-serif"'>Preferred Port- and Router-Configuration in case of NAT Problems </span></b></p> <p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Usually there is no special router configuration required to run Gigaset VoIP phones behind NAT. But if there are error patterns, such as described above, they often could be fixed by selecting exclusive SIP and RTP port numbers in the Gigaset VoIP phone. In some cases it might additionally be necessary to program Port forwarding rules for these ports in the router: </span></p> <p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoListParagraph style='text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Use exclusive Port Numbers for SIP and RTP in the Gigaset VoIP phone: Especially if there are additional VoIP phones in the LAN, it might help to choose port numbers, which are not used by any other host or application in the LAN and which are far away from the default SIP and RTP ports (e.g. random numbers from 1024 up to 49152). You need to know, that RTP protocol uses the preconfigured RTP base port number (e.g. 5004) and the next two even port numbers (e.g. 5006 and 5008). In the latest software releases you can configure a range of RTP ports. As you need to remember these port numbers for router configuration, you could choose numbers, which are quiet similar to the default settings, e.g.: </span></p> <p class=MsoNormal style='text-indent:35.4pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>SIP:      49060                           instead of 5060 </span></p> <p class=MsoNormal style='text-indent:35.4pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>RTP:     49004 (up to 49008 )     instead of 5004 (up to 5008) </span></p> <p class=MsoNormal style='text-indent:35.4pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoNormal style='margin-left:35.4pt'><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Recommended procedure to change SIP and RTP ports: </span></b></p> <p class=MsoListParagraphCxSpFirst style='margin-left:53.4pt;text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Change SIP and RTP ports. </span></p> <p class=MsoListParagraphCxSpLast style='margin-left:53.4pt;text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Wait until active SIP accounts are registered again. </span></p> <p class=MsoNormal style='text-indent:35.4pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><b><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Port forwarding (or Port-mapping) </span></b></p> <p class=MsoListParagraphCxSpLast><span lang=EN-US style='font-size:10.0pt; font-family:"Arial","sans-serif"'>For these port numbers of the Gigaset VoIP phones you need to program port forwarding rules in the router, to ensure, that these port numbers are also you used at the WAN interface with the public IP address. </span></p> <div> <table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=688 style='width:516.15pt;border-collapse:collapse'> <tr style='height:9.75pt'> <td width=644 colspan=6 valign=top style='width:483.0pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>e.g.: </span></p> </td> <td style='border:none;padding:0cm 0cm 0cm 0cm' width=44><p class='MsoNormal'>&nbsp;</td> </tr> <tr style='height:12.75pt'> <td style='border:none;padding:0cm 0cm 0cm 0cm' width=44><p class='MsoNormal'>&nbsp;</td> <td width=117 valign=top style='width:87.75pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:12.75pt'> <p class=MsoNormal align=center style='text-align:center'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Protocol </span></b></p> </td> <td width=118 valign=top style='width:88.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:12.75pt'> <p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>public Port </span></b></p> </td> <td width=123 valign=top style='width:92.25pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:12.75pt'> <p class=MsoNormal align=center style='text-align:center'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>local Port </span></b></p> </td> <td width=286 colspan=3 valign=top style='width:214.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:12.75pt'> <p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Host (IP-address) </span></b></p> </td> </tr> <tr style='height:11.25pt'> <td style='border:none;padding:0cm 0cm 0cm 0cm' width=44><p class='MsoNormal'>&nbsp;</td> <td width=117 valign=top style='width:87.75pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:11.25pt'> <p class=MsoNormal align=center style='text-align:center;line-height:11.25pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>UDP</span></p> </td> <td width=118 valign=top style='width:88.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:11.25pt'> <p class=MsoNormal style='line-height:11.25pt'><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>49060 </span></p> </td> <td width=123 valign=top style='width:92.25pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:11.25pt'> <p class=MsoNormal align=center style='text-align:center;line-height:11.25pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>49060 </span></p> </td> <td width=146 valign=top style='width:109.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:11.25pt'> <p class=MsoNormal style='line-height:11.25pt'><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>192.168.2.10 </span></p> </td> <td width=140 colspan=2 valign=top style='width:105.0pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:11.25pt'> <p class=MsoNormal style='line-height:11.25pt'><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>for SIP </span></p> </td> </tr> <tr style='height:9.75pt'> <td style='border:none;padding:0cm 0cm 0cm 0cm' width=44><p class='MsoNormal'>&nbsp;</td> <td width=117 valign=bottom style='width:87.75pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>UDP</span></p> </td> <td width=118 valign=bottom style='width:88.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>49004-49008 </span></p> </td> <td width=123 valign=bottom style='width:92.25pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>49004-49008 </span></p> </td> <td width=146 valign=bottom style='width:109.5pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>192.168.2.10 </span></p> </td> <td width=140 colspan=2 valign=bottom style='width:105.0pt;padding:2.25pt 2.25pt 2.25pt 2.25pt; height:9.75pt'> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>for RTP </span></p> </td> </tr> <tr height=0> <td width=44 style='border:none'></td> <td width=117 style='border:none'></td> <td width=118 style='border:none'></td> <td width=123 style='border:none'></td> <td width=146 style='border:none'></td> <td width=96 style='border:none'></td> <td width=44 style='border:none'></td> </tr> </table> <p class=MsoNormal style='margin-left:35.4pt'><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>In the latest software releases of Gigaset VoIP phones you can configure a range of RTP ports. Then you also have to program port forwarding rules for this range of RTP ports. To allow for such port forwarding rules, the DHCP settings of the router must ensure, that the Gigaset VoIP phone always gets the same local IP address. </span></p> </div> </div> <div> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>Background Information </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Following you find further details about NAT traversal of VoIP traffic. </span></p> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>STUN </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The STUN protocol is the preferred instrument of Gigaset VoIP telephones for overcoming NAT. And in many cases it is sufficient. If the problems described above arise even though the STUN protocol is activated, the deactivation of the STUN protocol is a useful test for troubleshooting. This measure enables any &quot;helpers&quot; that are available in the router (SIP Application Layer Gateway) or with the provider (SIP Proxy and RTP Proxy) to intervene and support NAT traversal. </span></p> <div> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>symmetric NAT </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>There is a so-called symmetric NAT, on which the STUN protocol does not work adequately. If a Gigaset VoIP phone is connected behind a symmetric NAT, although it can correctly ascertain the public IP address used for the VoIP protocols, it nevertheless cannot ascertain the public port mappings that the NAT will assign to the VoIP protocols. The Gigaset VoIP phone then assumes that the local ports set up for SIP and RTP also correspond to their public mapping. But this is not necessarily the case. The user can make sure that it is, however, with the following options. </span></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Option: Port Forwarding Rules: </span></p> <p class=MsoListParagraphCxSpMiddle><span lang=EN-US style='font-size:10.0pt; font-family:"Arial","sans-serif"'>The user can generally program so-called Port Forwarding Rules in the router, which ensure that the VoIP ports used locally in the Gigaset (e.g. 5060 for SIP and 5004 and ff. for RTP) are mapped on the WAN side to the same port numbers. </span><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>Only the base port can be set up for the RTP port on the Gigaset VoIP phone. Depending on the number of parallel VoIP calls supported, the subsequent even port numbers are used for RTP: 2 for devices that support one VoIP call, 3 for those that support two VoIP calls simultaneously. For example: 5004 is set up as the RTP port. Two parallel VoIP calls are supported. So 5004, 5006 and 5008 are used as RTP ports </span></p> <p class=MsoListParagraphCxSpMiddle><span style='font-size:10.0pt;font-family: "Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Option: Use of exclusive ports for VoIP protocols </span></p> <p class=MsoListParagraphCxSpLast><span lang=EN-US style='font-size:10.0pt; font-family:"Arial","sans-serif"'>The user can set up the VoIP ports used locally in the Gigaset (for SIP and RTP) in such a way that no other subscriber in the LAN can use the same ports. </span><span style='font-size:10.0pt; font-family:"Arial","sans-serif"'>With many routers, although by no means all, the ports are not re-mapped by the NAT in such cases, which means they meet the requirement that the locally set port numbers are also used on the WAN side. </span></p> </div> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span lang=EN-US style='font-family:"Arial","sans-serif"'>Ambiguous Port Numbers within the LAN </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Some NAT implementations have problems with forwarding traffic returning to the LAN to the correct LAN subscriber if multiple LAN subscribers are using the same port numbers for this. So for Gigaset VoIP telephones this behavior results in problems when further subscribers in the LAN, especially VoIP telephones or VoIP clients on connected PCs, are also using the port numbers set up on the Gigaset phone for SIP and port number ranges for RTP. In this case it is necessary to set up in the Gigaset VoIP phone exclusive port numbers (or port number ranges) for SIP and RTP, which no other LAN subscriber uses. It would also be possible to use the option of &quot;random port numbers&quot; for this, if latest firmware release is installed. For random port numbers it is not possible to program port forwarding rules in router. </span></p> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span lang=EN-US style='font-family:"Arial","sans-serif"'>SIP-Application Layer Gateway (SIP-ALG) </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Often there might be SIP-ALGs implemented in routers, which try to correct the effect of network address translation in the SIP protocol. But SIP-ALGs can also be troublesome in certain cases. This can be the case when older implementations modify the SIP protocol in a way that does not comply with RFC3261. It can then be helpful to deactivate a SIP-ALG in the router/gateway (rarely possible) or to circumvent the SIP-ALG. Circumventing the SIP-ALG is sometimes possible by setting up a local SIP server port for the Gigaset VoIP phone that is far removed from the conventional SIP ports (5060, 5062, & ). </span></p> <div> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span lang=EN-US style='font-family:"Arial","sans-serif"'>Gigaset VoIP phones with integrated Router </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Gigaset VoIP phones with integrated Router (CE450 IP R and AM variant) are somewhat different from the other Gigaset VoIP telephones as far as NAT traversal strategy is concerned. Depending on firewall settings, the integrated router implements symmetric NAT. So STUN is not particularly suitable for NAT traversal. Instead, the integrated router implements a SIP Application Layer Gateway which helps the SIP and SDP protocol to overcome the influences of NAT. This works very well as long as the NAT of the integrated router is the only NAT that needs to be overcome (e.g. if the CE450 IP R is connected directly to a DSL modem). Should the CE450 IP R be installed behind another NAT (router/gateway) however, this strategy no longer works. </span></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;</span></p> <p class=MsoNormal><span lang=EN-US style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The following measures are then required: </span></p> <p class=MsoListParagraphCxSpFirst style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Activate STUN </span></p> <p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>2.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Circumvent SIP-ALG in the CE450 IP R router. This is possible by setting up a SIP port outside the range of 5056-5071 in the telephony part of Gigaset CE450 IP R. </span></p> <p class=MsoListParagraphCxSpMiddle style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>3.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Enable Firewall. </span></p> <p class=MsoListParagraphCxSpLast style='text-indent:-18.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>4.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp; </span></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ensure, in accordance with the preceding sections on symmetric NAT, that the ports set up locally in CE450 IP R for SIP and RTP are used on the &quot;public&quot; side (WAN side) of the router in question. For this it may be necessary to program Port Forwarding Rules in both routers (CE450 IP R and upstream router). </span></p> </div> <p class=MsoNormal><b><span style='font-family:"Arial","sans-serif"'>&nbsp;</span></b></p> <p class=MsoNormal><b><span lang=EN-US style='font-family:"Arial","sans-serif"'>Incoming request from other than the preconfigured SIP-Proxy </span></b></p> <p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In order to pass through the NAT, incoming requests to the Gigaset VoIP phone must always be originiated by that communication endpoint, which the Gigaset VoIP phone expects requests to come from, because only to these endpoints a NAT binding is opened and maintained. Usually, this is the preconfigured SIP-Proxy. There are provider, which might send requests to the Gigaset VoIP phones via other SIP servers. Such requests will probably not pass through a NAT. For these providers, it is necessary to open the SIP listen port even at the WAN-interface by programming a port forwarding rule in the router. </span></p> </div> </div> </body> </html>