sr-dev September 2014

sr-dev@lists.kamailio.org

33 participants
375 discussions

git:master: dmq: update documentation with new functions dmq_t_replicate() and dmq_is_from_node()

by Charles Chance

Module: sip-router Branch: master Commit: 9556f8a37575c8f9a3a212f07e9fa9632116e06e URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9556f8a… Author: Charles Chance <charles.chance(a)sipcentric.com> Committer: Charles Chance <charles.chance(a)sipcentric.com> Date: Wed Sep 10 00:41:48 2014 +0100 dmq: update documentation with new functions dmq_t_replicate() and dmq_is_from_node() --- modules/dmq/README | 50 +++++++++++++++++++++++++++++++++ modules/dmq/doc/dmq_admin.xml | 61 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 111 insertions(+), 0 deletions(-) diff --git a/modules/dmq/README b/modules/dmq/README index 7f3fb6b..8bc19e4 100644 --- a/modules/dmq/README +++ b/modules/dmq/README @@ -41,6 +41,8 @@ Charles Chance 4.1. dmq_handle_message() 4.2. dmq_send_message(peer, node, body, content_type) 4.3. dmq_bcast_message(peer, body, content_type) + 4.4. dmq_t_replicate([skip_loop_test]) + 4.5. dmq_is_from_node() 2. Developer Guide @@ -63,6 +65,8 @@ Charles Chance 1.5. dmq_handle_message usage 1.6. dmq_send_message usage 1.7. dmq_bcast_message usage + 1.8. dmq_t_replicate usage + 1.9. dmq_is_from_node usage 2.1. dmq_api_t structure 2.2. register_dmq_peer usage 2.3. bcast_message usage @@ -90,6 +94,8 @@ Chapter 1. Admin Guide 4.1. dmq_handle_message() 4.2. dmq_send_message(peer, node, body, content_type) 4.3. dmq_bcast_message(peer, body, content_type) + 4.4. dmq_t_replicate([skip_loop_test]) + 4.5. dmq_is_from_node() 1. Overview @@ -183,6 +189,8 @@ modparam("dmq", "ping_interval", 90) 4.1. dmq_handle_message() 4.2. dmq_send_message(peer, node, body, content_type) 4.3. dmq_bcast_message(peer, body, content_type) + 4.4. dmq_t_replicate([skip_loop_test]) + 4.5. dmq_is_from_node() 4.1. dmq_handle_message() @@ -234,6 +242,48 @@ text/plain"); dmq_bcast_message("peer_name", "Message body...", "text/plain"); ... +4.4. dmq_t_replicate([skip_loop_test]) + + Replicates the current SIP message to all active nodes (except self). + Useful for replicating REGISTER, PUBLISH etc. in a clustered + environment. + + Meaning of parameters: + * skip_loop_test - by default, DMQ checks the source IP of the + message prior to replication, to ensure it has not been sent by + another DMQ node (to avoid infinite loops). If this optional + parameter is set to "1", the loop test is not performed. This makes + sense, from a performance perspective, if you have already + performed the necessary checks in the config script (see + dmq_is_from_node()). + + This function can be used from REQUEST_ROUTE only. + + Example 1.8. dmq_t_replicate usage +... + dmq_t_replicate(); +... + +4.5. dmq_is_from_node() + + Checks whether the current message has been sent by another DMQ node in + the cluster. + + This function can be used from REQUEST_ROUTE only. + + Example 1.9. dmq_is_from_node usage +... + # Example REGISTER block + if (dmq_is_from_node()) { + # Already authenticated, just save contact... + } else { + # Authenticate, save contact etc. + # Assuming all successful... + dmq_t_replicate("1"); # Already checked source, don't perform lo +op test again + } +... + Chapter 2. Developer Guide Table of Contents diff --git a/modules/dmq/doc/dmq_admin.xml b/modules/dmq/doc/dmq_admin.xml index 0192a21..7eabc1a 100644 --- a/modules/dmq/doc/dmq_admin.xml +++ b/modules/dmq/doc/dmq_admin.xml @@ -244,6 +244,67 @@ modparam("dmq", "ping_interval", 90) </programlisting> </example> </section> + <section id="dmq.f.dmq_t_replicate"> + <title> + <function moreinfo="none">dmq_t_replicate([skip_loop_test])</function> + </title> + <para> + Replicates the current SIP message to all active nodes (except self). Useful for replicating + REGISTER, PUBLISH etc. in a clustered environment. + </para> + <para>Meaning of parameters:</para> + <itemizedlist> + <listitem> + <para> + <emphasis>skip_loop_test</emphasis> - by default, DMQ checks the source IP of the + message prior to replication, to ensure it has not been sent by another DMQ node + (to avoid infinite loops). If this optional parameter is set to "1", the loop test + is not performed. This makes sense, from a performance perspective, if you have + already performed the necessary checks in the config script (see dmq_is_from_node()). + </para> + </listitem> + </itemizedlist> + <para> + This function can be used from REQUEST_ROUTE only. + </para> + + <example> + <title><function>dmq_t_replicate</function> usage</title> + <programlisting format="linespecific"> +... + dmq_t_replicate(); +... + </programlisting> + </example> + </section> + <section id="dmq.f.dmq_is_from_node"> + <title> + <function moreinfo="none">dmq_is_from_node()</function> + </title> + <para> + Checks whether the current message has been sent by another DMQ node in the cluster. + </para> + <para> + This function can be used from REQUEST_ROUTE only. + </para> + + <example> + <title><function>dmq_is_from_node</function> usage</title> + <programlisting format="linespecific"> +... + # Example REGISTER block + if (dmq_is_from_node()) { + # Already authenticated, just save contact... + } else { + # Authenticate, save contact etc. + # Assuming all successful... + dmq_t_replicate("1"); # Already checked source, don't perform loop test again + } +... + </programlisting> + </example> + </section> + </section> </chapter>

