evergreen-admin:sip
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
evergreen-admin:sip [2010/05/06 21:33] – Big title jatzberger | evergreen-admin:sip [2013/02/20 11:42] – The recommended minimum min_spare_servers should be 1. lazar | ||
---|---|---|---|
Line 3: | Line 3: | ||
This is a rough intro to installing the SIP server for Evergreen. | This is a rough intro to installing the SIP server for Evergreen. | ||
- | ===Getting the code=== | + | NOTE: This documentation is also available in the Evergreen documentation at [[http:// |
+ | |||
+ | =====Getting the code===== | ||
+ | Current SIP code lives at http:// | ||
< | < | ||
- | $ cd /opt | + | cd /opt |
- | $ sudo cvs -d: | + | git clone git://git.evergreen-ils.org/ |
- | # when prompted for the CVS password, just hit Enter (sudo password may be req' | + | |
- | $ sudo cvs -z3 -d: | + | |
</ | </ | ||
- | ===Configuring the Server=== | + | =====Configuring the Server===== |
- < | - < | ||
$ cd / | $ cd / | ||
Line 18: | Line 19: | ||
< | < | ||
min_servers=' | min_servers=' | ||
- | min_spare_servers=' | + | min_spare_servers=' |
max_servers=' | max_servers=' | ||
/></ | /></ | ||
- '' | - '' | ||
- | ===Adding SIP users==== | + | =====Adding SIP users===== |
- | - in the < | + | - in the < |
- In Evergreen, create a new profile group called SIP. This group should be a sub-group of Users (not Staff or Patrons). | - In Evergreen, create a new profile group called SIP. This group should be a sub-group of Users (not Staff or Patrons). | ||
< | < | ||
Line 38: | Line 39: | ||
OR use SQL like: | OR use SQL like: | ||
- | < | + | < |
INSERT INTO permission.grp_tree (id, | INSERT INTO permission.grp_tree (id, | ||
VALUES (8, ' | VALUES (8, ' | ||
- | INSERT INTO permission.grp_perm_map (grp, | + | INSERT INTO |
- | VALUES (8,15,0),(8,16,0),(8,17,0),(8,31,0),(8,32,0), | + | |
+ | SELECT | ||
+ | g.id, p.id, 0, FALSE | ||
+ | FROM | ||
+ | permission.grp_tree g, | ||
+ | permission.perm_list p | ||
+ | WHERE | ||
+ | g.name = ' | ||
+ | p.code in ( | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ); | ||
-- VERIFY: | -- VERIFY: | ||
Line 56: | Line 75: | ||
Note: The expiration date will affect the SIP users' connection, you might want to make a note of this somewhere. | Note: The expiration date will affect the SIP users' connection, you might want to make a note of this somewhere. | ||
- | ===Running the server=== | + | =====Running the server===== |
< | < | ||
$ sudo su opensrf | $ sudo su opensrf | ||
Line 62: | Line 81: | ||
</ | </ | ||
- | ===Logging=== | + | =====Logging===== |
==Syslog== | ==Syslog== | ||
It is useful to log SIP requests to a separate file especially during initial setup by modifying your syslog config file. | It is useful to log SIP requests to a separate file especially during initial setup by modifying your syslog config file. | ||
Line 80: | Line 99: | ||
- Restart syslog-ng < | - Restart syslog-ng < | ||
- | ===Testing Your Connection=== | + | == syslog-ng(remote logging server) == |
+ | |||
+ | Use this configuration in the destination server' | ||
+ | |||
+ | < | ||
+ | # -------------------------------------------------------------------------------- | ||
+ | # Destination | ||
+ | # -------------------------------------------------------------------------------- | ||
+ | |||
+ | destination d_external_sip { # f_sip | ||
+ | file("/ | ||
+ | template(" | ||
+ | |||
+ | |||
+ | # -------------------------------------------------------------------------------- | ||
+ | # Filter | ||
+ | # -------------------------------------------------------------------------------- | ||
+ | |||
+ | filter f_sip { match(" | ||
+ | |||
+ | # -------------------------------------------------------------------------------- | ||
+ | # Log Statement | ||
+ | # -------------------------------------------------------------------------------- | ||
+ | |||
+ | log { source(s_external); | ||
+ | |||
+ | Add the lines below to the syslog-ng.conf on the remote server you wish to forward logs from. | ||
+ | |||
+ | < | ||
+ | #SIP | ||
+ | source s_file_sip { file("/ | ||
+ | log { source(s_file_sip); | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | =====Testing Your Connection===== | ||
* In the top level CVS checkout of the SIPServer code | * In the top level CVS checkout of the SIPServer code | ||
< | < | ||
$ cd SIPServer/t | $ cd SIPServer/t | ||
</ | </ | ||
- | * Edit SIPTest.pm, change the $instid, $server, $username, and $password variables. | + | * Edit SIPtest.pm, change the $instid, $server, $username, and $password variables. |
< | < | ||
$ PERL5LIB=../ | $ PERL5LIB=../ | ||
Line 99: | Line 154: | ||
* Don't be dismayed at " | * Don't be dismayed at " | ||
- | ===More Testing=== | + | ====More Testing==== |
Once you have opened up either the SIP OR SIP2 ports to be accessible from outside you can do some testing via telnet. | Once you have opened up either the SIP OR SIP2 ports to be accessible from outside you can do some testing via telnet. | ||
You can try this with localhost if you so wish, but we want to prove that SIP2 works from non-localhost. | You can try this with localhost if you so wish, but we want to prove that SIP2 works from non-localhost. |
evergreen-admin/sip.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1