Snom 4S manual Codec Control, Web Server Integration, Clir Addresses

Page 39

[ S N O M 4 S N A T F I L T E R ]

packet. This setting does not only help you in making the packets shorter, it can also help you to keep some parts of the SIP message secret. For example, you might want to remove P-Asserted-Identity headers from all SIP messages, because you don’t want others to see which identities you already checked.

4.3.15Codec Control

In many environments, you want to exclude codecs from being used, although both communication partners could agree on them. The “Allow only the following codecs” setting lists the codecs (separated by space) that you will allow. If you don’t set anything here, all codecs will be allowed. The codecs must be written in their SDP name, for example “ulaw”, “alaw”, “gsm”, “g729”, “g723”, etc.

This feature can be used, for example, to make sure that only low-rate codecs are being used. The user agents might otherwise agree on ulaw, which might lead to breaking voice if the bandwidth is not suf- ficient for a stream using ulaw.

4.3.16Web Server Integration

The description of the web server integration follows in the next

chapter.

4.3.17CLIR Addresses

The SBC has the possibility to hide the identity of the caller (see description in the following chapter). For this feature it must decide when to hide the identity. If it hides the identity too early, the further processing in the data center will be difficult. Therefore it must make a decision when the request leaves the influence area of the data center.

When the request is sent to a UA that is handled by the NAT Filter, it does perform this step. However, when it is sent to a PSTN or IP-gate- way, it also must hide the identity. The setting Outbound Addresses (for CLIR) lists the IP addresses that also trigger a hiding of the identity. The format for this setting is the same as for the trusted IP addresses.

4.

snom technology AG • 39

Image 39
Contents Snom 4S NAT Filter Admin Manual Snom 4S NAT Filter Version Table of Contents Snmp Overview Applications FeaturesSnom technology AG Overview NAT Filter and SIP ArchitectureNAT Signalling SIP How does NAT work?Symmetrical RTP Classification of User Agents Media RTPRole of the NAT Filter Probing Media PathsNAT Optimizing the Media Path for SymmetricalRegistering SBC BehaviourRTP Relay Snom technology AG NAT Scaling and RedundancyDetecting the right NAT Filter Requirements on User Agents Non NAT-Aware User AgentsSTUN/ICE-Aware User Agents Defining the Maximum Session Time Architecture Windows InstallationInstallation Snom technology AG Installation Snom technology AG Linux Rpm -ihv snomnatf-2.10.*.rpm Installation Port Binding LoggingStandard Port Random Port Logging System SettingsGeneral Outound Proxy Preparing RecoveryControlling Routing Media PortsPort Budgets Media RelayMultiple 2xx Handling Challenging Trusted AddressesMaximum Packet Size Silence Suppression Connection Oriented MediaRemoving Headers Codec Control Web Server IntegrationClir Addresses Register Timeouts Timeout SettingsCall Timeouts Security Settings Snom technology AG Outbound Proxy List Server Log System InformationTrace Call History Current Ports Memory Statistics Currently Handled UAConfiguration Web Server Integration Interface to the Web Server AuthenticationSnom technology AG Web Server Integration Registration Call Initiation Snom technology AG Call Termination Snom technology AG Web Server Integration Setup of the Tools Setup of the SBCOID Available OIDSnom technology AG Snmp Checklist for Installation Checklist for Installation Reader‘s Feedback Snom technology AG All rights reserved