Module: sems
Branch: master
Commit: 06387027ac41979f853a7f9425cbd0ce79fbdd03
URL:    
http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=06387027ac41979f853a7f9425cbd0ce79fbdd03

Author: Stefan Sayer <[email protected]>
Committer: Stefan Sayer <[email protected]>
Date:   Mon Nov 21 13:48:54 2011 +0100

sbc: added note about SIP auth (a/b leg)

---

 doc/Readme.sbc.txt |   33 ++++++++++++++++++++++++++++++++-
 1 files changed, 32 insertions(+), 1 deletions(-)

diff --git a/doc/Readme.sbc.txt b/doc/Readme.sbc.txt
index 9fcd375..9ef5ab9 100644
--- a/doc/Readme.sbc.txt
+++ b/doc/Readme.sbc.txt
@@ -1,6 +1,6 @@
 SBC module
 
-Copyright (C) 2010 Stefan Sayer
+Copyright (C) 2010-2011 Stefan Sayer
 
 Overview
 --------
@@ -348,6 +348,37 @@ Reliable 1xx (PRACK)
 Reliable 1xx (PRACK) extension (3262) is supported in a transparent mode,
 i.e. the RSeq header is relayed and RAck CSeq is translated properly.
 
+SIP authentication
+------------------
+The SBC can perform SIP digest authentication. To use SIP authentication, the
+uac_auth module needs to be loaded.
+
+SIP authentication is enabled by the following parameters, separately for both
+call legs:
+
+# Authentication for B leg (second/callee leg):
+   enable_auth       "yes" or "no"
+   auth_user         authentication user
+   auth_pwd          authentication password
+# Authentication for A leg (first/caller leg):
+   enable_aleg_auth  "yes" or "no"
+   auth_aleg_user    authentication user
+   auth_aleg_pwd     authentication password
+
+
+Note: The 'A' leg is always the first leg, the one from the caller. 'B' leg is
+the one to callee:
+ caller <--- A (first) leg ---> SEMS <--- B (second) leg ---> callee
+
+Example:
+  enable_auth=yes
+  auth_user=$H(P-Auth-B-User)
+  auth_pwd=$H(P-Auth-B-Pwd)
+  enable_aleg_auth=yes
+  auth_aleg_user=$H(P-Auth-A-User)
+  auth_aleg_pwd=$H(P-Auth-A-Pwd)
+
+
 SIP Session Timer configuration
 -------------------------------
 If SIP Session Timers are enabled for a profile, the session timers values

_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev

Reply via email to