10 years, 2 months

git:master: dmq: add the following config functions:

by Charles Chance

Module: sip-router Branch: master Commit: d99a9c7f47613078f9d8ab42959e954fc58518f7 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=d99a9c7… Author: Charles Chance <charles.chance(a)sipcentric.com> Committer: Charles Chance <charles.chance(a)sipcentric.com> Date: Tue Sep 9 23:42:35 2014 +0100 dmq: add the following config functions: - dmq_t_replicate(): Replicates current SIP message to all active DMQ nodes. Includes built-in loop detection which can be skipped with optional parameter. - dmq_is_from_node(): Checks whether current message has come from another node, based on source IP. --- modules/dmq/dmq.c | 6 ++++ modules/dmq/dmq_funcs.c | 73 +++++++++++++++++++++++++++++++++++++++++++++++ modules/dmq/dmq_funcs.h | 2 + 3 files changed, 81 insertions(+), 0 deletions(-) diff --git a/modules/dmq/dmq.c b/modules/dmq/dmq.c index 30405f1..06d9cfb 100644 --- a/modules/dmq/dmq.c +++ b/modules/dmq/dmq.c @@ -97,6 +97,12 @@ static cmd_export_t cmds[] = { ANY_ROUTE}, {"dmq_bcast_message", (cmd_function)cfg_dmq_bcast_message, 3, bcast_dmq_fixup, 0, ANY_ROUTE}, + {"dmq_t_replicate", (cmd_function)cfg_dmq_t_replicate, 0, 0, 0, + REQUEST_ROUTE}, + {"dmq_t_replicate", (cmd_function)cfg_dmq_t_replicate, 1, fixup_spve_null, 0, + REQUEST_ROUTE}, + {"dmq_is_from_node", (cmd_function)cfg_dmq_is_from_node, 0, 0, 0, + REQUEST_ROUTE}, {"bind_dmq", (cmd_function)bind_dmq, 0, 0, 0}, {0, 0, 0, 0, 0, 0} }; diff --git a/modules/dmq/dmq_funcs.c b/modules/dmq/dmq_funcs.c index 6b09b2a..3c9c8c3 100644 --- a/modules/dmq/dmq_funcs.c +++ b/modules/dmq/dmq_funcs.c @@ -114,6 +114,30 @@ int build_uri_str(str* username, struct sip_uri* uri, str* from) return 0; } +/* Checks if the request (sip_msg_t* msg) comes from another DMQ node based on source IP. */ +int is_from_remote_node(sip_msg_t* msg) +{ + ip_addr_t* ip; + dmq_node_t* node; + int result = -1; + + ip = &msg->rcv.src_ip; + + lock_get(&node_list->lock); + node = node_list->nodes; + + while(node) { + if (!node->local && ip_addr_cmp(ip, &node->ip_address)) { + result = 1; + goto done; + } + node = node->next; + } +done: + lock_release(&node_list->lock); + return result; +} + /** * @brief broadcast a dmq message * @@ -340,6 +364,55 @@ error: return -1; } +/** + * @brief config file function for replicating SIP message to all nodes (wraps t_replicate) + */ +int cfg_dmq_t_replicate(struct sip_msg* msg, char* s) +{ + dmq_node_t* node; + int i = 0; + + /* avoid loops - do not replicate if message has come from another node + * (override if optional parameter is set) + */ + if ((!s || (get_int_fparam(&i, msg, (fparam_t*)s)==0 && !i)) + && (is_from_remote_node(msg) > 0)) { + LM_DBG("message is from another node - skipping replication\n"); + return -1; + } + + lock_get(&node_list->lock); + node = node_list->nodes; + while(node) { + /* we do not send the message to the following: + * - ourself + * - any inactive nodes + */ + if(node->local || node->status != DMQ_NODE_ACTIVE) { + LM_DBG("skipping node %.*s\n", STR_FMT(&node->orig_uri)); + node = node->next; + continue; + } + if(tmb.t_replicate(msg, &node->orig_uri) < 0) { + LM_ERR("error calling t_replicate\n"); + goto error; + } + node = node->next; + } + lock_release(&node_list->lock); + return 0; +error: + lock_release(&node_list->lock); + return -1; +} + +/* + * @brief config file function to check if received message is from another DMQ node based on source IP + */ +int cfg_dmq_is_from_node(struct sip_msg* msg) +{ + return is_from_remote_node(msg); +} /** * @brief pings the servers in the nodelist diff --git a/modules/dmq/dmq_funcs.h b/modules/dmq/dmq_funcs.h index a138788..55f67ac 100644 --- a/modules/dmq/dmq_funcs.h +++ b/modules/dmq/dmq_funcs.h @@ -50,6 +50,8 @@ int cfg_dmq_send_message(struct sip_msg* msg, char* peer, char* to, char* body, char* content_type); int cfg_dmq_bcast_message(struct sip_msg* msg, char* peer, char* body, char* content_type); +int cfg_dmq_t_replicate(struct sip_msg* msg, char* s); +int cfg_dmq_is_from_node(struct sip_msg* msg); dmq_peer_t* register_dmq_peer(dmq_peer_t* peer); int dmq_send_message(dmq_peer_t* peer, str* body, dmq_node_t* node, dmq_resp_cback_t* resp_cback, int max_forwards, str* content_type);

10 years, 2 months

git:master: dmq: include resolved IP address in RPC list_nodes output

by Charles Chance

Module: sip-router Branch: master Commit: 3bf32dc0003b447a5695be5ff9d22d70f393c62f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=3bf32dc… Author: Charles Chance <charles.chance(a)sipcentric.com> Committer: Charles Chance <charles.chance(a)sipcentric.com> Date: Tue Sep 9 23:52:46 2014 +0100 dmq: include resolved IP address in RPC list_nodes output --- modules/dmq/dmq.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/modules/dmq/dmq.c b/modules/dmq/dmq.c index 06d9cfb..c773e1f 100644 --- a/modules/dmq/dmq.c +++ b/modules/dmq/dmq.c @@ -343,12 +343,16 @@ static void dmq_rpc_list_nodes(rpc_t *rpc, void *c) { void *h; dmq_node_t* cur = node_list->nodes; + char ip[IP6_MAX_STR_SIZE + 1]; while(cur) { + memset(ip, 0, IP6_MAX_STR_SIZE + 1); + ip_addr2sbuf(&cur->ip_address, ip, IP6_MAX_STR_SIZE); if (rpc->add(c, "{", &h) < 0) goto error; - if (rpc->struct_add(h, "SSddd", + if (rpc->struct_add(h, "SSsddd", "host", &cur->uri.host, "port", &cur->uri.port, + "resolved_ip", ip, "status", cur->status, "last_notification", cur->last_notification, "local", cur->local) < 0) goto error;

10 years, 2 months

git:master: dmq: resolve IP address and store in node structure

by Charles Chance

Module: sip-router Branch: master Commit: b7bbcd730b21e7480dc1f1e26de58750395e6ff6 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b7bbcd7… Author: Charles Chance <charles.chance(a)sipcentric.com> Committer: Charles Chance <charles.chance(a)sipcentric.com> Date: Tue Sep 9 23:41:47 2014 +0100 dmq: resolve IP address and store in node structure --- modules/dmq/dmqnode.c | 19 +++++++++++++++++-- modules/dmq/dmqnode.h | 1 + 2 files changed, 18 insertions(+), 2 deletions(-) diff --git a/modules/dmq/dmqnode.c b/modules/dmq/dmqnode.c index 18b053b..5ac3951 100644 --- a/modules/dmq/dmqnode.c +++ b/modules/dmq/dmqnode.c @@ -24,6 +24,7 @@ */ #include "../../ut.h" +#include "../../resolve.h" #include "dmqnode.h" #include "dmq.h" @@ -146,7 +147,11 @@ dmq_node_t* build_dmq_node(str* uri, int shm) { dmq_node_t* ret = NULL; param_hooks_t hooks; param_t* params; - + + /* For DNS-Lookups */ + static char hn[256]; + struct hostent* he; + LM_DBG("build_dmq_node %.*s with %s memory\n", STR_FMT(uri), shm?"shm":"private"); if(shm) { @@ -171,7 +176,7 @@ dmq_node_t* build_dmq_node(str* uri, int shm) { } } set_default_dmq_node_params(ret); - if(parse_uri(ret->orig_uri.s, ret->orig_uri.len, &ret->uri) < 0) { + if(parse_uri(ret->orig_uri.s, ret->orig_uri.len, &ret->uri) < 0 || ret->uri.host.len > 254) { LM_ERR("error parsing uri\n"); goto error; } @@ -199,6 +204,16 @@ dmq_node_t* build_dmq_node(str* uri, int shm) { } else { LM_DBG("no dmqnode params found\n"); } + /* resolve hostname */ + strncpy(hn, ret->uri.host.s, ret->uri.host.len); + hn[ret->uri.host.len]='\0'; + he=resolvehost(hn); + if (he==0) { + LM_ERR("could not resolve %.*s\n", ret->uri.host.len, ret->uri.host.s); + goto error; + } + hostent2ip_addr(&ret->ip_address, he, 0); + return ret; error: diff --git a/modules/dmq/dmqnode.h b/modules/dmq/dmqnode.h index dfe684d..10e2962 100644 --- a/modules/dmq/dmqnode.h +++ b/modules/dmq/dmqnode.h @@ -44,6 +44,7 @@ typedef struct dmq_node { int local; /* local type set means the dmq dmqnode == self */ str orig_uri; /* original uri string - e.g. sip:127.0.0.1:5060;passive=true */ struct sip_uri uri; /* parsed uri string */ + struct ip_addr ip_address; /* resolved IP address */ param_t* params; /* uri parameters */ int status; /* reserved - maybe something like active,timeout,disabled */ int last_notification; /* last notificatino receied from the node */

