BlinkenArea - GitList
Repositories
Blog
Wiki
Blinker
Code
Commits
Branches
Tags
Search
Tree:
6c1426a
Branches
Tags
master
Blinker
doc
sipphone.html
implement SIP
Stefan Schuermans
commited
6c1426a
at 2019-05-04 14:47:32
sipphone.html
Blame
History
Raw
<html> <head> <title>Blinker - SIP Phone Connector</title> </head> <body> <h1>Blinker - SIP Phone Connector</h1> <p> The SIP phone connector module acts as SIP client and provides an interface to the internal operator connections. Each module instance is a separate SIP client and can handle a single call at a time. The incoming calls are connected to an internal operator connector. Received DTMF tones are delivered to the operator connection. Sound play requests received over the operator connection are processed based on <code>*.wav</code> files in the <code>sounds</code> subdirectory, i.e., the sounds are played on the SIP connection if the file is found. </p> <h2>Configuration</h2> <p> The configuration of the SIP phone connector module with name <code>NAME</code> is located in the <code>sipphones/NAME</code> subdirectory. </p> <h3>SIP Server Name</h3> <p> The file <code>server</code> contains the host name of the SIP server. <br> The SIP phone connector module will register with this server and accept incoming calls (or reject them if another call is already in progress). </p> <h3>SIP User Name</h3> <p> The file <code>username</code> contains the user name for the SIP connection. It is used for authentication and to form the SIP identity by prepending it to the SIP server name (separated <code>@</code>). </p> <h3>SIP Password</h3> <p> The file <code>password</code> contains the password for the SIP authentication. Please note that those files are not present in the example configuration. </p> <h3>Target Operator Connection Slot</h3> <p> The file <code>target</code> contains the name of the operator interface to contact via an operator connection if the extension is called. </p> <h3>Sound Directory</h3> <p> The <code>*.wav</code> files used to process sound playback requests received on the internal operator connection are read from the <code>sounds</code> subdirectory. The file name extension <code>.wav</code> is automatically appended to the name of the requested sound. This means if a sound play request for <code>SOUND</code> is received, the file <code>sounds/SOUND.wav</code> if opened. If it exists, it is played in the SIP connection. </p> <h3>Log Files</h3> <p> Log information from the SIP library is written to the file <code>sip.log</code>. When the file reaches 10000 lines, a new log file is started (using the same file name). The previous log file is kept under the name <code>sip.log.prev</code>. </p> </body> </html>
