sr-dev March 2014

sr-dev@lists.kamailio.org

29 participants
298 discussions

Stuck dialogs
by Alex Balashov 17 Apr '14

17 Apr '14

With 4.1, I've got a call scenario that looks like this: 1. INVITE --> 2. <-- 100 3. <-- 183 4. <-- 200 OK 5. <-- 200 OK again (no ACK from near end) 6. Finally an e2e ACK comes through --> 7. (38 seconds later) BYE --> 8. (no response to BYE) BYE --> 9. BYE --> 10. BYE --> 11. BYE --> 12. BYE --> 13. BYE --> etc. I've also got another call that looks very similarly, except that the BYE comes from the callee instead of the caller. It also goes unanswered by the near end. I am tracking both dialogs with 'dialog', and, sooner or later, they end up in DELETED state. However, they do not get deleted. I have one that has been in there for 4 days and isn't going anywhere, and another that has been stuck in DELETED state for 3. My dialog timeout is set to 4 hours, but the timeout operation doesn't delete dialogs that are already DELETED. Moreover, dlg_end_dlg is not a means of removing these dialogs, either: [root@gw1 ~]# kamctl fifo dlg_end_dlg 154 6753 500 Operation failed Any suggestions on what to do here? Should this be considered a bug? Thanks, -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/

3 5

[tracker] Comment added: tls: ssl bug #1491 workaround: not enough memory for safe operation
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#414 - tls: ssl bug #1491 workaround: not enough memory for safe operation User who did this - Jose Luis Verdeguer (pepelux) ---------- I increased the shm memory to 512Mb. I'll analyze and I'll send feedback Thanks ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=414#comment1377 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.

1 0

[tracker] Comment added: carrierroute not loading with kamailio 4.0.x
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#353 - carrierroute not loading with kamailio 4.0.x User who did this - Oli Roth (kolibri99) ---------- Hi Daniel It seems to be "loadable" using your provided url. The only thing I had to do is update the address table to verion 6 / before version 5 Now we will perform some tests You mentioned a patch you applied. Can I do this by myself with the newest kamailio versions? If I got you right you will apply this patch to the next stable kamailio verision - correct? Kind Regards, Oli ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=353#comment1376 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.

1 0

[tracker] Comment added: carrierroute not loading with kamailio 4.0.x
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#353 - carrierroute not loading with kamailio 4.0.x User who did this - Oli Roth (kolibri99) ---------- Hi Daniel I just upgraded to the lastest kamailio release version: kamailio 4.1.2 (x86_64/linux) As it seems it still does not work: * 0(32002) ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so: undefined symbol: cfg_set_error_functio 0(32002) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find command cr_user_carrier 0(32002) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 1109, column 67: unknown command, missing loadmodule? Should I use kamailio 4.0.x instead of 4.1.x? Thanks for reply ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=353#comment1375 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.

1 0

[tracker] Comment added: carrierroute not loading with kamailio 4.0.x
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#353 - carrierroute not loading with kamailio 4.0.x User who did this - Carsten Bock (carstenbock) ---------- You can use our repository as described here: http://www.kamailio.org/wiki/tutorials/ims/installation-howto Out "ims" repository contains a current stable 4.1 with some handpicked patches from current master (e.g. this patch), which we use or plan to use in our own setups. If no-one objects, i could apply the changes to current 4.1 and 4.0; but actually i wanted to leave this to the "original" developers of the Carrierroute module. Kind regards, Carsten ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=353#comment1374 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.

1 0

[tracker] Comment added: carrierroute not loading with kamailio 4.0.x
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#353 - carrierroute not loading with kamailio 4.0.x User who did this - Daniel-Constantin Mierla (miconda) ---------- The commit was only on master branch, it will be in next major release 4.2. I understood it is due to a change in the libconfuse api, not sure 4.0 will help at all. What you can do is to run the module from master in 4.1 (you can cherry pick the commits or simply copy over). You can write to sr-dev mailing list and ask about the plans for the module -- i am not its developer, nor using it. I noticed the patch and closed the task. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=353#comment1373 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.

1 0

[tracker] Comment added: carrierroute not loading with kamailio 4.0.x
by sip-router 31 Mar '14