10 years, 2 months

git:master: modules/rtpengine: generated README

by Juha Heinanen

Module: sip-router Branch: master Commit: 1110d4e6b5ec2f949951c9433a80bced778272d9 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=1110d4e… Author: Juha Heinanen <jh(a)tutpro.com> Committer: Juha Heinanen <jh(a)tutpro.com> Date: Tue Sep 9 20:41:47 2014 +0300 modules/rtpengine: generated README --- modules/rtpengine/README | 75 ++++++++++++++++++++++++++++++--------------- 1 files changed, 50 insertions(+), 25 deletions(-) diff --git a/modules/rtpengine/README b/modules/rtpengine/README index 760ac4b..b38d92c 100644 --- a/modules/rtpengine/README +++ b/modules/rtpengine/README @@ -69,7 +69,7 @@ Richard Fuchs 5. Functions - 5.1. set_rtpengine_set(setid) + 5.1. set_rtpengine_set(setid[, setid]) 5.2. rtpengine_offer([flags]) 5.3. rtpengine_answer([flags]) 5.4. rtpengine_delete([flags]) @@ -127,7 +127,7 @@ Chapter 1. Admin Guide 5. Functions - 5.1. set_rtpengine_set(setid) + 5.1. set_rtpengine_set(setid[, setid]) 5.2. rtpengine_offer([flags]) 5.3. rtpengine_answer([flags]) 5.4. rtpengine_delete([flags]) @@ -298,20 +298,32 @@ modparam("rtpengine", "setid_avp", "$avp(setid)") 5. Functions - 5.1. set_rtpengine_set(setid) + 5.1. set_rtpengine_set(setid[, setid]) 5.2. rtpengine_offer([flags]) 5.3. rtpengine_answer([flags]) 5.4. rtpengine_delete([flags]) 5.5. rtpengine_manage([flags]) 5.6. start_recording() -5.1. set_rtpengine_set(setid) +5.1. set_rtpengine_set(setid[, setid]) Sets the ID of the RTP proxy set to be used for the next rtpengine_delete(), rtpengine_offer(), rtpengine_answer() or rtpengine_manage() command. The parameter can be an integer or a config variable holding an integer. + A second set ID can be specified to daisy-chain two RTP proxies. The + two set IDs must be distinct from each other and there must not be any + overlap in the proxies present in both sets. In this use case, the + request (offer, answer, etc) is first sent to an RTP proxy from the + first set, which rewrites the SDP body and sends it back to the module. + The rewritten SDP body is then used to make another request to an RTP + proxy from the second set, which rewrites the SDP body another time and + sends it back to the module to be placed back into the SIP message. + This is useful if you have a set of RTP proxies that the caller must + use, and another distinct set of RTP proxies that the callee must use. + This is supported by all rtpengine commands except rtpengine_manage(). + This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, BRANCH_ROUTE. @@ -324,8 +336,8 @@ rtpengine_offer(); 5.2. rtpengine_offer([flags]) Rewrites SDP body to ensure that media is passed through an RTP proxy. - To be invoked on INVITE for the cases the SDPs are in INVITE and 200 OK - and on 200 OK when SDPs are in 200 OK and ACK. + To be invoked on INVITE for the cases the SDP bodies are in INVITE and + 200 OK and on 200 OK when SDP bodies are in 200 OK and ACK. Meaning of the parameters is as follows: * flags - flags to turn on some features. @@ -351,24 +363,29 @@ rtpengine_offer(); "answer" for the new branch. This flag is only supported by the Sipwise rtpengine RTP proxy at the moment! + asymmetric - flags that UA from which message is received - doesn't support symmetric RTP. (automatically sets the 'r' - flag) + doesn't support symmetric RTP. Disables learning of endpoint + addresses in the Sipwise rtpengine proxy. + force-answer - force "answer", that is, only rewrite SDP when corresponding session already exists in the RTP proxy. By default is on when the session is to be completed. - + internal, external - these flags specify the direction of the - SIP message. These flags only make sense when the RTP proxy is - running in bridge mode. "internal" corresponds to the proxy's - first interface, "external" corresponds to the RTP proxy's - second interface. You always have to specify two flags to - define the incoming network and the outgoing network. For - example, "internal external" should be used for SIP message - received from the local interface and sent out on the external - interface, and "external internal" vice versa. Other options - are "internal internal" and "external external". So, for - example if a SIP requests is processed with "internal - external" flags, the corresponding response must be processed - with "internal external" flags. + + direction=... - this option specifies a logical network + interface and should be given exactly twice. It enables RTP + bridging between different addresses or networks of the same + family (e.g. IPv4 to IPv4). The first instance of the option + specifies the interface that the originator of this message + should be using, while the second instance specifies the + interface that the target should be using. For example, if the + SIP message was sent by an endpoint on a private network and + will be sent to an endpoint on the public internet, you would + use "direction=priv direction=pub" if those two logical + network interfaces were called "priv" and "pub" in your RTP + proxy's configuration respectively. The direction must only be + specified in for initial SDP offer; answers or subsequent + offers can omit this option. + + internal, external - shorthand for "direction=internal" and + "direction=external" respectively. Useful for brevity or as + legacy option if the RTP proxy only supports two network + interfaces instead of multiple, arbitrarily named ones. + auto-bridge - this flag an alternative to the "internal" and "external" flags in order to do automatic bridging between IPv4 on the "internal network" and IPv6 on the "external @@ -407,7 +424,8 @@ rtpengine_offer(); SDP connection (c=) IP if media description also includes connection information. + symmetric - flags that for the UA from which message is - received, support symmetric RTP must be forced. + received, support symmetric RTP must be forced. Does nothing + with the Sipwise rtpengine proxy as it is the default. + repacketize=NN - requests the RTP proxy to perform re-packetization of RTP traffic coming from the UA which has sent the current message to increase or decrease payload size @@ -424,7 +442,7 @@ rtpengine_offer(); attributes within the SDP body. Possible values are: "force" - discard any ICE attributes already present in the SDP body and then generate and insert new ICE data, leaving itself as the - only ICE candidates; "force_relay" - discard any "relay" type + only ICE candidates; "force-relay" - discard any "relay" type ICE attributes already present in the SDP body and then generate and insert itself as the only ICE "relay" candidates; "remove" instructs the RTP proxy to discard any ICE attributes @@ -469,6 +487,13 @@ rtpengine_offer(); + media-address=... - force a particular media address to be used in the SDP body. Address family is detected automatically. + + TOS=... - change the IP TOS value for all outgoing RTP packets + within the entire call in both directions. Only honoured in an + "offer", ignored for an "answer". Valid values are 0 through + 255, given in decimal. If this option is not specified, the + TOS value will revert to the default TOS (normally 184). A + value of -1 may be used to leave the currently used TOS + unchanged. This function can be used from ANY_ROUTE. @@ -507,8 +532,8 @@ onreply_route[2] 5.3. rtpengine_answer([flags]) Rewrites SDP body to ensure that media is passed through an RTP proxy. - To be invoked on 200 OK for the cases the SDPs are in INVITE and 200 OK - and on ACK when SDPs are in 200 OK and ACK. + To be invoked on 200 OK for the cases the SDP bodies are in INVITE and + 200 OK and on ACK when SDP bodies are in 200 OK and ACK. See rtpengine_offer() function description above for the meaning of the parameters.

