F REQUENTLY A SKED Q UESTION - Snom

More documents

Recommendations

Info

[ F R E Q U E N T L Y A S K E D Q U E S T I O N ] sip_port_number: The SIP port number. nat_proxy: The address of the NAT gateway save_registration: True or false if the registration should be saved. hostname: The list of the hostnames. config_file: The name of the config file. min_regtime, max_regtime: Minimum and maximum registration time. default_q: The default q value. log_register: True or false if REGISTER should go into the SIP message trace. seqfork_delay: The delay for sequential forking. reg_dir: The directory for storing the registrations. log_filename: The filename for logging. log_level: The log level. max_forwards: The maximum number of SIP message forwards. tcp_threshold: The TCP threshold. retry_t1: The retry timeout T1. timeout_408: The timeout value for responding with 408 No Response. call_log_length: The length of the call log. auth_realm: The realm for authentication. force_authorization: True or false if authorization should be forced. auth_exception: The exception pattern for the authentication. html_port_number: The number for the http port. pw_pass1, pw_pass2: The password for the web interface (including confirmation). pw_user: The username for the web interface. allow_pattern: The allow pattern in encoded form. license_code: The license code. error_info: A pattern for generating the error-information headers. reject_nat_register: True or false if NAT registrations should be rejected. no_loose_routing: True or false if loose routing should be turned off. no_route_on_record_route: True or false if no route should be carried out if record- route is already present. callog_filename: The name of the call log file. dirty_host_ttl: The time to live to dirty host detections. welcome_event: The name of the welcome event. welcome_type: The type of the welcome event. welcome_file: The file for the welcome event. welcome_method: The method used for the welcome event (MESSAGE or NOTIFY). no_tags_on_18x: True or false if tags in 18x codes should be removed. Posting to the media server You should keep as little database information as possible on the media server. The newer versions of the media server allow for example the automatic setup of mailbox accounts, which reduces the need for automatic access to the media server. However, if you need to post to the media server, you can do this in the same way as posting to the 2.2x proxy. The media server does not have the concept of a domain and uses basic authentication for checking the user credentials. For example, if you want to set up a new calling card account, you would use “curl -u user:pass -d savecc=save -d cc_account=cc -d cc_number=1234567890 -d cc_code=1234 -d cc_credit=1000 mediaserver.com:8080 >/ dev/null” Security Currently, the proxy uses only plain http to exchange the data. Future releases will allow privacy by using https as transport layers. 4 snom technology AG
Europe & ROW: snom technology AG Pascalstr. 10B 10587 Berlin, Germany Phone: +49 (30) 39833-0 mailto:info@snom.de http://www.snom.com sip:info@snom.com © 2003 snom technology AG All rights reserved. USA and Americas: snom USA Representation ABP International, Inc. 1203 Crestside Dr. Coppell, Texas 75019, USA Phone: +1-972-831-0280 mailto:usa@snom.de sip:usa@snom.com India and SAARC: snom technology (India) Pvt Ltd. No. 417, International Trade Tower Nehru Place, New Delhi-110019 Phone: +91 11 26234097 Fax: +91 11 26234079 http://www.snomindia.com mailto:info@snomindia.com sip:india@snom.com
Page 1 and 2: F REQUENTLY A SKED Q UESTION Contro
Page 3: This function enables a user accoun

F REQUENTLY A SKED Q UESTION - Snom

Create successful ePaper yourself

Delete template?

Save as template?