Browse code

sbc: profile option for subscription-less NOTIFY forwarding

Stefan Sayer authored on 24/03/2014 16:49:04
Showing 3 changed files
... ...
@@ -174,6 +174,8 @@ bool SBCCallProfile::readFromConfiguration(const string& name,
174 174
 
175 175
   aleg_next_hop = cfg.getParameter("aleg_next_hop");
176 176
 
177
+  allow_subless_notify = cfg.getParameter("allow_subless_notify", "yes") == "yes";
178
+
177 179
   if (!readFilter(cfg, "header_filter", "header_list", headerfilter, false))
178 180
     return false;
179 181
   
... ...
@@ -68,6 +68,9 @@
68 68
 ## append extra headers
69 69
 #append_headers="P-Source-IP: $si\r\nP-Source-Port: $sp\r\n"
70 70
 
71
+## subscription-less NOTIFY pass through
72
+#allow_subless_notify=no
73
+
71 74
 ## reply translations
72 75
 # translate some 6xx class replies to 4xx class:
73 76
 #reply_translations="603=>488 Not acceptable here|600=>406 Not Acceptable"
... ...
@@ -627,6 +627,13 @@ Example:
627 627
   auth_aleg_pwd=$H(P-Auth-A-Pwd)
628 628
 
629 629
 
630
+NOTIFY pass-through
631
+-------------------
632
+If in-dialog NOTIFY messages which do not belong to an established subscription
633
+should not be passed through, the profile option 
634
+ allow_subless_notify=no
635
+may be set. This defaults to yes.
636
+
630 637
 SIP Session Timer configuration
631 638
 -------------------------------
632 639
 If SIP Session Timers are enabled for a profile, the session timers values