10 years, 2 months

about rtpengine trust-address flag and "received from" key

by Juha Heinanen

i would like to return to rtpengine trust-address flag. README says: trust-address - flags that IP address in SDP should be trusted. Without this flag, the RTP proxy ignores address in the SDP and uses source address of the SIP message as media address which is passed to the RTP proxy. the first part makes sense, i.e., if the flag is present, then ip address in the sdp is trusted. the second part does not make sense to me and neither does "received from" key of request passed to rtpengine. rtpengine doc tells about "received from": Contains a list of exactly two elements. The first element denotes the address family and the second element is the SIP message's source address itself. The address family can be one of IP4 or IP6. Used if neither the trust address flag nor the media address key is present. there is at least two reasons why it does not make sense to pass source ip address of sip request to rtpengine: 1) the proxy that is calling rtpengine_offer() may not be the first hop proxy of the sip ua. 2) even when sip proxy is the first hop, sip ua may not use the same ip address for sip signaling and rtp media so what is the reason for the existence of "received from" key? is there anything lost if the key is removed? if not, then lets get rid of it in order to simplify things and to avoid confusion. -- juha

10 years, 2 months

git:master: modules/ims_qos: new mod_param: authorize_video_flow

by Richard Good

Module: sip-router Branch: master Commit: 0db2ee84ae1c24fae6196f42034c68e5d16ea189 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0db2ee8… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Tue Sep 9 18:26:02 2014 +0200 modules/ims_qos: new mod_param: authorize_video_flow authorize_video_flows is a flag that specifies whether or not to authorize video flows. --- modules/ims_qos/doc/ims_qos_admin.xml | 20 +++++++++++ modules/ims_qos/mod.c | 3 ++ modules/ims_qos/rx_aar.c | 61 ++++++++++++++++++++++----------- 3 files changed, 64 insertions(+), 20 deletions(-) diff --git a/modules/ims_qos/doc/ims_qos_admin.xml b/modules/ims_qos/doc/ims_qos_admin.xml index 43223c3..726e441 100644 --- a/modules/ims_qos/doc/ims_qos_admin.xml +++ b/modules/ims_qos/doc/ims_qos_admin.xml @@ -181,6 +181,26 @@ modparam("ims_qos", "cdp_event_latency_log", 1) </programlisting> </example> </section> + <section> + <title><varname>authorize_video_flow</varname> (integer)</title> + + <para>This is a flag that specifies whether or not to authorize video flows. + 1 means video flows will be authorized over Rx and + 0 means video flows will not be authorized over Rx</para> + + <para><emphasis> Default value is 1. </emphasis></para> + + <example> + <title><varname>authorize_video_flow</varname> parameter + usage</title> + + <programlisting format="linespecific"> +... +modparam("ims_qos", "authorize_video_flow", 0) +... + </programlisting> + </example> + </section> </section> <section> diff --git a/modules/ims_qos/mod.c b/modules/ims_qos/mod.c index b164136..3dc9496 100644 --- a/modules/ims_qos/mod.c +++ b/modules/ims_qos/mod.c @@ -85,6 +85,8 @@ int rx_auth_expiry = 7200; int must_send_str = 1; +int authorize_video_flow = 1; //by default we authorize resources for video flow descriptions + struct tm_binds tmb; struct cdp_binds cdpb; struct dlg_binds dlgb; @@ -128,6 +130,7 @@ static param_export_t params[] = { { "cdp_event_latency", INT_PARAM, &cdp_event_latency}, /*flag: report slow processing of CDP callback events or not */ { "cdp_event_threshold", INT_PARAM, &cdp_event_threshold}, /*time in ms above which we should report slow processing of CDP callback event*/ { "cdp_event_latency_log", INT_PARAM, &cdp_event_latency_loglevel}, /*log-level to use to report slow processing of CDP callback event*/ + { "authorize_video_flow", INT_PARAM, &authorize_video_flow}, /*whether or not we authorize resources for video flows*/ { 0, 0, 0} }; diff --git a/modules/ims_qos/rx_aar.c b/modules/ims_qos/rx_aar.c index 89e5323..028d6cd 100644 --- a/modules/ims_qos/rx_aar.c +++ b/modules/ims_qos/rx_aar.c @@ -71,6 +71,8 @@ //extern struct tm_binds tmb; usrloc_api_t ul; +extern int authorize_video_flow; + str IMS_Serv_AVP_val = {"IMS Services", 12}; str IMS_Em_Serv_AVP_val = {"Emergency IMS Call", 18}; str IMS_Reg_AVP_val = {"IMS Registration", 16}; @@ -323,20 +325,31 @@ int rx_process_aaa(AAAMessage *aaa, unsigned int * rc) { int add_media_components_using_current_flow_description(AAAMessage* aar, rx_authsessiondata_t *p_session_data) { flow_description_t *flow_description; + int add_flow = 1; flow_description = p_session_data->first_current_flow_description; if(!flow_description) { return -1; } while (flow_description) { - rx_add_media_component_description_avp(aar, flow_description->stream_num, - &flow_description->media, &flow_description->req_sdp_ip_addr, - &flow_description->req_sdp_port, &flow_description->rpl_sdp_ip_addr, - &flow_description->rpl_sdp_port, &flow_description->rpl_sdp_transport, - &flow_description->req_sdp_raw_stream, - &flow_description->rpl_sdp_raw_stream, flow_description->direction); + + if(!authorize_video_flow) { + if (strncmp(flow_description->media.s, "video", 5) == 0) { + add_flow = 0; + } + } + + if(add_flow) { + rx_add_media_component_description_avp(aar, flow_description->stream_num, + &flow_description->media, &flow_description->req_sdp_ip_addr, + &flow_description->req_sdp_port, &flow_description->rpl_sdp_ip_addr, + &flow_description->rpl_sdp_port, &flow_description->rpl_sdp_transport, + &flow_description->req_sdp_raw_stream, + &flow_description->rpl_sdp_raw_stream, flow_description->direction); + } flow_description = flow_description->next; + add_flow = 1; } return 0; } @@ -350,6 +363,7 @@ int add_media_components(AAAMessage* aar, struct sip_msg *req, int sdp_stream_num; sdp_session_cell_t* req_sdp_session, *rpl_sdp_session; sdp_stream_cell_t* req_sdp_stream, *rpl_sdp_stream; + int add_flow = 1; if (!req || !rpl) { return CSCF_RETURN_FALSE; @@ -402,22 +416,29 @@ int add_media_components(AAAMessage* aar, struct sip_msg *req, int intportA = atoi(req_sdp_stream->port.s); int intportB = atoi(rpl_sdp_stream->port.s); if(intportA != 0 && intportB != 0){ + if(!authorize_video_flow) { + if (strncmp(req_sdp_stream->media.s, "video", 5) == 0) { + add_flow = 0; + } + } + if(add_flow) { //add this to auth session data - - add_flow_description((rx_authsessiondata_t*) auth->u.auth.generic_data, sdp_stream_num + 1, - &req_sdp_stream->media, &req_sdp_session->ip_addr, - &req_sdp_stream->port, &rpl_sdp_session->ip_addr, - &rpl_sdp_stream->port, &rpl_sdp_stream->transport, - &req_sdp_stream->raw_stream, - &rpl_sdp_stream->raw_stream, direction, 0 /*This is a new mcd, we are not setting it as active*/); - - rx_add_media_component_description_avp(aar, sdp_stream_num + 1, - &req_sdp_stream->media, &req_sdp_session->ip_addr, - &req_sdp_stream->port, &rpl_sdp_session->ip_addr, - &rpl_sdp_stream->port, &rpl_sdp_stream->transport, - &req_sdp_stream->raw_stream, - &rpl_sdp_stream->raw_stream, direction); + add_flow_description((rx_authsessiondata_t*) auth->u.auth.generic_data, sdp_stream_num + 1, + &req_sdp_stream->media, &req_sdp_session->ip_addr, + &req_sdp_stream->port, &rpl_sdp_session->ip_addr, + &rpl_sdp_stream->port, &rpl_sdp_stream->transport, + &req_sdp_stream->raw_stream, + &rpl_sdp_stream->raw_stream, direction, 0 /*This is a new mcd, we are not setting it as active*/); + + rx_add_media_component_description_avp(aar, sdp_stream_num + 1, + &req_sdp_stream->media, &req_sdp_session->ip_addr, + &req_sdp_stream->port, &rpl_sdp_session->ip_addr, + &rpl_sdp_stream->port, &rpl_sdp_stream->transport, + &req_sdp_stream->raw_stream, + &rpl_sdp_stream->raw_stream, direction); + } + add_flow = 1; } } sdp_stream_num++;

