snom 4S Product Overview December 2003

V1.0 2 User Web Interface Proxy is controlled via the web interface User Mode –Available to end users –May see call lists, change preferences Domain Administrator mode –Available to domain administrators –May change dial plans, set up users, … Proxy Administrator mode –May set up domains –Set up licensing, port binding, fundamental routing decisions, …

V1.0 3 Multi Language Support Multi Domain Support Multi User Support HTTPS

V1.0 4 Mobility Support Click 2 Dial Call History

V1.0 5 Speed Dial Personal Address Book Asian Character Support Click 2 Dial Personal Preferences

V1.0 6 SIP Proxy/Registrar Functionality Request forking –According to RFC3261 –TCP, UDP transport layer –TLS will come soon Server location –According to RFC3262 (DNS NAPTR, SRV, A) Registration Challenging –Digest authentication

V1.0 7 Multiple Domain Hosting Each domain may contain –Own user database –Own administrator –Own dial plan –Own logging “Virtual” proxy –Renting proxy space Only one SIP port is used

V1.0 8 Scripting Powerful way of programming the proxy –Available on domain level –Override the default implementation Specific functions can be overwritten –Thing which cannot be setup easily using the web interface Example: Determine when to challenge a request challenge() { return parse_user($from) == “123”; }

V1.0 9 Distinctive Ringing Users may select their ring tone in the web interface –Proxy supplies ring tone via web interface –Tone depends on who is called –Uses Alert-Info header from RFC3261

V Address Books and Call Lists Most of the numbers have been dialed before! Address books on different levels –User: Per account –Group: Definable group members –Domain: Implicitly via the registrar Import Via CSV –Support for UTF-8/SJIS (Asian Characters) Proxy automatically keeps call lists –Are stored along with the account information –Can be accessed from the user interface –Missed calls may be sent via Address books and Call Lists are subject to number guessing –Proxy automatically proposes completion of user input –snom proprietary SIP/HTTP extension

V Redundancy Support Support for hot stand-by Application-layer support –State replication between proxies via SIP messages –Switch via DNS SRV Keep-Alive messages between proxies –Trigger changing of DNS SRV entries (zone update)

V Multiple Platform Windows –32-bit versions Linux –Support for SuSE and RedHat distributions

V Voic Anonymous/personal greeting User identification, PIN code management SIP message waiting indication (MWI) Instant Mailbox –Automatic setup of mailbox account –Simplifies installation of mid-size corporations notify –New messages are sent as s with compressed audio attachments

V Auto Attendant, Conferencing Auto Attendant –Personalized Greeting –Default target Conference Bridge –Optional PIN code authentication –VAD on conferences with more than 5 participants (echo avoidance)

V Queues and IVR Dialogs Queues name the number of participants that are waiting in line –Background music on hold with fade –Pickup mechanism transparent IVR Dialogs allow DTMF navigation to final destination –Can be cascaded to allow complex scenarios –Stay inside the media server (no REFER) –Final destination may be any SIP URL

V MOH, Error Explanation Music on Hold –Loadable music –User can select melody with DTMF Error Explanation –Standard announcements –Early Media (no pick up) File Location Credentials One Melody for Every Key

V GRUU support GRUU = Globally Routable User-Agent URI –Hides IP identity to other party –Enables proper attended transfer through the proxy –Allows usage of TCP connections for solving SIP NAT problems

V Click to Call Used in several places in the proxy web interface –Address books –Call lists Convenient way of initiating a call –User just lifts the handset (security confirmation) –The registered phone will receive the request

V Initiating a Conference No conference scheduling –Very simple usage –Simple web interface setup Can also be used for call back service –“2-way conference” –Cost saving potential when on the road

V Integrated STUN Server STUN server solves NAT problems –NAT is a common way to create private networks –STUN is a “mirror in the public Internet” No 2nd IP address required –STUN server generates artificial response with different IP address –Very simple setup STUN server operates on SIP port –Makes STUN possible even for symmetrical NAT!

V ENUM Support ENUM uses telephone numbers to identity services –SIP, H323, or WWW are just examples –Users can keep their existing telephone numbers User Agents don’t have to support ENUM –Proxy treats ENUM as redirection –But: Security concerns when ENUM is abused Its better to have ENUM support on the user agents –snom phones support ENUM

V Call Pickup Support Call pickup by dialing feature number (e.g. *11) –Calling party is integrated into forking group –No backward compatibility problems with legacy gateways etc. –Phones that support Replaces header can perform pickup –Other pickups are blocked Call Pickup from function key –Proxy processes replaces header and puts picking party into the forking group –Other pickups are blocked

V Dialog Agent Indicating user agent status (ringing, talking, terminated) –Typical application is LED –Also switchboard and other PC-based applications are possible Makes “stupid” endpoints dialog-aware –TA, softphones, etc. –Reduction of traffic though the proxy

V Presence Agent Similar to dialog agent –Indicates the presence state of a user agent –Compatible to SIMPLE standard According to the SIP model necessary for call completion (auto redial) –SIP user agents must indicate their presence state –snom phones include this feature Also suitable for general presence indication –Softphones, etc.

V Prepaid Calling Cards Scalable solution –Stateless media server –Integration with web tools and database –Large number of calling cards possible Announcements –Per minute –Before calling cards ends Real Time Billing Information –IM about the charge status of the card IVR for querying the status, entering destination number etc. Gateway is not exposed to user (Security)

V CDR Generation Simple CDR file –Append records to file –Very simple to process SIP NOTIFY –XML attachment with CDR –Can be made scalable using DNS SRV and database Open Settlement Protocol –Authentication records –Accounting records –Integrated web client –TLS and S/MIME support RADIUS –User-based authentication with external database –Accounting

V Controlling Support Accumulated Call Data –Simple setup –Easy import to spreadsheet tools Billing groups –Departments, cost/profit centers –Wildcard pattern definition Detailed records are not stored –Legal requirement in some countries –Three month history

© 2003 snom technology Aktiengesellschaft Written by: Dr. Christian Stredicke Version: 1.0 The author has made his best effort to prepare this document. The content is based upon latest information whenever possible. The author makes no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accept no liability of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any losses or damages of any kind caused or alleged to be caused directly or indirectly from this document. For more information, mail Pascalstr. 10B, Berlin, Germany.