Module: sip-router
Branch: master
Commit: 3ce2efce27983e0fe818ff4e139c9589dbbfeb4a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3ce2efc…
Author: Marius Zbihlei <marius.zbihlei(a)1and1.ro>
Committer: Marius Zbihlei <marius.zbihlei(a)1and1.ro>
Date: Wed Oct 31 15:36:05 2012 +0200
modules/msrp : small documentation fix
---
modules/msrp/README | 2 +-
modules/msrp/doc/msrp_admin.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/modules/msrp/README b/modules/msrp/README
index 22a583b..5ab57f6 100644
--- a/modules/msrp/README
+++ b/modules/msrp/README
@@ -99,7 +99,7 @@ Chapter 1. Admin Guide
negotiated via INVITE-200 OK-ACK.
However, MSRP is still a text-based protocol. It uses several routing
- mechanisms similar to what exists in SIP. Furthermore, MSRP requres
+ mechanisms similar to what exists in SIP. Furthermore, MSRP requires
TCP, and recommends TLS for confidentiality and security. In light of
the scalability and performance of Kamailio in handling TCP/TLS, this
module reuses Kamailio's core framework to offer MSRP routing
diff --git a/modules/msrp/doc/msrp_admin.xml b/modules/msrp/doc/msrp_admin.xml
index 1422e8e..76813d2 100644
--- a/modules/msrp/doc/msrp_admin.xml
+++ b/modules/msrp/doc/msrp_admin.xml
@@ -29,7 +29,7 @@
<para>
However, MSRP is still a text-based protocol. It uses several routing
mechanisms similar to what exists in SIP. Furthermore,
- MSRP requres TCP, and recommends TLS for confidentiality and security.
+ MSRP requires TCP, and recommends TLS for confidentiality and security.
In light of the scalability and performance of &kamailio; in handling
TCP/TLS, this module reuses &kamailio;'s core framework to
offer MSRP routing capabilities. Along with embedded Presence and XCAP
Hi all
I'm using diferent versions of kamailio 3.3 in production environment. In 2
cases I've found what I suspect to be a mem leak in the parser.
In my scenarios, there's a stateless proxy in front of a stateful one. Both
run on the same machine and both handle the same traffic (except the one
rejected by the sl one). So my guess is that the parser has the mem leak
somewhere because the difference is the malformed messages rejected by the
first proxy.
Both have the same pkg and shm options.
The stateless one runs out of mem. shm mem and pkg mem grow until kamailio runs
out of mem. I have generated coredumps of the sl processes with kill -6 when the
mem was about to run out but I can't see anything useful there.
My question is, how can I debug this? Build kamailio with different flags?
Increase mem verbosity? It takes several days until it runs out of mem and I'd
like to catch it soon.
thanks,
Jon
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#128 - Debian / Ubuntu Packages for Kamailio 3.1.3 Broken
User who did this - Jon Bonilla (manwe)
----------
That should be fixed in latest kamailio 3.1.x versions.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=128#comment747
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Module: sip-router
Branch: master
Commit: 8a00d03a9328fd5ab4740f52ac47070e64f05236
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8a00d03…
Author: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Committer: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Date: Tue Oct 30 22:35:45 2012 +0000
modules_k/xcap_server: Enhanced org.oma.xcap-directory implementation
- Can now use a modparam to force the scheme in the listing URLs to a specific
value (default is to work out based on whether the connection is TCP or TLS).
- Can now use a modparam to force the hostname in the listing URLs to a
specific value (default is to work out based on the (mandatory) Host: header
or destination IP address and port).
- Updated README
---
modules_k/xcap_server/README | 83 ++++++++++++---
modules_k/xcap_server/doc/xcap_server_admin.xml | 75 +++++++++++++-
modules_k/xcap_server/xcap_server.c | 126 +++++++++++++++++------
3 files changed, 232 insertions(+), 52 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=8a0…
Hello,
just short note to let everyone know that the default database for
Kamailio is now named 'kamailio' - the change happened over the weekend
as part of migrating from last bits from openser to kamailio namespace.
Also, the default usernames and passwords to access the database are now:
- kamailio with password kamailiorw for read-write operations
- kamailioro with password kamailioro for read-only operations
If you set db_url parameters in the config file, there should be no
impact on existing configurations. You also have to make sure you set
the right value in kamctlrc file if you update kamctl.
This change impacts development version (to be released as 3.4.0). Two
other components are in the to-do list for this change: perl and snmpstats
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat
Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
Module: sip-router
Branch: master
Commit: 18220b91255f9a563ce56f1d05fe97905e7fe2d9
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=18220b9…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Oct 29 21:57:32 2012 +0100
UAC: Documentation updates and typo fixes
---
modules_k/uac/README | 30 ++++++++++++++++--------------
modules_k/uac/doc/uac_admin.xml | 25 +++++++++++++------------
modules_k/uac/uac_reg.c | 2 +-
3 files changed, 30 insertions(+), 27 deletions(-)
diff --git a/modules_k/uac/README b/modules_k/uac/README
index 7c115c3..d803f7e 100644
--- a/modules_k/uac/README
+++ b/modules_k/uac/README
@@ -137,20 +137,20 @@ Chapter 1. Admin Guide
The UAC (User Agent Client) module provides some basic UAC
functionalities like sending SIP requests, registering with a remote
- service and FROM header manipulation (anonymization) or client
+ service, FROM header manipulation (anonymization) and client
authentication.
From version 1.5.0 it has function to send SIP message from
configuration file. See variable $uac_req(name) and the function
uac_req_send().
- Version 3.1.0 adds user registration functionality. See
+ Version 3.1.0 adds database-driven SIP registration functionality. See
uac_reg_lookup() function and dedicated section for remote registration
configuration.
Known limitations in this version:
- * authentication does not support qop auth-int, just qop auth;
- * CSeq not increased during authentication - the response may be
+ * Authentication does not support qop auth-int, just qop auth;
+ * CSeq is not increased during authentication - the response may be
rejected.
2. Dependencies
@@ -193,8 +193,8 @@ Chapter 1. Admin Guide
3.1. rr_from_store_param (string)
- Name of Record-Route header parameter that will be used to store
- (encoded) the original FROM URI.
+ Name of Record-Route header parameter that will be used to store an
+ encoded version of the original FROM URI.
This parameter is optional, it's default value being "vsf".
@@ -217,8 +217,8 @@ modparam("uac","rr_to_store_param","my_param")
3.3. restore_mode (string)
- There are 3 mode of restoring the original FROM URI and the original TO
- URI:
+ There are 3 modes of restoring the original FROM URI and the original
+ TO URI:
* "none" - no information about original URI is stored; restoration
is not possible.
* "manual" - all following replies will be restored, but not also the
@@ -237,8 +237,8 @@ modparam("uac","restore_mode","auto")
3.4. restore_dlg (int)
If set to 1, the module uses dialog variables to store initial and new
- values for From/To headers. Dialog module has to be loaded and all
- calls that involve chages to From/To headers must be tracked.
+ values for From/To headers. The Dialog module has to be loaded and all
+ calls that involve changes to From/To headers must be tracked.
Default value of this parameter is 0.
@@ -281,8 +281,8 @@ modparam("uac","restore_from_avp","$avp(original_uri_from)")
3.7. restore_to_avp (string)
If defined and restore_mode is manual or auto, the avp is used to save
- the original to uri in order to be able to restore it in replies. That
- makes sense, if the original-uri can not be extracted from the original
+ the original To URI in order to be able to restore it in replies. That
+ makes sense if the original-uri can not be extracted from the original
request, e.g. if msg_apply_changes() was used after calling
uac_replace_to()
@@ -353,7 +353,7 @@ modparam("uac","auth_password_avp","$avp(i:12)")
3.12. reg_db_url (string)
- DB URL to fetch user profiles for registration.
+ DB URL to fetch account profiles for registration.
Example 1.12. Set reg_db_url parameter
...
@@ -376,7 +376,9 @@ modparam("uac", "reg_timer_interval", 60)
3.14. reg_contact_addr (string)
Address to be used to build contact address. Must be at least host
- part, can have port and parameters. Must not include 'sip:'.
+ part, can have port and parameters. Must not include 'sip:'. The
+ username part of the Contact: URI will be the L_UUID field in the
+ database.
Example 1.14. Set reg_contact_addr parameter
...
diff --git a/modules_k/uac/doc/uac_admin.xml b/modules_k/uac/doc/uac_admin.xml
index f663688..5e3b70a 100644
--- a/modules_k/uac/doc/uac_admin.xml
+++ b/modules_k/uac/doc/uac_admin.xml
@@ -18,8 +18,8 @@
<title>Overview</title>
<para>
The <acronym>UAC</acronym> (User Agent Client) module provides some basic UAC
- functionalities like sending SIP requests, registering with a remote service
- and FROM header manipulation (anonymization) or client authentication.
+ functionalities like sending SIP requests, registering with a remote service,
+ FROM header manipulation (anonymization) and client authentication.
</para>
<para>
From version 1.5.0 it has function to send SIP message from
@@ -27,7 +27,7 @@
uac_req_send().
</para>
<para>
- Version 3.1.0 adds user registration functionality. See
+ Version 3.1.0 adds database-driven SIP registration functionality. See
uac_reg_lookup() function and dedicated section for remote
registration configuration.
</para>
@@ -37,12 +37,12 @@
<itemizedlist>
<listitem>
<para>
- authentication does not support qop auth-int, just qop auth;
+ Authentication does not support qop auth-int, just qop auth;
</para>
</listitem>
<listitem>
<para>
- CSeq not increased during authentication - the response
+ CSeq is not increased during authentication - the response
may be rejected.
</para>
</listitem>
@@ -100,7 +100,7 @@
<title><varname>rr_from_store_param</varname> (string)</title>
<para>
Name of Record-Route header parameter that will be used to store
- (encoded) the original FROM URI.
+ an encoded version of the original FROM URI.
</para>
<para>
<emphasis>
@@ -141,7 +141,7 @@ modparam("uac","rr_to_store_param","my_param")
<section>
<title><varname>restore_mode</varname> (string)</title>
<para>
- There are 3 mode of restoring the original FROM URI and the original TO URI:
+ There are 3 modes of restoring the original FROM URI and the original TO URI:
<itemizedlist>
<listitem>
<para>
@@ -184,8 +184,8 @@ modparam("uac","restore_mode","auto")
<title><varname>restore_dlg</varname> (int)</title>
<para>
If set to 1, the module uses dialog variables to store initial and
- new values for From/To headers. Dialog module has to be loaded and
- all calls that involve chages to From/To headers must be tracked.
+ new values for From/To headers. The Dialog module has to be loaded and
+ all calls that involve changes to From/To headers must be tracked.
</para>
<para>
<emphasis>
@@ -251,8 +251,8 @@ modparam("uac","restore_from_avp","$avp(original_uri_from)")
<title><varname>restore_to_avp</varname> (string)</title>
<para>
If defined and restore_mode is manual or auto, the avp is used to save
- the original to uri in order to be able to restore it in replies.
- That makes sense, if the original-uri can not be extracted from the original
+ the original To URI in order to be able to restore it in replies.
+ That makes sense if the original-uri can not be extracted from the original
request, e.g. if msg_apply_changes() was used after calling uac_replace_to()
</para>
<para>
@@ -361,7 +361,7 @@ modparam("uac","auth_password_avp","$avp(i:12)")
<section id="reg-db-url-id">
<title><varname>reg_db_url</varname> (string)</title>
<para>
- DB URL to fetch user profiles for registration.
+ DB URL to fetch account profiles for registration.
</para>
<example>
<title>Set <varname>reg_db_url</varname> parameter</title>
@@ -402,6 +402,7 @@ modparam("uac", "reg_timer_interval", 60)
<para>
Address to be used to build contact address. Must be at least
host part, can have port and parameters. Must not include 'sip:'.
+ The username part of the Contact: URI will be the L_UUID field in the database.
</para>
<example>
<title>Set <varname>reg_contact_addr</varname> parameter</title>
diff --git a/modules_k/uac/uac_reg.c b/modules_k/uac/uac_reg.c
index 67deb46..645686f 100644
--- a/modules_k/uac/uac_reg.c
+++ b/modules_k/uac/uac_reg.c
@@ -557,7 +557,7 @@ void uac_reg_tm_callback( struct cell *t, int type, struct tmcb_params *ps)
if(auth.realm.len!=ri->realm.len
|| strncmp(auth.realm.s, ri->realm.s, ri->realm.len)!=0)
{
- LM_ERR("realms are different - ignire?!?!\n");
+ LM_ERR("realms are different - ignore?!?!\n");
}
cred.realm = auth.realm;
cred.user = ri->auth_username;
Module: sip-router
Branch: master
Commit: c244c7aeac06e4707ae76571dc73b804af31640f
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c244c7a…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Oct 29 19:50:48 2012 +0100
uac Fixing formatting
---
modules_k/uac/README | 107 ++++++++++++++++++++-------------------
modules_k/uac/doc/uac_admin.xml | 26 +++++-----
2 files changed, 67 insertions(+), 66 deletions(-)
diff --git a/modules_k/uac/README b/modules_k/uac/README
index 699b78b..7c115c3 100644
--- a/modules_k/uac/README
+++ b/modules_k/uac/README
@@ -44,23 +44,23 @@ Ramona-Elena Modroiu
3.11. auth_password_avp (string)
3.12. reg_db_url (string)
3.13. reg_timer_interval (string)
+ 3.14. reg_contact_addr (string)
- 4. reg_contact_addr (string)
- 5. Functions
+ 4. Functions
- 5.1. uac_replace_from(display,uri)
- 5.2. uac_replace_from(uri)
- 5.3. uac_restore_from()
- 5.4. uac_replace_to(display,uri)
- 5.5. uac_replace_to(uri)
- 5.6. uac_restore_to()
- 5.7. uac_auth()
- 5.8. uac_req_send()
- 5.9. uac_reg_lookup(uuid, dst)
- 5.10. uac_reg_request_to(user, mode)
+ 4.1. uac_replace_from(display,uri)
+ 4.2. uac_replace_from(uri)
+ 4.3. uac_restore_from()
+ 4.4. uac_replace_to(display,uri)
+ 4.5. uac_replace_to(uri)
+ 4.6. uac_restore_to()
+ 4.7. uac_auth()
+ 4.8. uac_req_send()
+ 4.9. uac_reg_lookup(uuid, dst)
+ 4.10. uac_reg_request_to(user, mode)
- 6. Exported pseudo-variables
- 7. Remote Registration
+ 5. Exported pseudo-variables
+ 6. Remote Registration
List of Examples
@@ -115,23 +115,23 @@ Chapter 1. Admin Guide
3.11. auth_password_avp (string)
3.12. reg_db_url (string)
3.13. reg_timer_interval (string)
+ 3.14. reg_contact_addr (string)
- 4. reg_contact_addr (string)
- 5. Functions
+ 4. Functions
- 5.1. uac_replace_from(display,uri)
- 5.2. uac_replace_from(uri)
- 5.3. uac_restore_from()
- 5.4. uac_replace_to(display,uri)
- 5.5. uac_replace_to(uri)
- 5.6. uac_restore_to()
- 5.7. uac_auth()
- 5.8. uac_req_send()
- 5.9. uac_reg_lookup(uuid, dst)
- 5.10. uac_reg_request_to(user, mode)
+ 4.1. uac_replace_from(display,uri)
+ 4.2. uac_replace_from(uri)
+ 4.3. uac_restore_from()
+ 4.4. uac_replace_to(display,uri)
+ 4.5. uac_replace_to(uri)
+ 4.6. uac_restore_to()
+ 4.7. uac_auth()
+ 4.8. uac_req_send()
+ 4.9. uac_reg_lookup(uuid, dst)
+ 4.10. uac_reg_request_to(user, mode)
- 6. Exported pseudo-variables
- 7. Remote Registration
+ 5. Exported pseudo-variables
+ 6. Remote Registration
1. Overview
@@ -189,6 +189,7 @@ Chapter 1. Admin Guide
3.11. auth_password_avp (string)
3.12. reg_db_url (string)
3.13. reg_timer_interval (string)
+ 3.14. reg_contact_addr (string)
3.1. rr_from_store_param (string)
@@ -357,7 +358,7 @@ modparam("uac","auth_password_avp","$avp(i:12)")
Example 1.12. Set reg_db_url parameter
...
modparam("uac", "reg_db_url",
- "mysql://openser:openserrw@localhost/openser")
+ "mysql://kamailio:kamailiorw@localhost/kamailio")
...
3.13. reg_timer_interval (string)
@@ -372,7 +373,7 @@ modparam("uac", "reg_db_url",
modparam("uac", "reg_timer_interval", 60)
...
-4. reg_contact_addr (string)
+3.14. reg_contact_addr (string)
Address to be used to build contact address. Must be at least host
part, can have port and parameters. Must not include 'sip:'.
@@ -382,20 +383,20 @@ modparam("uac", "reg_timer_interval", 60)
modparam("uac", "reg_contact_addr", "192.168.1.2:5080")
...
-5. Functions
+4. Functions
- 5.1. uac_replace_from(display,uri)
- 5.2. uac_replace_from(uri)
- 5.3. uac_restore_from()
- 5.4. uac_replace_to(display,uri)
- 5.5. uac_replace_to(uri)
- 5.6. uac_restore_to()
- 5.7. uac_auth()
- 5.8. uac_req_send()
- 5.9. uac_reg_lookup(uuid, dst)
- 5.10. uac_reg_request_to(user, mode)
+ 4.1. uac_replace_from(display,uri)
+ 4.2. uac_replace_from(uri)
+ 4.3. uac_restore_from()
+ 4.4. uac_replace_to(display,uri)
+ 4.5. uac_replace_to(uri)
+ 4.6. uac_restore_to()
+ 4.7. uac_auth()
+ 4.8. uac_req_send()
+ 4.9. uac_reg_lookup(uuid, dst)
+ 4.10. uac_reg_request_to(user, mode)
-5.1. uac_replace_from(display,uri)
+4.1. uac_replace_from(display,uri)
Replace in FROM header the display name and the URI part.
@@ -433,7 +434,7 @@ uac_replace_from("","sip:robin@gotham.org");
uac_replace_from("","");
...
-5.2. uac_replace_from(uri)
+4.2. uac_replace_from(uri)
Replace in FROM header the URI part without altering the display name.
@@ -446,7 +447,7 @@ uac_replace_from("","");
uac_replace_from("sip:batman@gotham.org");
...
-5.3. uac_restore_from()
+4.3. uac_restore_from()
This function will check if the FROM URI was modified and will use the
information stored in header parameter to restore the original FROM URI
@@ -459,7 +460,7 @@ uac_replace_from("sip:batman@gotham.org");
uac_restore_from();
...
-5.4. uac_replace_to(display,uri)
+4.4. uac_replace_to(display,uri)
Replace in TO header the display name and the URI part.
@@ -479,7 +480,7 @@ uac_replace_to("","sip:robin@gotham.org");
uac_replace_to("","");
...
-5.5. uac_replace_to(uri)
+4.5. uac_replace_to(uri)
Replace in TO header the URI part without altering the display name.
@@ -510,7 +511,7 @@ uac_replace_to("","");
uac_replace_to("sip:batman@gotham.org");
...
-5.6. uac_restore_to()
+4.6. uac_restore_to()
This function will check if the TO URI was modified and will use the
information stored in header parameter to restore the original TO URI
@@ -523,7 +524,7 @@ uac_replace_to("sip:batman@gotham.org");
uac_restore_to();
...
-5.7. uac_auth()
+4.7. uac_auth()
This function can be called only from failure route and will build the
authentication response header and insert it into the request without
@@ -536,7 +537,7 @@ uac_restore_to();
uac_auth();
...
-5.8. uac_req_send()
+4.8. uac_req_send()
This function sends a SIP message from the configuration file. The
message is built out of $uac_req(...) pseudo-variable.
@@ -553,7 +554,7 @@ $uac_req(turi)="sip:kamailio.org";
uac_req_send();
...
-5.9. uac_reg_lookup(uuid, dst)
+4.9. uac_reg_lookup(uuid, dst)
This function sets the PV dst to SIP URI that correspond to uuid in uac
registations table. uuid and dst must be pseudo-variables.
@@ -569,7 +570,7 @@ if(uac_reg_lookup("$rU", "$ru"))
}
...
-5.10. uac_reg_request_to(user, mode)
+4.10. uac_reg_request_to(user, mode)
This function can be used to send an authenticated request to a remote
user in the uac registrations table. It sets the request-uri, dst-uri
@@ -602,14 +603,14 @@ failure_route[REMOTE_AUTH] {
}
...
-6. Exported pseudo-variables
+5. Exported pseudo-variables
* $uac_req(key)
Exported pseudo-variables are documented at
http://www.kamailio.org/dokuwiki/.
-7. Remote Registration
+6. Remote Registration
The module can register contact addresses to remote REGISTRAR servers.
You have to add records to uacreg table. The table stores following
diff --git a/modules_k/uac/doc/uac_admin.xml b/modules_k/uac/doc/uac_admin.xml
index 53a1fa1..f663688 100644
--- a/modules_k/uac/doc/uac_admin.xml
+++ b/modules_k/uac/doc/uac_admin.xml
@@ -395,25 +395,25 @@ modparam("uac", "reg_timer_interval", 60)
</example>
</section>
- </section>
- <section id="reg-contact-addr-id">
- <title><varname>reg_contact_addr</varname> (string)</title>
- <para>
- Address to be used to build contact address. Must be at least
- host part, can have port and parameters. Must not include 'sip:'.
- </para>
- <example>
- <title>Set <varname>reg_contact_addr</varname> parameter</title>
- <programlisting format="linespecific">
+ <section id="reg-contact-addr-id">
+ <title><varname>reg_contact_addr</varname> (string)</title>
+ <para>
+ Address to be used to build contact address. Must be at least
+ host part, can have port and parameters. Must not include 'sip:'.
+ </para>
+ <example>
+ <title>Set <varname>reg_contact_addr</varname> parameter</title>
+ <programlisting format="linespecific">
...
modparam("uac", "reg_contact_addr", "192.168.1.2:5080")
...
- </programlisting>
- </example>
- </section>
+ </programlisting>
+ </example>
+ </section>
+ </section>
<section>
<title>Functions</title>
Setup:
One kamailio behind a NAT, one on public IP.
I register a client using the inside Kamailio as an outbound proxy. It adds a path header and forwards over TCP to the public server. This server saves the registration with the path header and send a response, which reaches the client fine.
Calling from the client to it's own number, the INVITE is sent over the inside proxy to the outside, it looks up the location database then drops the request. It doesn't realize that it has a TCP connection it can reuse open. The error message - a timeout - is sent back over the connection.
In my dream world, the server would reuse the open TCP connection to get back across the NAT. If we can get the response across, we should be able to get a new request back.
Now, I don't know the inner workings of TCP connection handling here. I guess I should test having the client open a connection directly to the outside proxy and see if that works.
Would it be possible with the current architecture to get Kamailio to reuse an existing TCP connection like this?
I started digging down the TCP code, but lost attention because of the complexity and fixed speling erors in other parts instead... Will try again.
/O
Module: sip-router
Branch: master
Commit: 212cf0d3c0d220affbafa545795ff5d0bf03b97d
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=212cf0d…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Sun Oct 28 21:09:51 2012 +0100
permissions - change openser => kamailio
---
modules_k/permissions/README | 2 +-
modules_k/permissions/doc/permissions_admin.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/modules_k/permissions/README b/modules_k/permissions/README
index 83cacc9..cf8498d 100644
--- a/modules_k/permissions/README
+++ b/modules_k/permissions/README
@@ -274,7 +274,7 @@ Chapter 1. Admin Guide
1.4. Address Permissions
The module can be used to determine if an address (IP address and port)
- matches any of the IP subnets stored in cached openser database table.
+ matches any of the IP subnets stored in cached Kamailio database table.
Port 0 in cached database table matches any port. IP address and port
to be matched can be either taken from the request
(allow_source_address) or given as pvar arguments (allow_address).
diff --git a/modules_k/permissions/doc/permissions_admin.xml b/modules_k/permissions/doc/permissions_admin.xml
index 6e16bd2..5788dfb 100644
--- a/modules_k/permissions/doc/permissions_admin.xml
+++ b/modules_k/permissions/doc/permissions_admin.xml
@@ -170,7 +170,7 @@
<para>
The module can be used to determine if an address (IP
address and port) matches any of the IP subnets
- stored in cached openser database table.
+ stored in cached &kamailio; database table.
Port 0 in cached database table matches any port. IP
address and port to be matched can be either taken from
the request (allow_source_address) or given as pvar