10 years, 2 months

Re: [sr-dev] new module db_kazoo

by Luis Azedo

Hi Daniel, historically, it started with db_kazoo but over the time it was getting less related to db_ as we moved to a more generic module implementation. we already had the discussion internally and we agree that kazoo would be fine for renaming the module. we will rename db_kazoo to kazoo. Thanks

10 years, 2 months

git:master: modules/ims_qos: store AAR flow descriptions in CDP session

by Richard Good

Module: sip-router Branch: master Commit: e5c9f006060b5b4d00c9ab56f25521debee32216 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e5c9f00… Author: Richard Good <richard.good(a)smilecoms.com> Committer: Richard Good <richard.good(a)smilecoms.com> Date: Tue Sep 9 16:56:00 2014 +0200 modules/ims_qos: store AAR flow descriptions in CDP session When flow_descriptions are installed save the active and new This allows Rx to fallback to previous flow descriptions if there is an upstream failure --- modules/ims_qos/cdpeventprocessor.c | 3 +- modules/ims_qos/mod.c | 192 ++++++++++++++++++++++++++--- modules/ims_qos/mod.h | 2 +- modules/ims_qos/rx_aar.c | 236 ++++++++++++++++++++++++++++++++--- modules/ims_qos/rx_aar.h | 5 + modules/ims_qos/rx_authdata.c | 230 +++++++++++++++++++++++++++++++++- modules/ims_qos/rx_authdata.h | 26 ++++- 7 files changed, 652 insertions(+), 42 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=e5c…