31 Mar '14

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#353 - carrierroute not loading with kamailio 4.0.x User who did this - Oli Roth (kolibri99) ---------- Hi Daniel I just upgraded to the lastest kamailio release version: kamailio 4.1.2 (x86_64/linux) As it seems it still does not work: * 0(32002) ERROR: <core> [sr_module.c:599]: load_module(): ERROR: load_module: could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so: undefined symbol: cfg_set_error_functio 0(32002) ERROR: <core> [cfg.y:3272]: yyparse(): cfg. parser: failed to find command cr_user_carrier 0(32002) : <core> [cfg.y:3411]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 1109, column 67: unknown command, missing loadmodule? Should I use kamailio 4.0.x instead of 4.1.x? Thanks for reply ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=353#comment1372 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.

1 0

git:master: evapi: fixed c&p typo in example
by Daniel-Constantin Mierla 31 Mar '14

31 Mar '14

Module: sip-router Branch: master Commit: 77e2c6beb250726f8bc5dec5d71ec175264e0c0f URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=77e2c6b… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Mar 31 09:48:58 2014 +0200 evapi: fixed c&p typo in example --- modules/evapi/README | 2 +- modules/evapi/doc/evapi_admin.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/evapi/README b/modules/evapi/README index 97e0390..4b8ff72 100644 --- a/modules/evapi/README +++ b/modules/evapi/README @@ -218,7 +218,7 @@ event_route[evapi:connection-closed] { If defined, the module calls event_route[evapi:message-received] when a message is received from a client. ... -event_route[evapi:connection-closed] { +event_route[evapi:message-received] { xlog("received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); } ... diff --git a/modules/evapi/doc/evapi_admin.xml b/modules/evapi/doc/evapi_admin.xml index ae78e2d..fe1ac94 100644 --- a/modules/evapi/doc/evapi_admin.xml +++ b/modules/evapi/doc/evapi_admin.xml @@ -226,7 +226,7 @@ event_route[evapi:connection-closed] { </para> <programlisting format="linespecific"> ... -event_route[evapi:connection-closed] { +event_route[evapi:message-received] { xlog("received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); } ...

1 0

git:master: evapi: docs updated with evapi_close(), new event routes and pvs
by Daniel-Constantin Mierla 31 Mar '14

31 Mar '14

Module: sip-router Branch: master Commit: 193f27a0da5e2e3da7737da0bd7b035912be59d5 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=193f27a… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Mar 31 09:41:17 2014 +0200 evapi: docs updated with evapi_close(), new event routes and pvs --- modules/evapi/README | 82 ++++++++++++++++++++++++++++++ modules/evapi/doc/evapi_admin.xml | 99 +++++++++++++++++++++++++++++++++++++ 2 files changed, 181 insertions(+), 0 deletions(-) diff --git a/modules/evapi/README b/modules/evapi/README index dfec149..97e0390 100644 --- a/modules/evapi/README +++ b/modules/evapi/README @@ -32,6 +32,15 @@ Daniel-Constantin Mierla 4.1. evapi_relay(evdata) 4.2. evapi_async_relay(evdata) + 4.3. evapi_close() + + 5. Event routes + + 5.1. evapi:connection-new + 5.2. evapi:connection-closed + 5.3. evapi:message-received + + 6. Exported pseudo-variables List of Examples @@ -40,6 +49,7 @@ Daniel-Constantin Mierla 1.3. evapi_relay usage 1.4. TCP message 1.5. evapi_async_relay usage + 1.6. evapi_evapi usage Chapter 1. Admin Guide @@ -60,6 +70,15 @@ Chapter 1. Admin Guide 4.1. evapi_relay(evdata) 4.2. evapi_async_relay(evdata) + 4.3. evapi_close() + + 5. Event routes + + 5.1. evapi:connection-new + 5.2. evapi:connection-closed + 5.3. evapi:message-received + + 6. Exported pseudo-variables 1. Overview @@ -113,6 +132,7 @@ modparam("evapi", "bind_addr", "1.2.3.4:8228") 4.1. evapi_relay(evdata) 4.2. evapi_async_relay(evdata) + 4.3. evapi_close() 4.1. evapi_relay(evdata) @@ -150,3 +170,65 @@ evapi_relay("{ \"event\": \"test\",\n \"data\": { \"fU\": \"$fU\" }\n}"); evapi_relay("{ \"event\": \"suspend\",\n \"data\":" " { \"index\": \"$T(id_index)\", \"label\": \"$T(id_label)\" }\n}"); ... + +4.3. evapi_close() + + Close evapi current client connection. + + This function can be used from ANY_ROUTE. + + Example 1.6. evapi_evapi usage +... +event_route[evapi:connection-new] { + if($evapi(srcaddr)!="127.0.0.1") { + evapi_close(); + exit; + } +} +... + +5. Event routes + + 5.1. evapi:connection-new + 5.2. evapi:connection-closed + 5.3. evapi:message-received + +5.1. evapi:connection-new + + If defined, the module calls event_route[evapi:connection-new] when a + new client is connected. +... +event_route[evapi:connection-new] { + xlog("new connection from $evapi(srcaddr):$evapi(srcport)\n"); +} +... + +5.2. evapi:connection-closed + + If defined, the module calls event_route[evapi:connection-closed] when + a client connection is closed. +... +event_route[evapi:connection-closed] { + xlog("connection closed by $evapi(srcaddr):$evapi(srcport)\n"); +} +... + +5.3. evapi:message-received + + If defined, the module calls event_route[evapi:message-received] when a + message is received from a client. +... +event_route[evapi:connection-closed] { + xlog("received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); +} +... + +6. Exported pseudo-variables + + * $evapi(srcaddr) - source ip + * $evapi(srcport) - source port + * $evapi(msg) - received event message + * $evapi(conidx) - internal connexion index + + Exported pseudo-variables are documented at + http://www.kamailio.org/wiki/. diff --git a/modules/evapi/doc/evapi_admin.xml b/modules/evapi/doc/evapi_admin.xml index 4015b8c..ae78e2d 100644 --- a/modules/evapi/doc/evapi_admin.xml +++ b/modules/evapi/doc/evapi_admin.xml @@ -155,6 +155,105 @@ evapi_relay("{ \"event\": \"suspend\",\n \"data\":" </example> </section> + <section id="evapi.f.evapi_close"> + <title> + <function moreinfo="none">evapi_close()</function> + </title> + <para> + Close evapi current client connection. + </para> + <para> + This function can be used from ANY_ROUTE. + </para> + <example> + <title><function>evapi_evapi</function> usage</title> + <programlisting format="linespecific"> +... +event_route[evapi:connection-new] { + if($evapi(srcaddr)!="127.0.0.1") { + evapi_close(); + exit; + } +} +... +</programlisting> + </example> + </section> + + </section> + + <section> + <title>Event routes</title> + <section> + <title> + <function moreinfo="none">evapi:connection-new</function> + </title> + <para> + If defined, the module calls event_route[evapi:connection-new] + when a new client is connected. + </para> + <programlisting format="linespecific"> +... +event_route[evapi:connection-new] { + xlog("new connection from $evapi(srcaddr):$evapi(srcport)\n"); +} +... + </programlisting> + </section> + <section> + <title> + <function moreinfo="none">evapi:connection-closed</function> + </title> + <para> + If defined, the module calls event_route[evapi:connection-closed] + when a client connection is closed. + </para> + <programlisting format="linespecific"> +... +event_route[evapi:connection-closed] { + xlog("connection closed by $evapi(srcaddr):$evapi(srcport)\n"); +} +... + </programlisting> + </section> + <section> + <title> + <function moreinfo="none">evapi:message-received</function> + </title> + <para> + If defined, the module calls event_route[evapi:message-received] + when a message is received from a client. + </para> + <programlisting format="linespecific"> +... +event_route[evapi:connection-closed] { + xlog("received [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); +} +... + </programlisting> + </section> + </section> + + <section> + <title>Exported pseudo-variables</title> + <itemizedlist> + <listitem><para> + <emphasis>$evapi(srcaddr)</emphasis> - source ip + </para></listitem> + <listitem><para> + <emphasis>$evapi(srcport)</emphasis> - source port + </para></listitem> + <listitem><para> + <emphasis>$evapi(msg)</emphasis> - received event message + </para></listitem> + <listitem><para> + <emphasis>$evapi(conidx)</emphasis> - internal connexion index + </para></listitem> + </itemizedlist> + <para> + Exported pseudo-variables are documented at &kamwikilink;. + </para> </section> + </chapter>

1 0

git:master: evapi: pass local env via sip msg structure
by Daniel-Constantin Mierla 31 Mar '14

31 Mar '14

Module: sip-router Branch: master Commit: b78239c7b389f871b8489fddc3a5a2988be460ec URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b78239c… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Mon Mar 31 09:18:22 2014 +0200 evapi: pass local env via sip msg structure --- modules/evapi/evapi_dispatch.c | 83 ++++++++++++++++++++++------------------ modules/evapi/evapi_dispatch.h | 6 +++ 2 files changed, 52 insertions(+), 37 deletions(-) diff --git a/modules/evapi/evapi_dispatch.c b/modules/evapi/evapi_dispatch.c index fadf886..72add89 100644 --- a/modules/evapi/evapi_dispatch.c +++ b/modules/evapi/evapi_dispatch.c @@ -66,15 +66,15 @@ typedef struct _evapi_evroutes { static evapi_evroutes_t _evapi_rts; -static evapi_env_t _evapi_env_data; - /** * */ -void evapi_env_reset(void) +void evapi_env_reset(evapi_env_t *evenv) { - memset(&_evapi_env_data, 0, sizeof(evapi_env_t)); - _evapi_env_data.conidx = -1; + if(evenv==0) + return; + memset(evenv, 0, sizeof(evapi_env_t)); + evenv->conidx = -1; } /** @@ -83,7 +83,6 @@ void evapi_env_reset(void) void evapi_init_event_routes(void) { memset(&_evapi_rts, 0, sizeof(evapi_evroutes_t)); - evapi_env_reset(); _evapi_rts.con_new = route_get(&event_rt, "evapi:connection-new"); if (_evapi_rts.con_new < 0 || event_rt.rlist[_evapi_rts.con_new] == NULL) @@ -99,13 +98,14 @@ void evapi_init_event_routes(void) /** * */ -int evapi_run_cfg_route(int rt) +int evapi_run_cfg_route(evapi_env_t *evenv, int rt) { int backup_rt; struct run_act_ctx ctx; sip_msg_t *fmsg; + sip_msg_t tmsg; - if(_evapi_env_data.eset==0) { + if(evenv==0 || evenv->eset==0) { LM_ERR("evapi env not set\n"); return -1; } @@ -114,26 +114,30 @@ int evapi_run_cfg_route(int rt) return 0; fmsg = faked_msg_next(); + memcpy(&tmsg, fmsg, sizeof(sip_msg_t)); + fmsg = &tmsg; + evapi_set_msg_env(fmsg, evenv); backup_rt = get_route_type(); set_route_type(REQUEST_ROUTE); init_run_actions_ctx(&ctx); run_top_route(event_rt.rlist[rt], fmsg, 0); set_route_type(backup_rt); + evapi_set_msg_env(fmsg, NULL); return 0; } /** * */ -int evapi_cfg_close_connection(void) +int evapi_cfg_close_connection(int cidx) { - if(_evapi_env_data.conidx<0 || _evapi_env_data.conidx>=EVAPI_MAX_CLIENTS) + if(cidx<0 || cidx>=EVAPI_MAX_CLIENTS) return -1; - if(_evapi_clients[_evapi_env_data.conidx].connected==1 - && _evapi_clients[_evapi_env_data.conidx].sock > 0) { - close(_evapi_clients[_evapi_env_data.conidx].sock); - _evapi_clients[_evapi_env_data.conidx].connected = 0; - _evapi_clients[_evapi_env_data.conidx].sock = 0; + if(_evapi_clients[cidx].connected==1 + && _evapi_clients[cidx].sock > 0) { + close(_evapi_clients[cidx].sock); + _evapi_clients[cidx].connected = 0; + _evapi_clients[cidx].sock = 0; return 0; } return -2; @@ -203,6 +207,7 @@ void evapi_recv_client(struct ev_loop *loop, struct ev_io *watcher, int revents) char rbuffer[CLIENT_BUFFER_SIZE]; ssize_t rlen; int i; + evapi_env_t evenv; if(EV_ERROR & revents) { perror("received invalid event\n"); @@ -227,12 +232,12 @@ void evapi_recv_client(struct ev_loop *loop, struct ev_io *watcher, int revents) return; } + evapi_env_reset(&evenv); if(rlen == 0) { /* client is gone */ - _evapi_env_data.eset = 1; - _evapi_env_data.conidx = i; - evapi_run_cfg_route(_evapi_rts.con_closed); - evapi_env_reset(); + evenv.eset = 1; + evenv.conidx = i; + evapi_run_cfg_route(&evenv, _evapi_rts.con_closed); _evapi_clients[i].connected = 0; _evapi_clients[i].sock = 0; ev_io_stop(loop, watcher); @@ -247,12 +252,11 @@ void evapi_recv_client(struct ev_loop *loop, struct ev_io *watcher, int revents) LM_NOTICE("{%d} [%s:%d] - received [%.*s]\n", i, _evapi_clients[i].src_addr, _evapi_clients[i].src_port, (int)rlen, rbuffer); - _evapi_env_data.conidx = i; - _evapi_env_data.msg.s = rbuffer; - _evapi_env_data.msg.len = rlen; - _evapi_env_data.eset = 1; - evapi_run_cfg_route(_evapi_rts.msg_received); - evapi_env_reset(); + evenv.conidx = i; + evenv.msg.s = rbuffer; + evenv.msg.len = rlen; + evenv.eset = 1; + evapi_run_cfg_route(&evenv, _evapi_rts.msg_received); } /** @@ -265,6 +269,7 @@ void evapi_accept_client(struct ev_loop *loop, struct ev_io *watcher, int revent int csock; struct ev_io *evapi_client; int i; + evapi_env_t evenv; evapi_client = (struct ev_io*) malloc (sizeof(struct ev_io)); if(evapi_client==NULL) { @@ -320,10 +325,10 @@ void evapi_accept_client(struct ev_loop *loop, struct ev_io *watcher, int revent LM_DBG("new connection - pos[%d] from: [%s:%d]\n", i, _evapi_clients[i].src_addr, _evapi_clients[i].src_port); - _evapi_env_data.conidx = i; - _evapi_env_data.eset = 1; - evapi_run_cfg_route(_evapi_rts.con_new); - evapi_env_reset(); + evapi_env_reset(&evenv); + evenv.conidx = i; + evenv.eset = 1; + evapi_run_cfg_route(&evenv, _evapi_rts.con_new); if(_evapi_clients[i].connected == 0) return; @@ -564,30 +569,34 @@ error: */ int pv_get_evapi(sip_msg_t *msg, pv_param_t *param, pv_value_t *res) { + evapi_env_t *evenv; + if(param==NULL || res==NULL) return -1; - if(_evapi_env_data.conidx<0 || _evapi_env_data.conidx>=EVAPI_MAX_CLIENTS) + evenv = (evapi_env_t*)msg->date; + + if(evenv==NULL || evenv->conidx<0 || evenv->conidx>=EVAPI_MAX_CLIENTS) return pv_get_null(msg, param, res); - if(_evapi_clients[_evapi_env_data.conidx].connected==0 - && _evapi_clients[_evapi_env_data.conidx].sock <= 0) + if(_evapi_clients[evenv->conidx].connected==0 + && _evapi_clients[evenv->conidx].sock <= 0) return pv_get_null(msg, param, res); switch(param->pvn.u.isname.name.n) { case 0: - return pv_get_sintval(msg, param, res, _evapi_env_data.conidx); + return pv_get_sintval(msg, param, res, evenv->conidx); case 1: - if(_evapi_env_data.msg.s==NULL) + if(evenv->msg.s==NULL) return pv_get_null(msg, param, res); - return pv_get_strval(msg, param, res, &_evapi_env_data.msg); + return pv_get_strval(msg, param, res, &evenv->msg); case 2: return pv_get_strzval(msg, param, res, - _evapi_clients[_evapi_env_data.conidx].src_addr); + _evapi_clients[evenv->conidx].src_addr); case 3: return pv_get_sintval(msg, param, res, - _evapi_clients[_evapi_env_data.conidx].src_port); + _evapi_clients[evenv->conidx].src_port); default: return pv_get_null(msg, param, res); } diff --git a/modules/evapi/evapi_dispatch.h b/modules/evapi/evapi_dispatch.h index 4614beb..ff49946 100644 --- a/modules/evapi/evapi_dispatch.h +++ b/modules/evapi/evapi_dispatch.h @@ -44,4 +44,10 @@ int pv_get_evapi(sip_msg_t *msg, pv_param_t *param, pv_value_t *res); int pv_set_evapi(sip_msg_t *msg, pv_param_t *param, int op, pv_value_t *val); +/* set evapi env to shortcut of hdr date - not used in faked msg */ +#define evapi_set_msg_env(_msg, _evenv) do { _msg->date=(hdr_field_t*)_evenv; } while(0) +#define evapi_get_msg_env(_msg) ((evapi_env_t*)_msg->date) + +int evapi_cfg_close_connection(int cidx); + #endif

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev March 2014