Module: sip-router
Branch: master
Commit: f6f42b24c2df7d3840ebe42be262b1dc5092b86a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f6f42b2…
Author: Alex Balashov <abalashov(a)evaristesys.com>
Committer: Alex Balashov <abalashov(a)evaristesys.com>
Date: Mon Nov 21 07:10:21 2011 -0500
Doc fixes for reg_timer_interval patch. I'll try not to break things
again.
---
modules_k/uac/README | 131 ++++++++++++++++++++++-----------------
modules_k/uac/doc/uac_admin.xml | 16 -----
2 files changed, 73 insertions(+), 74 deletions(-)
diff --git a/modules_k/uac/README b/modules_k/uac/README
index 1dcf3b7..91cc281 100644
--- a/modules_k/uac/README
+++ b/modules_k/uac/README
@@ -39,20 +39,21 @@ Ramona-Elena Modroiu
3.6. auth_username_avp (string)
3.7. auth_password_avp (string)
3.8. reg_db_url (string)
- 3.9. reg_contact_addr (string)
+ 3.9. reg_timer_interval (string)
- 4. Functions
+ 4. reg_contact_addr (string)
+ 5. Functions
- 4.1. uac_replace_from(display,uri)
- 4.2. uac_replace_from(uri)
- 4.3. uac_restore_from()
- 4.4. uac_auth()
- 4.5. uac_req_send()
- 4.6. uac_reg_lookup(uuid, dst)
- 4.7. uac_reg_request_to(user, mode)
+ 5.1. uac_replace_from(display,uri)
+ 5.2. uac_replace_from(uri)
+ 5.3. uac_restore_from()
+ 5.4. uac_auth()
+ 5.5. uac_req_send()
+ 5.6. uac_reg_lookup(uuid, dst)
+ 5.7. uac_reg_request_to(user, mode)
- 5. Exported pseudo-variables
- 6. Remote Registration
+ 6. Exported pseudo-variables
+ 7. Remote Registration
List of Examples
@@ -64,15 +65,16 @@ Ramona-Elena Modroiu
1.6. Set auth_username_avp parameter
1.7. Set auth_password_avp parameter
1.8. Set reg_db_url parameter
- 1.9. Set reg_contact_addr parameter
- 1.10. uac_replace_from usage
+ 1.9. Set reg_timer_inteval parameter
+ 1.10. Set reg_contact_addr parameter
1.11. uac_replace_from usage
- 1.12. uac_restore_from usage
- 1.13. uac_auth usage
- 1.14. uac_req_send usage
- 1.15. uac_reg_lookup usage
- 1.16. uac_reg_request_to usage
- 1.17. lookup remote registrations usage
+ 1.12. uac_replace_from usage
+ 1.13. uac_restore_from usage
+ 1.14. uac_auth usage
+ 1.15. uac_req_send usage
+ 1.16. uac_reg_lookup usage
+ 1.17. uac_reg_request_to usage
+ 1.18. lookup remote registrations usage
Chapter 1. Admin Guide
@@ -94,20 +96,21 @@ Chapter 1. Admin Guide
3.6. auth_username_avp (string)
3.7. auth_password_avp (string)
3.8. reg_db_url (string)
- 3.9. reg_contact_addr (string)
+ 3.9. reg_timer_interval (string)
- 4. Functions
+ 4. reg_contact_addr (string)
+ 5. Functions
- 4.1. uac_replace_from(display,uri)
- 4.2. uac_replace_from(uri)
- 4.3. uac_restore_from()
- 4.4. uac_auth()
- 4.5. uac_req_send()
- 4.6. uac_reg_lookup(uuid, dst)
- 4.7. uac_reg_request_to(user, mode)
+ 5.1. uac_replace_from(display,uri)
+ 5.2. uac_replace_from(uri)
+ 5.3. uac_restore_from()
+ 5.4. uac_auth()
+ 5.5. uac_req_send()
+ 5.6. uac_reg_lookup(uuid, dst)
+ 5.7. uac_reg_request_to(user, mode)
- 5. Exported pseudo-variables
- 6. Remote Registration
+ 6. Exported pseudo-variables
+ 7. Remote Registration
1. Overview
@@ -155,7 +158,7 @@ Chapter 1. Admin Guide
3.6. auth_username_avp (string)
3.7. auth_password_avp (string)
3.8. reg_db_url (string)
- 3.9. reg_contact_addr (string)
+ 3.9. reg_timer_interval (string)
3.1. rr_store_param (string)
@@ -263,27 +266,39 @@ modparam("uac", "reg_db_url",
"mysql://openser:openserrw@localhost/openser")
...
-3.9. reg_contact_addr (string)
+3.9. reg_timer_interval (string)
+
+ Timer interval (in seconds) at which registrations are managed, e.g.
+ renewed as needed.
+
+ The default value is 90 seconds.
+
+ Example 1.9. Set reg_timer_inteval parameter
+...
+modparam("uac", "reg_timer_interval", 60)
+...
+
+4. 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:'.
- Example 1.9. Set reg_contact_addr parameter
+ Example 1.10. Set reg_contact_addr parameter
...
modparam("uac", "reg_contact_addr", "192.168.1.2:5080")
...
-4. Functions
+5. Functions
- 4.1. uac_replace_from(display,uri)
- 4.2. uac_replace_from(uri)
- 4.3. uac_restore_from()
- 4.4. uac_auth()
- 4.5. uac_req_send()
- 4.6. uac_reg_lookup(uuid, dst)
- 4.7. uac_reg_request_to(user, mode)
+ 5.1. uac_replace_from(display,uri)
+ 5.2. uac_replace_from(uri)
+ 5.3. uac_restore_from()
+ 5.4. uac_auth()
+ 5.5. uac_req_send()
+ 5.6. uac_reg_lookup(uuid, dst)
+ 5.7. uac_reg_request_to(user, mode)
-4.1. uac_replace_from(display,uri)
+5.1. uac_replace_from(display,uri)
Replace in FROM header the display name and the URI part.
@@ -291,7 +306,7 @@ modparam("uac", "reg_contact_addr", "192.168.1.2:5080")
This function can be used from REQUEST_ROUTE and from BRANCH_ROUTE.
- Example 1.10. uac_replace_from usage
+ Example 1.11. uac_replace_from usage
...
# replace both display and uri
uac_replace_from("$avp(s:display)","$avp(s:uri)");
@@ -303,7 +318,7 @@ uac_replace_from("","sip:robin@gotham.org");
uac_replace_from("","");
...
-4.2. uac_replace_from(uri)
+5.2. uac_replace_from(uri)
Replace in FROM header the URI part without altering the display name.
@@ -311,12 +326,12 @@ uac_replace_from("","");
This function can be used from REQUEST_ROUTE and from BRANCH_ROUTE.
- Example 1.11. uac_replace_from usage
+ Example 1.12. uac_replace_from usage
...
uac_replace_from("sip:batman@gotham.org");
...
-4.3. uac_restore_from()
+5.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
@@ -324,12 +339,12 @@ uac_replace_from("sip:batman@gotham.org");
This function can be used from REQUEST_ROUTE.
- Example 1.12. uac_restore_from usage
+ Example 1.13. uac_restore_from usage
...
uac_restore_from();
...
-4.4. uac_auth()
+5.4. 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
@@ -337,12 +352,12 @@ uac_restore_from();
This function can be used from FAILURE_ROUTE.
- Example 1.13. uac_auth usage
+ Example 1.14. uac_auth usage
...
uac_auth();
...
-4.5. uac_req_send()
+5.5. uac_req_send()
This function sends a SIP message from the configuration file. The
message is built out of $uac_req(...) pseudo-variable.
@@ -350,7 +365,7 @@ uac_auth();
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE, ONREPLY_ROUTE, LOCAL_ROUTE.
- Example 1.14. uac_req_send usage
+ Example 1.15. uac_req_send usage
...
$uac_req(method)="OPTIONS";
$uac_req(ruri)="sip:kamailio.org";
@@ -359,14 +374,14 @@ $uac_req(turi)="sip:kamailio.org";
uac_req_send();
...
-4.6. uac_reg_lookup(uuid, dst)
+5.6. 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.
This function can be used from ANY_ROUTE.
- Example 1.15. uac_reg_lookup usage
+ Example 1.16. uac_reg_lookup usage
...
if(uac_reg_lookup("$rU", "$ru"))
@@ -375,7 +390,7 @@ if(uac_reg_lookup("$rU", "$ru"))
}
...
-4.7. uac_reg_request_to(user, mode)
+5.7. 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
@@ -389,7 +404,7 @@ if(uac_reg_lookup("$rU", "$ru"))
This function can be used from REQUEST_ROUTE, FAILURE_ROUTE,
BRANCH_ROUTE.
- Example 1.16. uac_reg_request_to usage
+ Example 1.17. uac_reg_request_to usage
...
if(uac_reg_request_to("$fU", 0))
@@ -408,14 +423,14 @@ failure_route[REMOTE_AUTH] {
}
...
-5. Exported pseudo-variables
+6. Exported pseudo-variables
* $uac_req(key)
Exported pseudo-variables are documented at
http://www.kamailio.org/dokuwiki/.
-6. Remote Registration
+7. Remote Registration
The module can register contact addresses to remote REGISTRAR servers.
You have to add records to uacreg table. The table stores following
@@ -448,7 +463,7 @@ failure_route[REMOTE_AUTH] {
if the call is coming from a remote SIP provider and can change the
R-URI to local username@domain. Afterwards you can run location lookup.
- Example 1.17. lookup remote registrations usage
+ Example 1.18. lookup remote registrations usage
...
if(uac_reg_lookup("$rU", "$ru")) {
xlog("request from a remote SIP provider [$ou => $ru]\n");
diff --git a/modules_k/uac/doc/uac_admin.xml b/modules_k/uac/doc/uac_admin.xml
index e278be6..6abbaea 100644
--- a/modules_k/uac/doc/uac_admin.xml
+++ b/modules_k/uac/doc/uac_admin.xml
@@ -273,22 +273,6 @@ modparam("uac", "reg_db_url",
</example>
</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">
-...
-modparam("uac", "reg_contact_addr", "192.168.1.2:5080")
-...
- </programlisting>
- </example>
- </section>
-
<section id="reg-timer-interval-id">
<title><varname>reg_timer_interval</varname> (string)</title>
<para>
Hello,
I put together a wiki page to help people porting patches between
branches, exemplified with master and 3.2 branches -- the typical patch
backporting these days:
* http://www.kamailio.org/wiki/devel/backporting-to-3.2.x
They are useful also for people with no write access, in case they want
to try patches committed to devel branch in their local git repo clones.
In additions, I added to kamailio wiki the page with guidelines for
commits, trying to give the generic suggestions of how to do it in order
to keep the coherence of the development:
* http://www.kamailio.org/wiki/devel/git-commit-guidelines
Updates and enhancements are welcome! If one has more suggestions or
want to debate some of the proposed guidelines, feel free to start the
discussion on the mailing list.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Bayan Towfiq (btowfiq)
----------
Just as a note both Brandon Armstead and I are using dlg_manage() in the script. Could this have something to do with it?
Bayan
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment370
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#179 - segfault in tm/timers?
User who did this - Bayan Towfiq (btowfiq)
http://sip-router.org/tracker/index.php?do=details&task_id=179
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.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#173 - Double Free -- Crash/Coredump and possible security vulnerability
User who did this - Brandon Armstead (CRYY2010)
----------
Timo,
To be honest - after the crash occurred I've tried like 10 different builds from the top of the origin/3.1 origin/3.2 branch downwards - trying to see if one of them would not reproduce the crash. So I can not say without a doubt that this log info is from a 3.1 or a 3.2 branch.
However the crash has happened with latest git 3.1 and 3.2 and several commits downwards from these branches.
*** MOD PARAM ***
# dialog
modparam("dialog", "enable_stats", 1)
modparam("dialog", "dlg_flag", 4)
modparam("dialog", "timeout_avp", "$avp(s:dialog-timeout)")
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "db_mode", 1)
modparam("dialog", "detect_spirals", 1)
*** SCENARIO ***
The only thing that I am doing in configuration with dialog is three things.
1) I call dlg_manage right before t_relay()
2) I have the following code ABOVE loose_route:
if(dlg_get("$ci", "$ft", "$tt")){
xlog("L_INFO", "[$ci] forceful call hangup");
dlg_bye("all");
}
3) I am using various dialog pseudo variables through out the config, typically to insert information into the database via avp_db_query.
That is the extent of my dialog scripting.
Here is another interesting .... thought this issue seems specific to the following call scenario:
UAC -> outbound call -> REGISTRAR -> (CORE PROXY / LCR *CRASHING*) -> PSTN
PSTN responds with 503 "Service Unavailable"
CORE / PROXY advance routes -> SECOND PSTN
*CRASH*
Also - another interesting note is that it seems it only happens in this scenario when sending the call to the explicit "SECOND PSTN".
If I trade out SECOND PSTN for THIRD PSTN (an alternate carrier) then the crash does not happen.
I hope this provides some more light on the situation, let me know if I can provide any additional information, thanks!
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=173#comment369
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.