10 years, 2 months

git:master: rtpengine: docs update

by Richard Fuchs

Module: sip-router Branch: master Commit: e6591dc75d34e8522060ea71148b4cdcae139234 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e6591dc… Author: Richard Fuchs <rfuchs(a)sipwise.com> Committer: Richard Fuchs <rfuchs(a)sipwise.com> Date: Tue Sep 9 10:37:53 2014 -0400 rtpengine: docs update --- modules/rtpengine/doc/rtpengine_admin.xml | 46 +++++++++++++++-------------- 1 files changed, 24 insertions(+), 22 deletions(-) diff --git a/modules/rtpengine/doc/rtpengine_admin.xml b/modules/rtpengine/doc/rtpengine_admin.xml index 7907fb5..fdc9a2d 100644 --- a/modules/rtpengine/doc/rtpengine_admin.xml +++ b/modules/rtpengine/doc/rtpengine_admin.xml @@ -288,8 +288,8 @@ rtpengine_offer(); <para> Rewrites &sdp; body to ensure that media is passed through an &rtp; proxy. To be invoked - on INVITE for the cases the SDPs are in INVITE and 200 OK and on 200 OK - when SDPs are in 200 OK and ACK. + on INVITE for the cases the &sdp; bodies are in INVITE and 200 OK and on 200 OK + when &sdp; bodies are in 200 OK and ACK. </para> <para>Meaning of the parameters is as follows:</para> <itemizedlist> @@ -325,7 +325,8 @@ rtpengine_offer(); </para></listitem> <listitem><para> <emphasis>asymmetric</emphasis> - flags that UA from which message is - received doesn't support symmetric RTP. (automatically sets the 'r' flag) + received doesn't support symmetric &rtp;. Disables learning of endpoint addresses + in the Sipwise rtpengine proxy. </para></listitem> <listitem><para> <emphasis>force-answer</emphasis> - force <quote>answer</quote>, that is, @@ -359,8 +360,8 @@ rtpengine_offer(); in order to do automatic bridging between IPv4 on the "internal network" and IPv6 on the "external network". Instead of explicitly instructing the &rtp; proxy to select a particular address - family, the distinction is done by the given IP in the SDP body by - the RTP proxy itself. Not supported by Sipwise rtpengine. + family, the distinction is done by the given IP in the &sdp; body by + the &rtp; proxy itself. Not supported by Sipwise rtpengine. </para></listitem> <listitem><para> <emphasis>address-family=...</emphasis> - instructs the &rtp; proxy that the @@ -387,10 +388,10 @@ rtpengine_offer(); a chain of proxies. Not supported and ignored by Sipwise rtpengine. </para></listitem> <listitem><para> - <emphasis>trust-address</emphasis> - flags that IP address in SDP should + <emphasis>trust-address</emphasis> - flags that IP address in &sdp; should be trusted. Without this flag, the &rtp; proxy ignores address in - the SDP and uses source address of the &sip; message as media - address which is passed to the RTP proxy. + the &sdp; and uses source address of the &sip; message as media + address which is passed to the &rtp; proxy. </para></listitem> <listitem><para> <emphasis>replace-origin</emphasis> - flags that IP from the origin @@ -398,18 +399,19 @@ rtpengine_offer(); </para></listitem> <listitem><para> <emphasis>replace-session-connection</emphasis> - flags to change the session-level - SDP connection (c=) IP if media description also includes + &sdp; connection (c=) IP if media description also includes connection information. </para></listitem> <listitem><para> <emphasis>symmetric</emphasis> - flags that for the UA from which - message is received, support symmetric RTP must be forced. + message is received, support symmetric &rtp; must be forced. Does nothing with + the Sipwise rtpengine proxy as it is the default. </para></listitem> <listitem><para> <emphasis>repacketize=NN</emphasis> - requests the &rtp; proxy to perform - re-packetization of RTP traffic coming from the UA which + re-packetization of &rtp; traffic coming from the UA which has sent the current message to increase or decrease payload - size per each RTP packet forwarded if possible. The NN is the + size per each &rtp; packet forwarded if possible. The NN is the target payload size in ms, for the most codecs its value should be in 10ms increments, however for some codecs the increment could differ (e.g. 30ms for GSM or 20ms for G.723). The @@ -426,7 +428,7 @@ rtpengine_offer(); discard any ICE attributes already present in the &sdp; body and then generate and insert new ICE data, leaving itself as the <emphasis>only</emphasis> ICE candidates; - <quote>force_relay</quote> - + <quote>force-relay</quote> - discard any <quote>relay</quote> type ICE attributes already present in the &sdp; body and then generate and insert itself as the <emphasis>only</emphasis> ICE <quote>relay</quote> candidates; @@ -488,7 +490,7 @@ rtpengine_offer(); be used in the &sdp; body. Address family is detected automatically. </para></listitem> <listitem><para> - <emphasis>TOS=...</emphasis> - change the IP TOS value for all outgoing RTP + <emphasis>TOS=...</emphasis> - change the IP TOS value for all outgoing &rtp; packets within the entire call in both directions. Only honoured in an <quote>offer</quote>, ignored for an <quote>answer</quote>. Valid values are 0 through 255, given in decimal. If this option is not specified, the TOS @@ -544,8 +546,8 @@ onreply_route[2] <para> Rewrites &sdp; body to ensure that media is passed through an &rtp; proxy. To be invoked - on 200 OK for the cases the SDPs are in INVITE and 200 OK and on ACK - when SDPs are in 200 OK and ACK. + on 200 OK for the cases the &sdp; bodies are in INVITE and 200 OK and on ACK + when &sdp; bodies are in 200 OK and ACK. </para> <para> See rtpengine_offer() function description above for the meaning of the @@ -606,19 +608,19 @@ rtpengine_delete(); <itemizedlist> <listitem> <para> - If INVITE with SDP, then do <function>rtpengine_offer()</function> + If INVITE with &sdp;, then do <function>rtpengine_offer()</function> </para> </listitem> <listitem> <para> - If INVITE with SDP, when the tm module is loaded, mark transaction with + If INVITE with &sdp;, when the tm module is loaded, mark transaction with internal flag FL_SDP_BODY to know that the 1xx and 2xx are for <function>rtpengine_answer()</function> </para> </listitem> <listitem> <para> - If ACK with SDP, then do <function>rtpengine_answer()</function> + If ACK with &sdp;, then do <function>rtpengine_answer()</function> </para> </listitem> <listitem> @@ -633,8 +635,8 @@ rtpengine_delete(); </listitem> <listitem> <para> - If reply with SDP to INVITE having code 1xx and 2xx, then - do <function>rtpengine_answer()</function> if the request had SDP or tm is not loaded, + If reply with &sdp; to INVITE having code 1xx and 2xx, then + do <function>rtpengine_answer()</function> if the request had &sdp; or tm is not loaded, otherwise do <function>rtpengine_offer()</function> </para> </listitem> @@ -659,7 +661,7 @@ rtpengine_manage(); </title> <para> This function will send a signal to the &rtp; proxy to record - the RTP stream on the &rtp; proxy. + the &rtp; stream on the &rtp; proxy. <emphasis>This function is not supported by Sipwise rtpengine at the moment!</emphasis> </para> <para>

10 years, 2 months

← Newer
1
...
21
22
23
24
25
26
27
...
38
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev September 2014