Re: [SR-Users] t_precheck_trans
It's a function of TMX module. http://www.kamailio.org/docs/modules/4.4.x/modules/tmx.html#tmx.f.t_precheck_trans Best regards. Julia. On Fri, Jan 6, 2017 at 7:55 PM, Annus Fictus <annusfic...@gmail.com> wrote: > Hi, > > where can I find documentation for this function present on the default > script? > > In TM module not exist (Kamailio 4.4.4) > > Thank you > > Regards > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 4.4 segmentation fault when dp_translate match dialplan with ftmatch operator and empty match expression
Hello Daniel,
I haven't internet assess in our LAB kamailio,
I just applied your last commit3a48835cf68f583ff2fbd7cec9bd76ddc0a1b6fc
and now It's working.
(Tested for empty match_exp with match_op 1 and 2)
Thank you so much!
Julia
On Tue, Dec 20, 2016 at 9:38 AM, Daniel-Constantin Mierla <mico...@gmail.com
> wrote:
> Hello,
>
> thanks, it helped and hopefully it is not fixed in master and 4.4
> branches? Can you try fetching from git repository and see all ok now?
>
> Cheers,
> Daniel
>
> On 20/12/2016 06:56, Julia Boudniatsky wrote:
>
> Hello,
>
> (gdb) frame 2
> #2 0x7f7dca44d21a in translate (msg=0x7f7dd00bedd8, input=...,
> output=0x7fff32793420, idp=0x7f7cc9376648, attrs=0x7fff32793410)
> at dp_repl.c:636
> 636 rez = fnmatch(rulep->match_exp.s,
> input.s, 0);
> (gdb) list
> 631
> 632 case DP_FNMATCH_OP:
> 633 LM_DBG("fnmatch operator
> testing\n");
> 634 b = input.s[input.len];
> 635 input.s[input.len] = '\0';
> 636 rez = fnmatch(rulep->match_exp.s,
> input.s, 0);
> 637 input.s[input.len] = b;
> 638 rez = (rez==0)?0:-1;
> 639 break;
> 640
>
> Thank you,
> Julia
>
> On Mon, Dec 19, 2016 at 10:46 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> I mistakenly pointed to a wrong frame, can you do it again for frame 2?
>> frame 2
>> list
>>
>> Cheers,
>> Daniel
>>
>>
>> On 19/12/2016 21:28, Julia Boudniatsky wrote:
>>
>> Hello Daniel,
>>
>> Thank you for reply.
>>
>>
>> Program terminated with signal 11, Segmentation fault.
>> #0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
>> Missing separate debuginfos, use: debuginfo-install
>> MySQL-shared-5.5.27-1.el6.x86_64 glibc-2.12-1.47.el6.x86_64
>> libgcc-4.4.6-3.el6.x86_64 libuuid-2.17.2-12.4.el6.x86_64
>> pcre-7.8-3.1.el6.x86_64
>> (gdb) frame 0
>> #0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
>> (gdb) list
>> 1834int proto;
>> 1835char *options;
>> 1836int ret;
>> 1837unsigned int seed;
>> 1838int rfd;
>> 1839int debug_save, debug_flag;
>> 1840int dont_fork_cnt;
>> 1841struct name_lst* n_lst;
>> 1842char *p;
>> 1843struct stat st = {0};
>>
>> Best regards.
>>
>> Julia
>>
>>
>>
>>
>>
>> On Mon, Dec 19, 2016 at 8:38 PM, Daniel-Constantin Mierla <
>> mico...@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> can you give the output in gdb for:
>>>
>>> frame 0
>>> list
>>>
>>> The head of 4.4 branch got some extra commits to the module and those
>>> commands help to identify the right lines of code.
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 19/12/2016 13:47, Julia Boudniatsky wrote:
>>>
>>> version: kamailio 4.4.4 id:852c47
>>>
>>> ENTRY: {
>>> PRIO: 16765956
>>> MATCHOP: 2
>>> *MATCHEXP: *
>>> MATCHLEN: 0
>>> SUBSTEXP:
>>> REPLEXP:
>>> ATTRS: 1
>>> }
>>>
>>> Please see generated core file in extension.
>>>
>>> Thank you,
>>> Julia.
>>>
>>>
>>> ___
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>> --
>>> Daniel-Constantin Mierlawww.twitter.com/miconda --
>>> www.linkedin.com/in/miconda
>>> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>>>
>>> ___ SIP Express Router
>>> (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org http://lists.sip-router.org/cg
>>> i-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierlawww.twitter.com/miconda --
>> www.linkedin.com/in/miconda
>> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>>
>> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 4.4 segmentation fault when dp_translate match dialplan with ftmatch operator and empty match expression
Hello,
(gdb) frame 2
#2 0x7f7dca44d21a in translate (msg=0x7f7dd00bedd8, input=...,
output=0x7fff32793420, idp=0x7f7cc9376648, attrs=0x7fff32793410)
at dp_repl.c:636
636 rez = fnmatch(rulep->match_exp.s,
input.s, 0);
(gdb) list
631
632 case DP_FNMATCH_OP:
633 LM_DBG("fnmatch operator
testing\n");
634 b = input.s[input.len];
635 input.s[input.len] = '\0';
636 rez = fnmatch(rulep->match_exp.s,
input.s, 0);
637 input.s[input.len] = b;
638 rez = (rez==0)?0:-1;
639 break;
640
Thank you,
Julia
On Mon, Dec 19, 2016 at 10:46 PM, Daniel-Constantin Mierla <
mico...@gmail.com> wrote:
> Hello,
>
> I mistakenly pointed to a wrong frame, can you do it again for frame 2?
> frame 2
> list
>
> Cheers,
> Daniel
>
>
> On 19/12/2016 21:28, Julia Boudniatsky wrote:
>
> Hello Daniel,
>
> Thank you for reply.
>
>
> Program terminated with signal 11, Segmentation fault.
> #0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> MySQL-shared-5.5.27-1.el6.x86_64 glibc-2.12-1.47.el6.x86_64
> libgcc-4.4.6-3.el6.x86_64 libuuid-2.17.2-12.4.el6.x86_64
> pcre-7.8-3.1.el6.x86_64
> (gdb) frame 0
> #0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
> (gdb) list
> 1834int proto;
> 1835char *options;
> 1836int ret;
> 1837unsigned int seed;
> 1838int rfd;
> 1839int debug_save, debug_flag;
> 1840int dont_fork_cnt;
> 1841 struct name_lst* n_lst;
> 1842char *p;
> 1843struct stat st = {0};
>
> Best regards.
>
> Julia
>
>
>
>
>
> On Mon, Dec 19, 2016 at 8:38 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
>
>> Hello,
>>
>> can you give the output in gdb for:
>>
>> frame 0
>> list
>>
>> The head of 4.4 branch got some extra commits to the module and those
>> commands help to identify the right lines of code.
>>
>> Cheers,
>> Daniel
>>
>> On 19/12/2016 13:47, Julia Boudniatsky wrote:
>>
>> version: kamailio 4.4.4 id:852c47
>>
>> ENTRY: {
>> PRIO: 16765956
>> MATCHOP: 2
>> *MATCHEXP: *
>> MATCHLEN: 0
>> SUBSTEXP:
>> REPLEXP:
>> ATTRS: 1
>> }
>>
>> Please see generated core file in extension.
>>
>> Thank you,
>> Julia.
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierlawww.twitter.com/miconda --
>> www.linkedin.com/in/miconda
>> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>>
>> ___ SIP Express Router (SER)
>> and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org http://lists.sip-router.org/cg
>> i-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 4.4 segmentation fault when dp_translate match dialplan with ftmatch operator and empty match expression
Hello Daniel,
Thank you for reply.
Program terminated with signal 11, Segmentation fault.
#0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
MySQL-shared-5.5.27-1.el6.x86_64 glibc-2.12-1.47.el6.x86_64
libgcc-4.4.6-3.el6.x86_64 libuuid-2.17.2-12.4.el6.x86_64
pcre-7.8-3.1.el6.x86_64
(gdb) frame 0
#0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
(gdb) list
1834int proto;
1835char *options;
1836int ret;
1837unsigned int seed;
1838int rfd;
1839int debug_save, debug_flag;
1840int dont_fork_cnt;
1841struct name_lst* n_lst;
1842char *p;
1843struct stat st = {0};
Best regards.
Julia
On Mon, Dec 19, 2016 at 8:38 PM, Daniel-Constantin Mierla <mico...@gmail.com
> wrote:
> Hello,
>
> can you give the output in gdb for:
>
> frame 0
> list
>
> The head of 4.4 branch got some extra commits to the module and those
> commands help to identify the right lines of code.
>
> Cheers,
> Daniel
>
> On 19/12/2016 13:47, Julia Boudniatsky wrote:
>
> version: kamailio 4.4.4 id:852c47
>
> ENTRY: {
> PRIO: 16765956
> MATCHOP: 2
> *MATCHEXP: *
> MATCHLEN: 0
> SUBSTEXP:
> REPLEXP:
> ATTRS: 1
> }
>
> Please see generated core file in extension.
>
> Thank you,
> Julia.
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamailio 4.4 segmentation fault when dp_translate match dialplan with ftmatch operator and empty match expression
version: kamailio 4.4.4 id:852c47
ENTRY: {
PRIO: 16765956
MATCHOP: 2
*MATCHEXP: *
MATCHLEN: 0
SUBSTEXP:
REPLEXP:
ATTRS: 1
}
Please see generated core file in extension.
Thank you,
Julia.
Core was generated by `/usr/local/sbin/kamailio -f
/usr/local/etc/kamailio/kamailio.cfg -P /var/run/ka'.
Program terminated with signal 11, Segmentation fault.
#0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
MySQL-shared-5.5.27-1.el6.x86_64 glibc-2.12-1.47.el6.x86_64
libgcc-4.4.6-3.el6.x86_64 libuuid-2.17.2-12.4.el6.x86_64 pcre-7.8-3.1.el6.x86_64
(gdb) bt full
#0 0x0036074afb73 in internal_fnmatch () from /lib64/libc.so.6
No symbol table info available.
#1 0x0036074b41b0 in fnmatch@@GLIBC_2.2.5 () from /lib64/libc.so.6
No symbol table info available.
#2 0x7f7dca44d21a in translate (msg=0x7f7dd00bedd8, input=...,
output=0x7fff32793420, idp=0x7f7cc9376648, attrs=0x7fff32793410)
at dp_repl.c:636
rulep = 0x7f7cc9382c68
indexp = 0x7f7cc93766a8
user_len = 9
rez = -1
b = 64 '@'
re_list = 0x0
rt = 0x0
__FUNCTION__ = "translate"
#3 0x7f7dca42e150 in dp_translate_f (msg=0x7f7dd00bedd8,
str1=0x7f7dcfe99cf8 "\001", str2=0x7f7dcfe99d58 "\001") at dialplan.c:334
dpid = 256
input = {s = 0x7f7dcff801fc "036264863", len = 9}
output = {s = 0x0, len = -919125688}
idp = 0x7f7cc9376648
id_par = 0x7f7dcfe99cf8
repl_par = 0x7f7dcfe99d58
attrs = {s = 0x7fff32793440 "@5y2\377\177", len = -919125704}
attrs_par = 0x7fff32793410
__FUNCTION__ = "dp_translate_f"
#4 0x0041f532 in do_action (h=0x7fff32797b70, a=0x7f7dd0226838,
msg=0x7f7dd00bedd8) at action.c:1066
ret = -5
v = 846805968
dst = {send_sock = 0x7f7dd00bedd8, to = {s = {sa_family = 31600,
sa_data = "y2\377\177\000\000\000\000\000\000\000\000\000"}, sin = {
sin_family = 31600, sin_port = 12921, sin_addr = {s_addr =
32767}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {
sin6_family = 31600, sin6_port = 12921, sin6_flowinfo = 32767,
sin6_addr = {__in6_u = {
__u6_addr8 =
"\000\000\000\000\000\000\000\000\260>\"\320}\177\000", __u6_addr16 = {0, 0, 0,
0, 16048, 53282, 32637, 0},
__u6_addr32 = {0, 0, 3491905200, 32637}}}, sin6_scope_id =
4288096}}, id = 0, proto = -48 '\320', send_flags = {
f = 59 ';', blst_imask = 121 'y'}}
tmp = 0xfed00bedd8
new_uri = 0x7f7dd01eebc0 ""
end = 0x7f7dd00bedd8 "#\002"
crt = 0x32793b60
cmd = 0x7f7dcfd1b690
len = -803057080
user = 32637
uri = {user = {s = 0x0, len = 0}, passwd = {s = 0x7fff32793b60
"\220=y2\377\177", len = 5586823}, host = {
s = 0x7fff32793a60 "PY\"\320}\177", len = 0}, port = {s =
0x7f7dd0223eb0 "", len = 0}, params = {s = 0xaae720 "8A7\311|\177",
len = -803934995}, sip_params = {s = 0x3 , len = -803279859}, headers = {
s = 0x416e60
"1\355I\211\321^H\211\342H\203\344\360PTI\307\300p\252q", len = 846824480},
port_no = 0, proto = 0,
---Type to continue, or q to quit---
type = ERROR_URI_T, flags = 0, transport = {s = 0x7fff32793a30
"\240:y2\377\177", len = 6444816}, ttl = {s = 0x7f7d01f1 "",
len = -803279859}, user_param = {s = 0x7fff0007 , len = 11141120}, maddr = {s = 0x0,
len = 846805600}, method = {s = 0x0, len = -803279859}, lr = {s =
0x7fff0007 ,
len = 0}, r2 = {s = 0x7f7d0001 "", len = -803279859}, gr = {s =
0x7fff0007 ,
len = 11141120}, transport_val = {s = 0x416e60
"1\355I\211\321^H\211\342H\203\344\360PTI\307\300p\252q", len = -803279859},
ttl_val = {s = 0x7fff32793aa0 "\330\355\v\320}\177", len = 6474388},
user_param_val = {
s = 0xd01eebc0 , len =
-803279859}, maddr_val = {s = 0x7f7d0007 "", len = 256},
method_val = {s = 0x7f7dd0225950 "\001", len = 846806340}, lr_val =
{s = 0x7f7dd00bedd8 "#\002", len = 846822256}, r2_val = {
s = 0x7fff32793d00 "", len = -803057088}, gr_val = {s =
0x7fff32793d48 "", len = 846806200}}
next_hop = {user = {s = 0x7f7cc93740f0 "0", len = -930689024}, passwd =
{s = 0x0, len = -919125776}, host = {
s = 0x7fff327938c0 " 9y2", len = 846806280}, port = {s =
0x7f7dd0225250 "\004", len = -804524584}, params = {
Re: [SR-Users] event_route[uac:reply] question
Hi Alex, This works fine, undoubtedly it's a better solution. Thank you very much! Julia. On Tue, Sep 20, 2016 at 11:28 AM, Alex Hermann <a...@speakup.nl> wrote: > On maandag 19 september 2016 13:34:07 CEST Julia Boudniatsky wrote: > > I send INVITE via uac_send_req() and receive "183" and "200"responses. > > Only "200" appears in the log of event_route[uac:reply]. > > > > Is event_route[uac:reply] executed only for final responses? > > You should be able to set an onreply route in the tm:local-request > event_route > to catch replies. > > -- > Greetings, > > Alex Hermann > > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] event_route[uac:reply] question
Hello, thank you for reply. I need to set some variable with sdp from 183. I solved it with sending uac request to different kamailio local port (before sending to destination) and specifying onreply_route for INVITEs, received in this port. On Tue, Sep 20, 2016 at 10:38 AM, Daniel-Constantin Mierla < mico...@gmail.com> wrote: > Indeed, only the final response gets to the even_route, this is because of > the callback used from tm module. > > Maybe, if you can offer more details about what you need from 183, we can > provide some hints if it's possible and how. > > Cheers, > Daniel > > On 20/09/16 07:27, Julia Boudniatsky wrote: > > I found in the module uac documentation: > > "6.1. event_route[uac:reply] > Event route executed for the* final* reply to the request set with > uac_req_send(). > > Thanks, > Julia > > On Mon, Sep 19, 2016 at 1:34 PM, Julia Boudniatsky <juli...@gmail.com> > wrote: > >> I send INVITE via uac_send_req() and receive "183" and "200"responses. >> Only "200" appears in the log of event_route[uac:reply]. >> >> Is event_route[uac:reply] executed only for final responses? >> >> Thank you, >> Julia >> >> > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing > listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > -- > Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda > Kamailio Advanced Training, Berlin, Oct 24-26, 2016 - http://www.asipto.com > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] event_route[uac:reply] question
I found in the module uac documentation: "6.1. event_route[uac:reply] Event route executed for the* final* reply to the request set with uac_req_send(). Thanks, Julia On Mon, Sep 19, 2016 at 1:34 PM, Julia Boudniatsky <juli...@gmail.com> wrote: > I send INVITE via uac_send_req() and receive "183" and "200"responses. > Only "200" appears in the log of event_route[uac:reply]. > > Is event_route[uac:reply] executed only for final responses? > > Thank you, > Julia > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] event_route[uac:reply] question
I send INVITE via uac_send_req() and receive "183" and "200"responses. Only "200" appears in the log of event_route[uac:reply]. Is event_route[uac:reply] executed only for final responses? Thank you, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] To/From tags in uac_req()
Hello Daniel, How to track with dialog the call initiated by Kamailio ? Simple dlg_manage(), after uac_req_send()? Thank you, Julia. On Thu, Aug 18, 2016 at 10:53 AM, Daniel-Constantin Mierla < mico...@gmail.com> wrote: > Hello, > > an alternative is to track the call with dialog module and then trigger > the end of the dialog via config or mi/rpc: > > - https://www.kamailio.org/docs/modules/stable/modules/dialog. > html#idp47915332 > > - https://www.kamailio.org/docs/modules/stable/modules/dialog. > html#idp47967692 > > Cheers, > Daniel > > On 18/08/16 09:40, Julia Boudniatsky wrote: > > Thank you Alex! > I'll try it. > Best regards, > Julia > > On Thu, Aug 18, 2016 at 10:32 AM, Alex Balashov <abalas...@evaristesys.com > > wrote: > >> Hi Julia, >> >> The only attributes that can be set on a request formed with uac_req() >> are listed here: >> >> http://www.kamailio.org/wiki/cookbooks/4.4.x/pseudovariables#uac_req_key >> >> Tags are not among them. >> >> However, it might be possible to generate a completely synthetic SIP >> message yourself using an alternate facility: >> >> http://kamailio.org/docs/modules/4.4.x/modules/corex.html#co >> rex.f.send_data >> >> -- Alex >> >> On 08/18/2016 03:27 AM, Julia Boudniatsky wrote: >> >> Hello, >>> >>> Is it possible to set To/From tags in uac_req() ? >>> We want to implement service like "color ring back tone". >>> >>> _Kamailio uac_ _Asterisk_ >>> >>> INVITE SDP --> >>> <-200 SDP-- >>> -BYE --> >>> <--- 200 --- >>> >>> I need to send in BYE the same tags. >>> Kamailio 4.4.2. >>> >>> Thanks, >>> >>> Julia >>> >>> >>> >>> ___ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users@lists.sip-router.org >>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> 1447 Peachtree Street NE, Suite 700 >> Atlanta, GA 30309 >> United States >> >> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> ___ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing > listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > -- > Daniel-Constantin Mierlahttp://www.asipto.com - > http://www.kamailio.orghttp://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] To/From tags in uac_req()
Thank you Alex! I'll try it. Best regards, Julia On Thu, Aug 18, 2016 at 10:32 AM, Alex Balashov <abalas...@evaristesys.com> wrote: > Hi Julia, > > The only attributes that can be set on a request formed with uac_req() are > listed here: > > http://www.kamailio.org/wiki/cookbooks/4.4.x/pseudovariables#uac_req_key > > Tags are not among them. > > However, it might be possible to generate a completely synthetic SIP > message yourself using an alternate facility: > > http://kamailio.org/docs/modules/4.4.x/modules/corex.html# > corex.f.send_data > > -- Alex > > On 08/18/2016 03:27 AM, Julia Boudniatsky wrote: > > Hello, >> >> Is it possible to set To/From tags in uac_req() ? >> We want to implement service like "color ring back tone". >> >> _Kamailio uac_ _Asterisk_ >> >> INVITE SDP --> >> <-200 SDP-- >> -BYE --> >> <--- 200 --- >> >> I need to send in BYE the same tags. >> Kamailio 4.4.2. >> >> Thanks, >> >> Julia >> >> >> >> ___ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users@lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> >> > > -- > Alex Balashov | Principal | Evariste Systems LLC > 1447 Peachtree Street NE, Suite 700 > Atlanta, GA 30309 > United States > > Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] To/From tags in uac_req()
Hello, Is it possible to set To/From tags in uac_req() ? We want to implement service like "color ring back tone". *Kamailio uac* *Asterisk* INVITE SDP --> <-200 SDP-- -BYE --> <--- 200 --- I need to send in BYE the same tags. Kamailio 4.4.2. Thanks, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] question about dlg_var
Hello,
I am using two different on_reply routes:
if (is_method("INVITE") && !has_totag()) {
...
t_on_reply(REPLY_TO_SOURCE);
}
route[WITHINDLG] {
if(has_to_tag()) {
t_on_reply(REPLY_IN_DIALOG);
}
May be it will help.
Best regards,
Julia.
On Thu, Mar 3, 2016 at 10:57 AM, Federico Cabiddu <
federico.cabi...@gmail.com> wrote:
> Hi,
> If I understood correctly the original question was to identify, in a
> reply route, a 200 OK coming for an initial INVITE.
> In the reply route the 200 OK will always have a to tag (unless the UAS is
> broken), so you cannot this condition.
>
> Regards,
>
> Federico
>
> On Thu, Mar 3, 2016 at 9:05 AM, Serge S. Yuriev <m...@nevian.org> wrote:
>
>> Hi,
>>
>> Sorry, but why not to check has_totag again? Why we need a flag?
>>
>> --
>> Wbr, Serge via mobile
>>
>> 03.03.2016, 09:31, "Federico Cabiddu" <federico.cabi...@gmail.com>:
>>
>>
>> Hi,
>> $dlg_var is not available at this stage of the dialog:
>>
>>
>> http://www.kamailio.org/docs/modules/devel/modules/dialog.html#idp19330392
>>
>>
>>
>> To achieve your goal you can use there an avp or a flag, which are bound
>> to transactions.
>> Something like:
>>
>>
>>
>> #define INIT_FLAG
>>
>>
>> if (is_method("INVITE") && !has_totag()) {
>>
>> $avp(is_init_invite) = 1;
>> # or
>> # setflag(INIT_FLAG);
>> }
>>
>>
>> onreply_route {
>> if (is_method("INVITE") && t_check_status("200") &&
>> $avp(is_init_invite) == "1") {
>> # or
>> # if (is_method("INVITE") && t_check_status("200") &&
>> isflagset(INIT_FLAG))
>> #
>> # do somting
>> }
>> }
>>
>>
>> Regards,
>>
>>
>> Federico
>>
>>
>> On Thu, Mar 3, 2016 at 4:55 AM, 张顺通 <shuntongzh...@gmail.com> wrote:
>>
>>
>> I want to distingguish 200 OK is for INVITE or reINVITE。
>>
>>
>> so I do this:
>> request_route {
>> if (is_method("INVITE") && !has_totag()) {
>> $dlg_var(is_init_invite) = "1";
>> }
>> }
>>
>>
>> onreply_route {
>> xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]");
>> if (is_method("INVITE") && t_check_status("200") &&
>> $dlg_var(is_init_invite) == "1") {
>> # do somting
>> $dlg_var(is_init_invite) = "0";
>> }
>> xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]");
>> }
>>
>>
>> What I confuse is：
>> When I recive 100 Trying LOG is
>> [100 - Trying][is_init_invite:0]
>> [100 - Trying][is_init_invite:1]
>>
>>
>>
>> why is_init_invite is 0?
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>>
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] PKG memory leak in 4.2.6
Hello Daniel,
Please find the attached new pkg summary log file at runtime.
Memory leak ~ 5M .
Thank you,
Julia
On Thu, Nov 12, 2015 at 10:08 AM, Daniel-Constantin Mierla <
mico...@gmail.com> wrote:
> Hello,
>
> ok -- one more note, if you need to lower the memlog via kamcmd, once you
> get the log messages, you can set it back to higher value:
>
> kamcmd cfg.set_now_int core memlog 5
>
> Cheers,
> Daniel
>
>
> On 11/11/15 11:03, Julia Boudniatsky wrote:
>
> Hello Daniel,
>
> I'll try to execute this procedure.
>
> Thank you,
> Julia
>
> On Wed, Nov 11, 2015 at 10:49 AM, Daniel-Constantin Mierla <
> <mico...@gmail.com>mico...@gmail.com> wrote:
>
>> Hello,
>>
>> it looks like the pkg summary is made by the main kamailio process which
>> doesn't route sip packets at runtime, therefore it doesn't expose any
>> potential leak.
>>
>> Can you add following snipped at beginning of the request_route:
>>
>> if(is_method("OPTIONS") && src_ip==TRUSTEDIP && $rU=="pkgsummary") {
>>pkg_summary();
>>sl_send_reply("200", "ok");
>>exit;
>> }
>>
>> You need to replace TRUSTEDIP with the IP address from where you will
>> send a SIP OPTIONS later.
>>
>> After you restart kamailio, let it run for a while until you see the pkg
>> decreasing enough.
>>
>> Then send OPTIONS request via sipsak:
>>
>> sipsak -s sip:pkgsummary@yourserverip
>>
>> Check the syslog to see if the pkg summary messages are there and if yes,
>> send them here.
>>
>> If not, you may need to decrease the value for memlog, do:
>>
>> kamcmd cfg.set_now_int core memlog 1
>>
>> and then run again the sipsak command.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 11/11/15 07:17, Julia Boudniatsky wrote:
>>
>> Hello,
>>
>> We are running Kamailio 4.2.6 ( db77ac) compiled with memory debugging.
>>
>> The free PKG memory has decreased on ~6.5 M after two weeks.
>>
>> Please see attached file with the log messages at kamailio shutdown.
>>
>> Thank you in advance,
>>
>> Julia.
>>
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
>> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
>> http://www.linkedin.com/in/miconda
>> Book: SIP Routing With Kamailio - http://www.asipto.com
>> Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
>>
>>
>> ___
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users@lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
>
>
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
summarizing all alloc'ed. fragments:
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size= 472 bytes from : parser/msg_parser.c:
get_hdr_field(173)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size=80 bytes from pv: pv_trans.c: tr_eval_nameaddr(1425)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size=80 bytes from pv: pv_trans.c: tr_eval_uri(999)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size=72 bytes from pv: pv_trans.c: tr_eval_paramlist(1199)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size= 2976 bytes from tmx: t_var.c: pv_t_update_rpl(190)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size= 1992 bytes from tmx: t_var.c: pv_t_update_req(114)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 6 size= 384 bytes from : parser/parse_via.c:
parse_via(2540)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 1 size= 1768 bytes from : receive.c: receive_msg(120)
Dec 2 08:44:10 KAMnet-JAF-01 /usr/local/sbin/kamailio[2601]: WARNING: qm_sums:
count= 3 size=
Re: [SR-Users] PKG memory leak in 4.2.6
Hello Daniel,
I'll try to execute this procedure.
Thank you,
Julia
On Wed, Nov 11, 2015 at 10:49 AM, Daniel-Constantin Mierla <
mico...@gmail.com> wrote:
> Hello,
>
> it looks like the pkg summary is made by the main kamailio process which
> doesn't route sip packets at runtime, therefore it doesn't expose any
> potential leak.
>
> Can you add following snipped at beginning of the request_route:
>
> if(is_method("OPTIONS") && src_ip==TRUSTEDIP && $rU=="pkgsummary") {
>pkg_summary();
>sl_send_reply("200", "ok");
>exit;
> }
>
> You need to replace TRUSTEDIP with the IP address from where you will send
> a SIP OPTIONS later.
>
> After you restart kamailio, let it run for a while until you see the pkg
> decreasing enough.
>
> Then send OPTIONS request via sipsak:
>
> sipsak -s sip:pkgsummary@yourserverip
>
> Check the syslog to see if the pkg summary messages are there and if yes,
> send them here.
>
> If not, you may need to decrease the value for memlog, do:
>
> kamcmd cfg.set_now_int core memlog 1
>
> and then run again the sipsak command.
>
> Cheers,
> Daniel
>
>
> On 11/11/15 07:17, Julia Boudniatsky wrote:
>
> Hello,
>
> We are running Kamailio 4.2.6 ( db77ac) compiled with memory debugging.
>
> The free PKG memory has decreased on ~6.5 M after two weeks.
>
> Please see attached file with the log messages at kamailio shutdown.
>
> Thank you in advance,
>
> Julia.
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
> http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Nov 30-Dec 2, Berlin - http://asipto.com/kat
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] PKG memory leak in 4.2.6
Hello, We are running Kamailio 4.2.6 ( db77ac) compiled with memory debugging. The free PKG memory has decreased on ~6.5 M after two weeks. Please see attached file with the log messages at kamailio shutdown. Thank you in advance, Julia. Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: [main.c:611]: cleanup(): Memory still-in-use summary (pkg): Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: summarizing all alloc'ed. fragments: Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 4 size= 448 bytes from pv: pv_xavp.c: pv_parse_xavp_name(531) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 4 size= 448 bytes from pv: pv_xavp.c: pv_parse_xavp_name(507) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 2 size= 464 bytes from : parser/msg_parser.c: get_hdr_field(133) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 2 size= 128 bytes from : parser/msg_parser.c: parse_headers(343) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 2 size=32 bytes from : select.c: register_select_table(465) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=24 bytes from kex: mi_core.c: init_mi_uptime(74) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=80 bytes from : socket_info.c: fix_sock_str(438) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=16 bytes from : socket_info.c: fix_hostname(1378) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=16 bytes from : socket_info.c: fix_hostname(1360) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 2 size=40 bytes from : name_alias.h: add_alias(99) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 2 size=64 bytes from : name_alias.h: add_alias(97) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=16 bytes from : socket_info.c: fix_socket_list(1580) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 6 size= 248 bytes from pv: pv_trans.c: tr_parse_string(2103) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 9 size= 936 bytes from tmx: t_var.c: pv_parse_t_var_name(362) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=96 bytes from textops: textops.c: fixup_regexpNL_none(2693) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count=15 size= 992 bytes from : sr_module.c: fix_param(1173) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=32 bytes from pv: pv_trans.c: tr_parse_paramlist(2420) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 3 size=96 bytes from pv: pv_trans.c: tr_parse_paramlist(2412) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 3 size=96 bytes from textops: txt_var.c: tr_txt_parse_re(206) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=24 bytes from avpops: avpops_parse.c: parse_intstr_value(309) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=64 bytes from avpops: avpops.c: fixup_check_avp(677) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=32 bytes from avpops: avpops_parse.c: parse_intstr_value(277) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 1 size=32 bytes from avpops: avpops_parse.c: avpops_parse_pvar(64) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count=13 size= 3144 bytes from : re.c: subst_parser(302) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count=13 size= 832 bytes from : re.c: subst_parser(285) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count=13 size= 456 bytes from : re.c: subst_parser(312) Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 9 size= 512 bytes from pv: pv_trans.c: tr_parse_string() Nov 10 17:48:09 KAMnet-JAF-01 /usr/local/sbin/kamailio[7498]: WARNING: qm_sums: count= 9 size= 288 bytes from pv: pv_trans.c: tr_parse_string(2038) Nov 10 17:48:09
Re: [SR-Users] core parameter onsend_route_reply=1 doesn't execute onsend_route block for received replies
Hello Daniel, When I run with debug=3, I don't see message with "reply forward to". That are received logs (without dialog part) in replay 183: Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: tm [t_reply.c:1311]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=183 Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: tm [t_reply.c:1829]: relay_reply(): DEBUG: relay_reply: branch=1, save=0, relay=1 icode=0 Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fc307dcf4b8, callback type 32, id 0 entered Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: [msg_translator.c:2278]: generate_res_buf_from_sip_res(): old size: 993, new size: 896 Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: [msg_translator.c:2296]: generate_res_buf_from_sip_res(): copied size: orig:446, new: 349, rest: 547 msg= SIP/2.0 183 Session Progress Via:SIP/2.0/UDP 192.168.180.1:5060 ;branch=z9hG4bK-6120862ccddf-ac11bf17-1 From:<sip:506777498;ss7-cpc=10;cpc=ordinary@192.168.180.1 ;user=phone>;tag=6998741155494809055 To:<sip:D39539988202@10.25.153.150;user=phone>;tag=581042614-1441039641760 Call-ID:6998741155494809055-1441039607@172.17.191.23 CSeq:1 INVITE Contact: Record-Route:<sip:10.25.153.150;lr;ftag=6998741155494809055> Session: Media RSeq:39056976 P-Asserted-Identity:"Test Julia"<sip:039988202@10.25.148.41;user=phone> Privacy:none Require:100rel Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE Content-Type:application/sdp Content-Length:198 v=0 o=BroadWorks 209562 1 IN IP4 10.25.148.43 s=- c=IN IP4 10.25.148.43 t=0 0 m=audio 15944 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 Aug 31 19:47:21 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[9487]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fc307dcf4b8, callback type 1048576, id 0 entered Thank you, Julia On Mon, Aug 31, 2015 at 7:24 PM, Daniel-Constantin Mierla <mico...@gmail.com > wrote: > Hello, > > do you get any other log error message? > > If you run with debug=3, do you a message containing: > > ... reply forwarded to ... > > ? > > Cheers, > Daniel > > > On 30/08/15 14:55, Julia Boudniatsky wrote: > > Hello, > > I set some logs in onsend_route and it works fine for requests. > With setting core parameter onsend_route_reply=1 ( yes, on), i expect to > see logs for replays also, but it not occurs. > Is this a bug or I miss something? > > version: kamailio 4.2.6 (x86_64/linux) db77ac > > BR, > Julia > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing > listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > -- > Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda > Book: SIP Routing With Kamailio - http://www.asipto.com > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] core parameter onsend_route_reply=1 doesn't execute onsend_route block for received replies
Hello, I set some logs in onsend_route and it works fine for requests. With setting core parameter onsend_route_reply=1 ( yes, on), i expect to see logs for replays also, but it not occurs. Is this a bug or I miss something? version: kamailio 4.2.6 (x86_64/linux) db77ac BR, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio V4.2.5 append prefix to Request Uri problem.
Hi, Try to use: $rU=$_s($avp(69)$rU); BR Julia On Fri, May 29, 2015 at 12:13 PM, Yasin CANER yasin.ca...@netgsm.com.tr wrote: Hello; i try to append prefix to $rU like below in Kamailio V4.2.5 . i get error even if i set string value. it works only when i append like that $rU=3002+$rU; - 1 test $var(prefix)=$avp(s:69); $rU=$var(prefix)+$rU; -FAILED -2 test $rU=$avp(s:69)+$rU; -FAILED --- 3 test $rU=$avp(i:69)+$rU; -FAILED ---ERROR- May 29 12:06:57 group1-imslab11 /usr/local/sbin/kamailio[26196]: ERROR: pv [pv_core.c:2115]: pv_set_ruri_user(): str value required to set R-URI user May 29 12:06:57 group1-imslab11 /usr/local/sbin/kamailio[26196]: ERROR: core [lvalue.c:363]: lval_pvar_assign(): setting pvar failed May 29 12:06:57 group1-imslab11 /usr/local/sbin/kamailio[26196]: ERROR: core [lvalue.c:416]: lval_assign(): assignment failed at pos: (790,7-790,22) it work on Version 4.1.7 like below correctly; $rU=$avp(i:69)+$rU; Thanks Yasin ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio V4.2.5 append prefix to Request Uri problem.
Please see in http://www.kamailio.org/wiki/cookbooks/4.2.x/pseudovariables $_s(format) - Evaluate dynamic format *$_s(format)* - returns the string after evaluating all pseudo-variables in format $var(x) = sip: + $rU + @ + $fd; # is equivalent of:$var(x) = $_s(sip:$rU@$fd); BR On Fri, May 29, 2015 at 2:40 PM, ycaner yasin.ca...@netgsm.com.tr wrote: Hello; it works both ways. Could you explain what i did here? $rU=*$_s*($avp(i:69)$rU); $rU=*$_s*($avp(s:69)$rU); Thanks. -- View this message in context: http://sip-router.1086192.n5.nabble.com/Kamailio-V4-2-5-append-prefix-to-Request-Uri-problem-tp138258p138277.html Sent from the Users mailing list archive at Nabble.com. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] 4.2.3 textops: flag f doesn't work in subst_hf(hf, subexp, flags)
Hello Daniel, Thank you so much, it's working now! BR, Julia On Mon, Mar 9, 2015 at 1:43 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, can you try with latest version from branch 4.2, I pushed a patch that should fix the case for f flag. Cheers, Daniel On 08/03/15 17:49, Julia Boudniatsky wrote: Hello, I received INVITE with 3 Diversion headers. I try to make substitutions in the body of a first Diversion header field by using flag f, command *subst_hf(Diversion, /sip:(.*)@/sip:$var(dU)@/, f) ;* substitutes *all headers *Diversion instead of only first header, command *subst_hf(Diversion, /sip:(.*)@/sip:$var(dU)@/, *l*) ;* substitutes only *last* Diversion header. Thanks for help, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] 4.2.3 textops: flag f doesn't work in subst_hf(hf, subexp, flags)
Hello, I received INVITE with 3 Diversion headers. I try to make substitutions in the body of a first Diversion header field by using flag f, command *subst_hf(Diversion, /sip:(.*)@/sip:$var(dU)@/, f) ;* substitutes *all headers *Diversion instead of only first header, command *subst_hf(Diversion, /sip:(.*)@/sip:$var(dU)@/, *l*) ;* substitutes only *last* Diversion header. Thanks for help, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Wrong dialog selected in on_reply/failure route in case of spirals.
Hello Daniel, Today I installed kamailio from GIT last devel 4.3.0-dev3. *The problem is solved!* Thank you so much for your help ! Julia On Mon, Jan 26, 2015 at 8:38 PM, Julia Boudniatsky juli...@gmail.com wrote: Yes it /usr/local/sbin/kamailio, I haven't internet in the test server. I get git from another server and copy received directory kamailio to test server, then make cfg/all/install. BR, Julia On Mon, Jan 26, 2015 at 8:10 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: I did the same right now and I get: version: kamailio 4.3.0-dev3 (x86_64/darwin) 1b334f Can you check if you have another instance installed on a different path that takes precendence? Do: which kamailio When installed from sources, it should be: /usr/local/sbin/kamailio Cheers, Daniel On 26/01/15 18:55, Julia Boudniatsky wrote: I used from your link * http://www.kamailio.org/wiki/#installation - Install Kamailio Devel Version From GIT http://www.kamailio.org/wiki/install/devel/git #mkdir -p /usr/local/src/kamailio-devel #cd /usr/local/src/kamailio-devel #git clone --depth 1 --no-single-branch git://git.kamailio.org/kamailio kamailio #cd kamailio BR, Julia On Mon, Jan 26, 2015 at 7:04 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, that is not the last devel version, it should be with -dev3. How did you get the sources? I get: version: kamailio 4.3.0-dev3 (x86_64/darwin) 1b334f And yes, if you still get the error, send the logs with the description. Cheers, Daniel On 26/01/15 17:16, Julia Boudniatsky wrote: Hello Daniel, In devel installed, I received the same problem. kamailio -V version: kamailio 4.3.0-dev2 (x86_64/linux) ecd5c5 flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: ecd5c5 compiled on 18:02:05 Jan 26 2015 with gcc 4.4.6 Do you want a log files? Thank you, Julia On Mon, Jan 26, 2015 at 12:47 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, none of existing releases are good because the patches are only in git branches, added after the last relesea (I added it iver this weekend). You must install from git, as pointed by one of the tutorials at: * http://www.kamailio.org/wiki/#installation You must use devel (master), 4.2 (v4.2.x) or 4.1 (v4.1.x) branches. We will have new releases in the near future, like 1-2 weeks from now, but by then I hope to get this bug sorted out. Cheers, Daniel On 26/01/15 11:42, Julia Boudniatsky wrote: Hello Daniel, I installed last 4.2 version: kamailio 4.2.1 (x86_64/linux) d80dfc flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: d80dfc compiled on 10:06:01 Jan 26 2015 with gcc 4.4.6 *Problem in call with Call-ID : 5-5028@10.25.153.150 5-5028@10.25.153.150 * *Short log* *dialog [3748:5628]* *100 trying* Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status): Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:635]: parse_msg(): version: SIP/2.0 Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:637]: parse_msg(): status: 100 Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:639]: parse_msg(): reason: Trying Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=9313591363960470767 Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header reached, state=29 Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: To [71]; uri=[sip:039951004@10.25.153.149:5060;user=phone] Jan 26 10:20:49 vm-KAMnet-dev01 /usr/local/sbin/kamailio[20649]: DEBUG: core [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [ sip:039951004@10.25.153.149:5060;user=phone] Jan 26 10:20:49 vm-KAMnet
Re: [SR-Users] Wrong dialog selected in on_reply/failure route in case of spirals.
Hello Daniel,
I have re-installed kamailio from last 4.1 branch, but unfortunately, the
problem persists.
Failed call with callID=2-17858@10.25153.150.
The log file i send to your private mail.
Best regards,
Julia
On Sun, Jan 25, 2015 at 12:03 AM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
Hello,
got the time to analyze your last logs and I discovered that the previous
patch was not resetting properly the dialog shortcuts. I pushed a fix, can
you try again with the latest version from one of the branches: master, 4.2
or 4.1?Let me know the results.
Cheers,
Daniel
On 15/01/15 23:42, Daniel-Constantin Mierla wrote:
Hello,
I looked at the logs, but I cannot see the log message I added with the
patch for reseting local dialog shortcuts after onreply and failure route.
It shuld be something like:
... resetting the local dialog shortcuts
Are you sure you are running the latest branch 4.1? You can send the
output of kamailio -v to double check here.
I separated the logs per process and looked when a 301 was received,
apparently the ones for Call-ID: 4-21712 are matching the same dialog. I
found something not printing the same kind of logs like for other 301 for
Call-ID: 2-21712. If you can point the line in the logs where you think it
was the wrong dialog match, I can investigate from there, but now I
couldn't find any lead.
Anyhow, if it is the latest branch 4.1 and the problem still persists, can
you add the following xlog at the beginning of main request_route (or the
route {...} ), plus in each reply_route, onreply_route and failure_route:
xlog(processing $rm ( $ci / %ft / $tt / $hdr(Via) ) [$fu = $tu]\n);
Then redo the tests to catch the issue and send me the new logs. Because
you use sipp with tags like '4', it is hard to search on a single tocken
and I want to have the all message attribute when a relevant route block is
executed.
Cheers,
Daniel
On 14/01/15 15:07, Daniel-Constantin Mierla wrote:
Hello Julia,
ok, I will look over the logs very soon.
As a short note for the future, make the archives zip or tgz, being more
common formats that can be unarchived everywhere without installing
additional app, being handy to open even on small devices. Now it is ok
with rar, being at the desk.
Cheers,
Daniel
On 14/01/15 14:43, Julia Boudniatsky wrote:
Hello Daniel,
Please find in attached file the debug 3 log.
Failed call with Call-ID: 4-21712@10.25.153.150.
The problem occurred with all modes of dlg_match_mode
The same load test in 3.3 executed without failures.
Thank you,
Julia.
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Search Un-Register Expires header
Hello Emilio,
I use
if( $hdr(Expires)==0) {
Best regards,
Julia
On Mon, Jan 19, 2015 at 1:44 PM, Emilio Soler Muñoz emilioso...@gmail.com
wrote:
Hi,
I find a problem when I try to search the header Expires with value 0.
At my kamailio.cfg the configuration is:
if ( search_hf(Expires, :0@, a) )
{
xlog(L_INFO, Encontrado expires 0 ($rm));
}
This way find nothing.
I test with 0 (no wildcards regular expression), but this make matches in
any Register with header Expires content 0. Example:
...
if ( search_hf(Expires, 0, a) )
I saw some people control expires=0 at contact header, but not my case.
Example:
if (search(expires=0))
{
xlog(L_INFO, Encontrado expires 0 ($rm));
}
Regards,
--
Emilio Soler
emilioso...@gmail.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Search Un-Register Expires header
For header Contact :
if($sel(contact.expires) == 0) {
also may be used.
BR,
Julia
On Mon, Jan 19, 2015 at 2:56 PM, Emilio Soler Muñoz emilioso...@gmail.com
wrote:
Thank you all for the help.
Finally, considering that according to the RFC in Contact header can only
come expires = 0
I set this in my config file:
...
if (($ hdr (Expires) == 0) || ($ hdr (Contact) = ~ expires = 0)
...
2015-01-19 13:16 GMT+01:00 Olle E. Johansson o...@edvina.net:
Try
if ($hdr(Expires) == 0)
Note that expires can also be a contact parameter.
/O
On 19 Jan 2015, at 12:44, Emilio Soler Muñoz emilioso...@gmail.com
wrote:
Hi,
I find a problem when I try to search the header Expires with value 0.
At my kamailio.cfg the configuration is:
if ( search_hf(Expires, :0@, a) )
{
xlog(L_INFO, Encontrado expires 0 ($rm));
}
This way find nothing.
I test with 0 (no wildcards regular expression), but this make matches
in any Register with header Expires content 0. Example:
...
if ( search_hf(Expires, 0, a) )
I saw some people control expires=0 at contact header, but not my case.
Example:
if (search(expires=0))
{
xlog(L_INFO, Encontrado expires 0 ($rm));
}
Regards,
--
Emilio Soler
emilioso...@gmail.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Emilio Soler Muñoz
665801225
emilioso...@gmail.com
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Wrong dialog selected in on_reply/failure route in case of spirals.
: t_check_msg: msg id=645 global id=644 T start=0x Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 13904 label 0 branch 0 Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: tm [t_lookup.c:1004]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7fb318dcfae8)! Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=645 global id=645 T end=0x7fb318dcfae8 Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: tm [t_reply.c:2206]: reply_received(): DEBUG: reply_received: org. status uas=100, uac[0]=100 local=0 is_invite=1) Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: core [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: core [parser/msg_parser.c:106]: get_hdr_field(): found end of header Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: dialog [dlg_hash.c:656]: dlg_lookup(): dialog id=6551 found on entry 3838 Dec 16 14:07:49 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[5540]: DEBUG: dialog [dlg_hash.c:654]: dlg_lookup(): ref dlg 0x7fb318d989c0 with 1 - 2 BR, Julia On Tue, Dec 16, 2014 at 1:03 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, looking again at your diagram, it seems that the Call-Id is the same, but there is a different dialog structure. If you dump the dialogs with kamctl, can you see the two structure listed? Are they with same dialog attributes (From/To/...)? Dialog module has a parameter for detecting spirals, have you set it to some value? Cheers, Daniel On 10/12/14 13:39, Julia Boudniatsky wrote: Hello Daniel, I have tried from latest git branch 4.1 (I see your new patches for dialog ) But the problem steel occur. Thank you, Julia On Wed, Dec 10, 2014 at 12:21 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, can you try with latest git branch 4.1 and report the results? I just pushed a patch that should fix it. Cheers, Daniel On 09/12/14 19:06, Julia Boudniatsky wrote: After kamailio upgrade from v3.3 to v4.1.7 in production ~5% of calls with spirals dialog are failed with wrong dialog variables in on-reply/failure routes. The problem has been reproduced in the LAB (load test generated by SIPP). Please see the attached file with debug3 log. Scenario: Proxy Location Kamailio P1 Nbr translation Redirect | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150)| |--| | 100 Trying| | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150)| |--| | 301 Moved Permanently | | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150
[SR-Users] Wrong dialog selected in on_reply/failure route in case of spirals.
After kamailio upgrade from v3.3 to v4.1.7 in production ~5% of calls with spirals dialog are failed with wrong dialog variables in on-reply/failure routes. The problem has been reproduced in the LAB (load test generated by SIPP). Please see the attached file with debug3 log. Scenario: Proxy Location Kamailio P1 Nbr translation Redirect | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150)| |--| | 100 Trying| | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150)| |--| | 301 Moved Permanently | | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150)| |--| | | Thank you, Julia. Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: NOTICE: KAMnet: RELAY: dlg_hash=7851:1036 INVITE from IVRcustomer to LNP ru=sip:039936648@192.168.180.1:5081 fu=sip:039988222@10.25.153.150;user=phone tu=sip:039936648@10.25.153.150:5060;user=phone ai=sip:039988222@10.25.153.150;user=phone ci=5-8286@10.25.153.150 cl=201 di=Arik Lustigsip:36264836@10.25.148.1;user=phone;privacy=off;reason=deflection;answered;counter=1 branch[0] Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_hash.c:711]: internal_get_dlg(): ref dlg 0x7f8f8501aba0 with 1 - 2 Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_hash.c:714]: internal_get_dlg(): dialog callid='5-8286@10.25.153.150' found on entry 1036, dir=1 Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:227]: print_lists(): Internal var-list ((nil)): Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:237]: print_lists(): Dialog var-list (0x7f8f85011230): Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): ServNum=039936648 (flags 1) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): ServIP=10.25.154.104 (flags 1) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): ServCarrier=IEC1 (flags 1) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): LegNum=1 (flags 1) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): branch=0 (flags 1) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): OutTrunk=LNPVERAZNEW-1 (flags 0) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): CHARGE=n (flags 0) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): DEST=LNP (flags 0) Dec 9 14:24:11 KAMnet-JAF-TST-01 /usr/local/sbin/kamailio[6365]: DEBUG: dialog [dlg_var.c:242]: print_lists(): henek=y (flags 1) Dec 9 14
Re: [SR-Users] Wrong dialog selected in on_reply/failure route in case of spirals.
Hello Daniel, I have tried from latest git branch 4.1 (I see your new patches for dialog ) But the problem steel occur. Thank you, Julia On Wed, Dec 10, 2014 at 12:21 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, can you try with latest git branch 4.1 and report the results? I just pushed a patch that should fix it. Cheers, Daniel On 09/12/14 19:06, Julia Boudniatsky wrote: After kamailio upgrade from v3.3 to v4.1.7 in production ~5% of calls with spirals dialog are failed with wrong dialog variables in on-reply/failure routes. The problem has been reproduced in the LAB (load test generated by SIPP). Please see the attached file with debug3 log. Scenario: Proxy Location Kamailio P1 Nbr translation Redirect | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | | 100 Trying | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150) | | |---| | || | | INVITE | | | dlg 0x7f8f8501aba0 | | | Call-ID:(5-8286@10.25.153.150)| |--| | 100 Trying| | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150)| |--| | 301 Moved Permanently | | dlg 0x7f8f8504cda0 | | Call-ID:(5-8286@10.25.153.150)| |--| | | Thank you, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] xavp contact_avp question
Hello, We use get_redirects(*) and t_load_contacts in script. modparam(tm, contacts_avp, $avp(contacts)) In versions previous to 4.1 print all contacts: $(avp(contacts[*]) delete all contacts: $(avp(contacts[*])=$null From 4.1 this avp is changed to xavp structure. What is the structure name and value name of xavp for print in log $xavp(contacts=?) ? Is it possible to delete xavp? Thank you, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] xavp contact_avp question
Daniel, thank you for quick response. After t_load_contact() i try to use pv_printf($var(contact), $xavp(contacts[0]=dst_uri)); xlog (L_NOTICE, var(contact)=$var(contact)\r\n); and receive result null. What is wrong? On Thu, Nov 27, 2014 at 12:58 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, On 27/11/14 10:16, Julia Boudniatsky wrote: Hello, We use get_redirects(*) and t_load_contacts in script. modparam(tm, contacts_avp, $avp(contacts)) In versions previous to 4.1 print all contacts: $(avp(contacts[*]) delete all contacts: $(avp(contacts[*])=$null From 4.1 this avp is changed to xavp structure. What is the structure name and value name of xavp for print in log $xavp(contacts=?) ? there are couple of subfileds in this xavp: uri dst_uri path sock instance flags q_flag ruid ua Is it possible to delete xavp? Yes, as with avp, assign $null to it. Cheers, Daniel -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] kamailio with pipelimit crashes when CPU load average 2
Hello, Sometimes kamailio with pipelimit crashes with segmentation fault, when CPU load average 2. The problem is not reproduced in the LAB (we used stress –c ). Please find attached core file. Thank you, Julia Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 4096 -u kamailio -g kamail'. Program terminated with signal 11, Segmentation fault. #0 0x7fb4d4ab9766 in do_update_load (ticks=value optimized out, tl=value optimized out, data=value optimized out) at pipelimit.c:262 262 memset(spcs, '-', load / 4); Missing separate debuginfos, use: debuginfo-install MySQL-shared-5.5.27-1.el6.x86_64 glibc-2.12-1.47.el6.x86_64 libgcc-4.4.6-3.el6.x86_64 (gdb) bt full #0 0x7fb4d4ab9766 in do_update_load (ticks=value optimized out, tl=value optimized out, data=value optimized out) at pipelimit.c:262 err = -nan(0x8) output = value optimized out spcs = '-' repeats 51 times #1 update_cpu_load (ticks=value optimized out, tl=value optimized out, data=value optimized out) at pipelimit.c:276 No locals. #2 pl_timer_handle (ticks=value optimized out, tl=value optimized out, data=value optimized out) at pipelimit.c:594 No locals. #3 0x005185e5 in timer_list_expire () at timer.c:894 tl = 0x7fb3d42e8ae0 ret = value optimized out #4 timer_handler () at timer.c:959 saved_ticks = 3557652736 run_slow_timer = 0 i = 525 #5 timer_main () at timer.c:998 No locals. #6 0x00462855 in main_loop () at main.c:1704 i = value optimized out pid = value optimized out si = 0x0 si_desc = udp receiver child=7 sock=vm-kamredn1:5060\000\000\000\000\000\000\220(\006?´\177\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000\000\260\b?³\177\000\000\001\000\000\000\000\000\000\000 \264\214\000\000\000\000\000\000\000@\000\001, '\000' repeats 11 times, \001\000\000\000\000\000\000 nrprocs = value optimized out #7 0x0046413c in main (argc=value optimized out, argv=value optimized out) at main.c:2546 cfg_stream = value optimized out c = value optimized out r = value optimized out tmp = 0x7fff58446f5e tmp_len = 0 options = 0x5a3868 :f:cm:M:dVIhEb:l:L:n:vrRDTN:W:w:t:u:g:P:G:SQ:O:a:A: ret = -1 seed = 1549924303 rfd = value optimized out debug_save = value optimized out debug_flag = value optimized out dont_fork_cnt = value optimized out n_lst = value optimized out p = value optimized out (gdb) ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Problem with locally generated BYE in dialog timeout.
We use dialog module in our configuration. uac_replace_from/to is called after dlg_manage(). From UAC documentation: If you create a dialog ( with dlg_manage() ) before calling uac_replace_from(), this avp will not be needed. The values of the uris will be stored as dialog variables. And we have problem only with locally generated BYE, all other local requests (ACK, CANCEL) works fine. Thank you, Julia On Wed, Oct 1, 2014 at 4:28 PM, Julia Boudniatsky juli...@gmail.com wrote: Hello, We use dialog module in our configuration. uac_replace_from/to is called after dlg_manage(). restore_mode is auto. URIs are modified automatically in all subsequent local requests, exclude BYE generated in dlg timeout. In this case original URIs are sent to both caller and calee sides. If call going through only one kamailio server, all works fine. Problem starts with a chain of servers with from/to manipulation. When timeout occurs in one kamailio server, calee kamailio server receives BYE with original (not modified) URIs and URI restore gets wrong parsing result. Call clears in caller side and stay connected in caller. Whether there is any solution? BR , Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Problem with locally generated BYE in dialog timeout.
Storing the values in dialog module doesn't help. I updated headers in event_route[tm:local-request] by subst_hf with saved dialog variables (uac_replace_to/from has been used in branch route). Now it's working. Great! Thank you, Julia On Thu, Oct 2, 2014 at 9:11 AM, Daniel-Constantin Mierla mico...@gmail.com wrote: Storing the values in dialog module can be useful, you need to enable it: - http://kamailio.org/docs/modules/stable/modules/uac.html#uac.p.restore_dlg But I am not sure if that is making dialog to use them automatically for BYE requests. What you can try is to enable event_route[tm:local-request] to catch local generated BYEs and update the headers there (either from dialog variables or from other source if you can determine that). Cheers, Daniel On 02/10/14 09:00, Julia Boudniatsky wrote: We use dialog module in our configuration. uac_replace_from/to is called after dlg_manage(). From UAC documentation: If you create a dialog ( with dlg_manage() ) before calling uac_replace_from(), this avp will not be needed. The values of the uris will be stored as dialog variables. And we have problem only with locally generated BYE, all other local requests (ACK, CANCEL) works fine. Thank you, Julia On Wed, Oct 1, 2014 at 4:28 PM, Julia Boudniatsky juli...@gmail.com wrote: Hello, We use dialog module in our configuration. uac_replace_from/to is called after dlg_manage(). restore_mode is auto. URIs are modified automatically in all subsequent local requests, exclude BYE generated in dlg timeout. In this case original URIs are sent to both caller and calee sides. If call going through only one kamailio server, all works fine. Problem starts with a chain of servers with from/to manipulation. When timeout occurs in one kamailio server, calee kamailio server receives BYE with original (not modified) URIs and URI restore gets wrong parsing result. Call clears in caller side and stay connected in caller. Whether there is any solution? BR , Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] event_route[core:receive-parse-error] question
Hello,
I try to use event_route[core:receive-parse-error] in 4.1.6
event_route[core:receive-parse-error] {
xlog(L_WARN, Event-parse-error: $rm from
$avp(inc_carrier)/n$mb/n);
}
When core parse error occurs , *log message is not printed*.
What is wrong?
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] event_route[core:receive-parse-error] question
I understand my mistake.
It's working when message is broken.
I wanted to use it for bad SDP.
We have a problem with SDP from some users.
In error of parsing SDP on log printed only wrong part of SDP
and correlation to call is very difficult.
Thank you,
Julia
On Wed, Oct 1, 2014 at 3:54 PM, Daniel-Constantin Mierla mico...@gmail.com
wrote:
Hello,
iirc, the event route is executed only when the sip request is so broken
not to make it till config file execution.
In your previous email on this topic that I had in mind to reply but got
forgotten, you refer to From. That is not part of the basic parsing (again,
iirc), you should catch that using sanity_check() function from sanity
module, using it somewhere at the top of config request route (see default
config, it is in the route[REQINIT)).
Cheers,
Daniel
On 01/10/14 14:38, Julia Boudniatsky wrote:
Hello,
I try to use event_route[core:receive-parse-error] in 4.1.6
event_route[core:receive-parse-error] {
xlog(L_WARN, Event-parse-error: $rm from
$avp(inc_carrier)/n$mb/n);
}
When core parse error occurs , *log message is not printed*.
What is wrong?
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Problem with locally generated BYE in dialog timeout.
Hello, We use dialog module in our configuration. uac_replace_from/to is called after dlg_manage(). restore_mode is auto. URIs are modified automatically in all subsequent local requests, exclude BYE generated in dlg timeout. In this case original URIs are sent to both caller and calee sides. If call going through only one kamailio server, all works fine. Problem starts with a chain of servers with from/to manipulation. When timeout occurs in one kamailio server, calee kamailio server receives BYE with original (not modified) URIs and URI restore gets wrong parsing result. Call clears in caller side and stay connected in caller. Whether there is any solution? BR , Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.
Hello,
Some Uri transformations stopped working after upgrade from 3.3 to 4.1.6.
*To: sip:01412127775678;cic=012;csel=noind@10.25.153.150:5060
http://noind@10.25.153.150:5060;user=phone*
*In v3.3*
$tu({uri.params}) return: cic=012;csel=noind
$tu({uri.param,cic}) return:012
*In v4.1.6*
$tu({uri.params}) return : user=phone
$tu({uri.param,cic}) return :
Best regards,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Uri transformations stopped working after upgrade from 3.3 to 4.1.6.
$(tu{uri.uparam,cic}) gets ERROR wrong format,
$(tu{uri.uparam}) return : phone
So, uparam return the value of parameter user .
I solved a problem by usage $(tu{param.value,cic,;})
BR
Julia
On Tue, Sep 30, 2014 at 12:09 PM, Daniel-Constantin Mierla
mico...@gmail.com wrote:
Hello,
On 30/09/14 10:41, Julia Boudniatsky wrote:
Hello,
Some Uri transformations stopped working after upgrade from 3.3 to 4.1.6.
*To: sip:01412127775678;cic=012;csel=noind@10.25.153.150:5060
http://noind@10.25.153.150:5060;user=phone*
*In v3.3*
$tu({uri.params}) return: cic=012;csel=noind
$tu({uri.param,cic}) return:012
*In v4.1.6*
$tu({uri.params}) return : user=phone
$tu({uri.param,cic}) return :
looks like this is happening as a fix, as the cic is an username
parameter, not a uri parameter.
You should use {uri.uparam,cic}:
http://www.kamailio.org/wiki/cookbooks/devel/transformations#uriuparam
Cheers,
Daniel
--
Daniel-Constantin Mierlahttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] event_route[core:receive-parse-error] is not executed 4.1.6
Hello,
I try to use an
event_route[core:receive-parse-error] {
xlog(L_WARN, Parse-error: $rm from
$avp(inc_carrier)/n$mb/n);
}
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] event_route[core:receive-parse-error] is not executed 4.1.6
Hello,
I try to use an
event_route[core:receive-parse-error] {
xlog(L_WARN, Event-parse-error:
$rm from $avp(inc_carrier)/n$mb/n);
}
corelog=1
debug=0
kamailio 4.1.6 from source
Wrong header From is simulated by SIPP.
In log I receive only ERROR:core [parser/parse_from.c:79]:
parse_from_header() ..
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] permanent 1.5 s timer interval in module pipelimit
Hello all, Timer pl_timer in pipelimit.c is defined as MS_TO_TICKS(1500) instead of timer_interval (in versions 3.3 - 4.1). I found a patch that solves the same problem in the ratelimit module: Module: sip-router Branch: 3.1 Commit: f027ca95a2a1818cd40e4ed6d4358a76d18252ad URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=f027ca9 5a2a1818cd40e4ed6d4358a76d18252ad http://git.sip-router.org/cgi-bin/gitweb.cgi/... Author: Marius Zbihlei Committer: Marius Zbihlei Date: Mon Apr 11 13:45:10 2011 +0300 modules/ratelimit Timer was ran at a 1.5 s interval instead of timer_interval, thus rendering TAILDROP alg unusable (cherry picked from commit 3a06d7d3561f889c84249eaa5ec7a5b79a2a23bd) Regards, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] RTPProxy on a different machine than Kamailio problem
Hello, I try to run RTPProxy on a different machine than Kamailio (Kamailio IP is 10.25.1.5 without NAT) for rtp recording. Remote machine has an IP Address of 10.25.1.1 and started with /usr/local/bin/rtpproxy -l 10.25.1.1 -s udp:*:7722 -F -P -r/log/rtp_trace In Kamailio configuration file: modparam(rtpproxy, rtpproxy_sock, udp:10.25.1.1:7722) And then, we receive an error after Kamailio start: /usr/local/sbin/kamailio[24510]: ERROR: rtpproxy [rtpproxy.c:1527]: timeout waiting reply from a RTP proxy /usr/local/sbin/kamailio[24510]: ERROR: rtpproxy [rtpproxy.c:1536]: proxy udp:10.25.153.149:7722 does not respond, disable it /usr/local/sbin/kamailio[24510]: WARNING: rtpproxy [rtpproxy.c:1404]: RTP proxy went down during version query /usr/local/sbin/kamailio[24510]: WARNING: rtpproxy [rtpproxy.c:1430]: support for RTP proxy udp:10.25.153.149:7722 has been disabled temporarily In netstat -a: udp0 0 KAMnet-JAF-TST-01:53522 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED udp0 0 KAMnet-JAF-TST-01:36633 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED udp0 0 KAMnet-JAF-TST-01:32925 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED It works, when Kamailio RTPproxy are configured in the same machine, with modparam(rtpproxy, rtpproxy_sock, udp:localhost:7722), Is there something wrong in configuration of remote mode? Thanks for any help, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] RTPProxy on a different machine than Kamailio problem
Thank you Daniel. We tried with -s udp:10.25.1.1:7722, but received the same result. We see in log file of rtpproxy and in tcpdump in Kamailio, that remote rtpproxy send response to all requests from Kamailio. Best regards, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Tuesday, December 24, 2013 11:33 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] RTPProxy on a different machine than Kamailio problem Hello, from logs, kamailio cannot communicate with rtpproxy. I never used rtpproxy with -s udp:*:7722, so I don't know if it is valid, you should try with -s udp:10.25.1.1:7722 Cheers, Daniel On 24/12/13 09:45, Julia wrote: Hello, I try to run RTPProxy on a different machine than Kamailio (Kamailio IP is 10.25.1.5 without NAT) for rtp recording. Remote machine has an IP Address of 10.25.1.1 and started with /usr/local/bin/rtpproxy -l 10.25.1.1 -s udp:*:7722 -F -P -r/log/rtp_trace In Kamailio configuration file: modparam(rtpproxy, rtpproxy_sock, udp:10.25.1.1:7722) And then, we receive an error after Kamailio start: /usr/local/sbin/kamailio[24510]: ERROR: rtpproxy [rtpproxy.c:1527]: timeout waiting reply from a RTP proxy /usr/local/sbin/kamailio[24510]: ERROR: rtpproxy [rtpproxy.c:1536]: proxy udp:10.25.153.149:7722 udp:10.25.153.149:7722 does not respond, disable it /usr/local/sbin/kamailio[24510]: WARNING: rtpproxy [rtpproxy.c:1404]: RTP proxy went down during version query /usr/local/sbin/kamailio[24510]: WARNING: rtpproxy [rtpproxy.c:1430]: support for RTP proxy udp:10.25.153.149:7722 udp:10.25.153.149:7722 has been disabled temporarily In netstat -a: udp0 0 KAMnet-JAF-TST-01:53522 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED udp0 0 KAMnet-JAF-TST-01:36633 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED udp0 0 KAMnet-JAF-TST-01:32925 vm-kamnet-dev01.bgtehi:7722 ESTABLISHED It works, when Kamailio RTPproxy are configured in the same machine, with modparam(rtpproxy, rtpproxy_sock, udp:localhost:7722), Is there something wrong in configuration of remote mode? Thanks for any help, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok.
OK We will wait for 4.1 Thank you, Julia _ From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Monday, November 11, 2013 9:43 AM To: Julia; 'Kamailio (SER) - Users Mailing List' Cc: 'Uri Shacked' Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Hello, the changes came after 4.0 was releases and affected a tm function with impact in many other places. They were not backported not to introduce unknown side effects. They will be part of next major release, v4.1, to be out in few weeks. Cheers, Daniel On 11/10/13 8:20 PM, Julia wrote: Hello, We successful upgraded Kamailio from 3.3 to 4.0.4 and get the problem with BYE dialog timeout as was in 3.0.1 Daniel committed a set of patches, that solved the problem (please, see below in previous mails). But these patches are not a part of 4.0.4, why? 4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b 57ed79b9d45c29d37c405c3fa582c1d1011a2315 f22dcd559c739dd99275cd2444cf481d458d2fab ff890a4eee1888ed3e1e080a18bd72124ab99690 aefea5477dc7878d5e818628e04ddcb088fd2858 Thank you, Julia _ From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Monday, April 29, 2013 3:11 PM To: Julia; 'Kamailio (SER) - Users Mailing List' Cc: 'Uri Shacked' Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Hello, there are few follow up patches that you need to get, here are the commits id: 57ed79b9d45c29d37c405c3fa582c1d1011a2315 f22dcd559c739dd99275cd2444cf481d458d2fab ff890a4eee1888ed3e1e080a18bd72124ab99690 aefea5477dc7878d5e818628e04ddcb088fd2858 Cheers, Daniel On 4/29/13 11:31 AM, Julia wrote: Thank you, The patch solves the problem with dlgtimeout BYE (also for chain of proxy servers), but causes a new one. Now, OPTIONs from dispatcher module sent with angle brackets, but 200 OK (received with same format) are ignored by kamailio. ERROR: dispatcher [dispatch.c:2373]: Setting the state failed (sip:) . BR, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, April 25, 2013 4:24 PM To: Uri Shacked Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Here is the link to the patch: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blobdiff;f=modul es/tm/t_msgbuilder.c;h=b5ff3094af2594e62a050ccc56768ad9237eb633;hp=aa0144c84 43760c9e81ee121ef907be812fa9da8;hb=4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b; hpb=744a8d317b894a1360e3441a9e69ac9190a1745b You have to add the lines starting with '+' in t_msgbuilder.c -- there are six. Not sure it really works replacing the entire file, it is safe to apply the patch. Cheers, Daniel On 4/25/13 3:17 PM, Uri Shacked wrote: I have no internet access from my kamailio servers. where can i download it and install? or just download the t_msgbuilder.c and reinstall 3.3.2 ? On Thu, Apr 25, 2013 at 3:55 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, I committed a patch to add angle brackets around From/To URI for local generated requests. Here is the link to commit: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4e4b1339 bfd3a832f5feeb1d2a2380c7455ec82b No time to test it, so give it a try. If you are using 4.0 (even 3.3) should work by just cherry-picking. Let me know if works fine. Depending on feedback will be part of 4.0.1 (out in few hours), or let to be backported for 4.0.2. Cheers, Daniel On 4/25/13 2:23 PM, Uri Shacked wrote: Hi, As i wrote, when the BYE is normal not generated form dlg_timeout. srv2 that forwards it, does it OK. The TO/From headers in my scenario are the same as the initial request in both servers (there are 2 legs for each call (incoming and outgoing), on each leg i use the same initial headers.Ii hope i was more clear now. Thanks, Uri On Thu, Apr 25, 2013 at 2:50 PM, Klaus Darilion klaus.mailingli...@pernau.at wrote: IMO the timeout-triggered BYE should have identical From/To headers as the initial request - otherwise it may cause issues with clients that are strict, or rely on identical headers (like in your setup). regards Klaus On 25.04.2013 13 tel:25.04.2013%2013 :30, Uri Shacked wrote: Hi, Following this issue, and the issue BYE dialog timeout bad syntax from Julia. I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to srv2 that forwards the BYE to the next sip server (some other server...). I can definitely see that the BYE that is being forward is malformed. The TO header info is not complete (the port section for example). When a normal bye is received from srv1 (not dlg_timeout) all works fine. One thing that i do in this scenario, on srv2 i use uac_replace() on the TO header. So, it is OK that the final destination is different (i do translations). I attached the BYE from both servers
[SR-Users] Kamailio 4.0.4 crash t_load_contact();
Hello, After upgrade from 3.3 to 4.0.4 Kamailio crashed when the first call after application start is a call with failure route: get_redirect(); t_load_contact(); t_next_contacts(); Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:78]: get_redirect(): resume branch=0 Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:85]: get_redirect(): checking branch=0 (added=0) Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:89]: get_redirect(): branch=0 is a redirect (added=0) Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:165]: sort_contacts(): sort_contacts: sip:39988202@10.25.147.241:5060;user=phone q=250 Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:165]: sort_contacts(): sort_contacts: sip:39988202@10.25.148.41:5060;user=phone q=500 Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:297]: shmcontact2dset(): adding contact sip:39988202@10.25.147.241:5060;user=phone Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: core [sruid.c:176]: sruid_next(): new sruid is [rdir-5280b7a9-2874-1] (1 / 20) Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: uac_redirect [rd_funcs.c:297]: shmcontact2dset(): adding contact sip:39988202@10.25.148.41:5060;user=phone Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: core [sruid.c:176]: sruid_next(): new sruid is [rdir-5280b7a9-2874-2] (2 / 20) Nov 11 12:55:48 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10356]: DEBUG: tm [t_serial.c:166]: t_load_contacts(): nr_branches is 2 Nov 11 12:56:00 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10336]: ALERT: core [main.c:788]: handle_sigs(): child process 10356 exited by a signal 11 Nov 11 12:56:00 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10336]: ALERT: core [main.c:791]: handle_sigs(): core was generated Nov 11 12:56:00 vm-KAMnet-dev01 /usr/local/sbin/kamailio[10336]: INFO: core [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLD Regards, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Wrong To header in CANCEL, when To has been rewritten by uac_replace_to() in branch route
O.K
We will soon upgrade to 4.0.4
Thank you.
Julia
_
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Thursday, November 07, 2013 9:32 PM
To: Julia; 'Kamailio (SER) - Users Mailing List'
Subject: Re: [SR-Users] Wrong To header in CANCEL, when To has been
rewritten by uac_replace_to() in branch route
Hello,
On 11/7/13 10:39 AM, Julia wrote:
Hello Daniel,
Version 3.3.5,
We use uac_replace_to() in branch route and without patch the To in local
CANCEL is taken from original INVITE.
3.3.x doesn't have it. The patch you mentioned is fixing it, but not like it
is on 4.0 or master branch -- it will just make it always to use to header
from outgoing branch. The right way is to backport from 4.0 or master, so it
preserves the behaviour when upgrading form 3.3 to newer version. There is
an item on tracker as well, but no developer jumped on it and I couldn't
find the time to check all changes towards 4.0 and do the patch. If someone
will provide it, I will review it quickly and commit.
Cheers,
Daniel
Thank you,
Julia
_
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, November 07, 2013 11:30 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Wrong To header in CANCEL, when To has been
rewritten by uac_replace_to() in branch route
Hello,
what version do you have and what function is used to change the To header?
If you use uac_replace_to() with latest stable version, the new To header
should be used for local CANCEL and ACK.
Cheers,
Daniel
On 11/7/13 9:31 AM, Julia wrote:
Hello,
I know it was already discussed, that not recommended to modify To header
and no routing should ever be done on To.
But as long as there are carriers that do it, we need full support for this
manipulation for all messages in the call flow.
I found in list a few mails with the same problem of wrong header To in
CANCEL after To rewriting.
And one solution from Vitaliy Aleksandrov :
http://lists.sip-router.org/pipermail/sr-dev/2012-October/016657.html
Kamailio builds To header from the received INVITE.
Patch to fix it:
--- ./kamailio-3.2.3/modules/tm/t_cancel.c 2012-08-22
10:39:21.0 +0300
+++ ./kamailio-3.2.3-fixed/modules/tm/t_cancel.c 2012-10-01
18:25:57.0 +0300
@@ -284,7 +284,7 @@
if (cfg_get(tm, tm_cfg, reparse_invite)) {
/* build the CANCEL from the INVITE which was sent out */
cancel = build_local_reparse(t, branch, len, CANCEL,
CANCEL_LEN,
- t-to
+ NULL
#ifdef CANCEL_REASON_SUPPORT
,
reason
#endif /* CANCEL_REASON_SUPPORT */
We use header To manipulation in branch route (after failure route) and
this patch solved our problem with To in CANCEL.
But a patch is not committed.
Is it possible to commit this solution?
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda http://twitter.com/#%21/miconda -
http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok.
Hello, We successful upgraded Kamailio from 3.3 to 4.0.4 and get the problem with BYE dialog timeout as was in 3.0.1 Daniel committed a set of patches, that solved the problem (please, see below in previous mails). But these patches are not a part of 4.0.4, why? 4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b 57ed79b9d45c29d37c405c3fa582c1d1011a2315 f22dcd559c739dd99275cd2444cf481d458d2fab ff890a4eee1888ed3e1e080a18bd72124ab99690 aefea5477dc7878d5e818628e04ddcb088fd2858 Thank you, Julia _ From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Monday, April 29, 2013 3:11 PM To: Julia; 'Kamailio (SER) - Users Mailing List' Cc: 'Uri Shacked' Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Hello, there are few follow up patches that you need to get, here are the commits id: 57ed79b9d45c29d37c405c3fa582c1d1011a2315 f22dcd559c739dd99275cd2444cf481d458d2fab ff890a4eee1888ed3e1e080a18bd72124ab99690 aefea5477dc7878d5e818628e04ddcb088fd2858 Cheers, Daniel On 4/29/13 11:31 AM, Julia wrote: Thank you, The patch solves the problem with dlgtimeout BYE (also for chain of proxy servers), but causes a new one. Now, OPTIONs from dispatcher module sent with angle brackets, but 200 OK (received with same format) are ignored by kamailio. ERROR: dispatcher [dispatch.c:2373]: Setting the state failed (sip:) . BR, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, April 25, 2013 4:24 PM To: Uri Shacked Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Here is the link to the patch: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blobdiff;f=modul es/tm/t_msgbuilder.c;h=b5ff3094af2594e62a050ccc56768ad9237eb633;hp=aa0144c84 43760c9e81ee121ef907be812fa9da8;hb=4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b; hpb=744a8d317b894a1360e3441a9e69ac9190a1745b You have to add the lines starting with '+' in t_msgbuilder.c -- there are six. Not sure it really works replacing the entire file, it is safe to apply the patch. Cheers, Daniel On 4/25/13 3:17 PM, Uri Shacked wrote: I have no internet access from my kamailio servers. where can i download it and install? or just download the t_msgbuilder.c and reinstall 3.3.2 ? On Thu, Apr 25, 2013 at 3:55 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, I committed a patch to add angle brackets around From/To URI for local generated requests. Here is the link to commit: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4e4b1339 bfd3a832f5feeb1d2a2380c7455ec82b No time to test it, so give it a try. If you are using 4.0 (even 3.3) should work by just cherry-picking. Let me know if works fine. Depending on feedback will be part of 4.0.1 (out in few hours), or let to be backported for 4.0.2. Cheers, Daniel On 4/25/13 2:23 PM, Uri Shacked wrote: Hi, As i wrote, when the BYE is normal not generated form dlg_timeout. srv2 that forwards it, does it OK. The TO/From headers in my scenario are the same as the initial request in both servers (there are 2 legs for each call (incoming and outgoing), on each leg i use the same initial headers.Ii hope i was more clear now. Thanks, Uri On Thu, Apr 25, 2013 at 2:50 PM, Klaus Darilion klaus.mailingli...@pernau.at wrote: IMO the timeout-triggered BYE should have identical From/To headers as the initial request - otherwise it may cause issues with clients that are strict, or rely on identical headers (like in your setup). regards Klaus On 25.04.2013 13 tel:25.04.2013%2013 :30, Uri Shacked wrote: Hi, Following this issue, and the issue BYE dialog timeout bad syntax from Julia. I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to srv2 that forwards the BYE to the next sip server (some other server...). I can definitely see that the BYE that is being forward is malformed. The TO header info is not complete (the port section for example). When a normal bye is received from srv1 (not dlg_timeout) all works fine. One thing that i do in this scenario, on srv2 i use uac_replace() on the TO header. So, it is OK that the final destination is different (i do translations). I attached the BYE from both servers. Any ideas? Thanks, Uri You probably meant the To and From headers, I'm guessing. Yeah, as long as there is no display name component, URIs in headers like that don't have to go in s. The way Kamailio sends it is grammatically valid, per RFC 3261. The user agents are at fault for not understanding it correctly. Alex Balashov abalashov at evaristesys.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: /BYE headers? Which headers? Uri Shacked ushacked at gmail.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: Hi, I think there is a bug
[SR-Users] Wrong To header in CANCEL, when To has been rewritten by uac_replace_to() in branch route
Hello,
I know it was already discussed, that not recommended to modify To header
and no routing should ever be done on To.
But as long as there are carriers that do it, we need full support for this
manipulation for all messages in the call flow.
I found in list a few mails with the same problem of wrong header To in
CANCEL after To rewriting.
And one solution from Vitaliy Aleksandrov :
http://lists.sip-router.org/pipermail/sr-dev/2012-October/016657.html
Kamailio builds To header from the received INVITE.
Patch to fix it:
--- ./kamailio-3.2.3/modules/tm/t_cancel.c 2012-08-22
10:39:21.0 +0300
+++ ./kamailio-3.2.3-fixed/modules/tm/t_cancel.c 2012-10-01
18:25:57.0 +0300
@@ -284,7 +284,7 @@
if (cfg_get(tm, tm_cfg, reparse_invite)) {
/* build the CANCEL from the INVITE which was sent out */
cancel = build_local_reparse(t, branch, len, CANCEL,
CANCEL_LEN,
- t-to
+ NULL
#ifdef CANCEL_REASON_SUPPORT
,
reason
#endif /* CANCEL_REASON_SUPPORT */
We use header To manipulation in branch route (after failure route) and
this patch solved our problem with To in CANCEL.
But a patch is not committed.
Is it possible to commit this solution?
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Wrong To header in CANCEL, when To has been rewritten by uac_replace_to() in branch route
Hello Daniel,
Version 3.3.5,
We use uac_replace_to() in branch route and without patch the To in local
CANCEL is taken from original INVITE.
Thank you,
Julia
_
From: sr-users-boun...@lists.sip-router.org
[mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Thursday, November 07, 2013 11:30 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Wrong To header in CANCEL, when To has been
rewritten by uac_replace_to() in branch route
Hello,
what version do you have and what function is used to change the To header?
If you use uac_replace_to() with latest stable version, the new To header
should be used for local CANCEL and ACK.
Cheers,
Daniel
On 11/7/13 9:31 AM, Julia wrote:
Hello,
I know it was already discussed, that not recommended to modify To header
and no routing should ever be done on To.
But as long as there are carriers that do it, we need full support for this
manipulation for all messages in the call flow.
I found in list a few mails with the same problem of wrong header To in
CANCEL after To rewriting.
And one solution from Vitaliy Aleksandrov :
http://lists.sip-router.org/pipermail/sr-dev/2012-October/016657.html
Kamailio builds To header from the received INVITE.
Patch to fix it:
--- ./kamailio-3.2.3/modules/tm/t_cancel.c 2012-08-22
10:39:21.0 +0300
+++ ./kamailio-3.2.3-fixed/modules/tm/t_cancel.c 2012-10-01
18:25:57.0 +0300
@@ -284,7 +284,7 @@
if (cfg_get(tm, tm_cfg, reparse_invite)) {
/* build the CANCEL from the INVITE which was sent out */
cancel = build_local_reparse(t, branch, len, CANCEL,
CANCEL_LEN,
- t-to
+ NULL
#ifdef CANCEL_REASON_SUPPORT
,
reason
#endif /* CANCEL_REASON_SUPPORT */
We use header To manipulation in branch route (after failure route) and
this patch solved our problem with To in CANCEL.
But a patch is not committed.
Is it possible to commit this solution?
Thank you,
Julia
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] topoch and xHTTP
Thank you Daniel, It works fine (without errors) with your patch. Best regards, Julia _ From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Monday, May 27, 2013 5:15 PM To: Julia; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] topoch and xHTTP Hello, I pushed over the weekend a patch that should fix it. Practically was an error message, but the processing was going on further without issues. topoh was executed for http requests and shouldn't have been like that. Would be appreciated if you can test and report whether is fine now or not. The patch is now in branches 3.3, 4.0 and master. Cheers, Daniel On 5/23/13 2:50 PM, Julia wrote: It's an incoming request Debug3 : May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [ip_addr.c:247]: tcpconn_new: new tcp connection: 80.80.80.241 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:1089]: tcpconn_new: on port 51898, type 2 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:1400]: tcpconn_add: hashes: 902:996:7, 4 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [io_wait.h:390]: DBG: io_watch_add(0x82cec0, 57, 2, 0x7f8481de59a0), fd_no=48 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [io_wait.h:617]: DBG: io_watch_del (0x82cec0, 57, -1, 0x0) fd_no=49 called May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:4295]: tcp: DBG: sending to child, events 1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:3966]: selected tcp worker 3 33(29526) for activity on [tcp:172.16.60.113:5060], 0x7f8481de59a0 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_read.c:1354]: received n=8 con=0x7f8481de59a0, fd=11 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:624]: SIP Request: May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:626]: method: GET May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:628]: uri: /Update May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:630]: version: HTTP/1.1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:104]: found end of header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: ERROR: core [parser/parse_from.c:60]: ERROR:parse_from_header: bad msg or missing FROM header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: ERROR: topoh [topoh_mod.c:215]: cannot parse FROM header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:624]: SIP Request: May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:626]: method: GET May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:628]: uri: /Update May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:630]: version: HTTP/1.1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:104]: found end of header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [receive.c:149]: After parse_msg... May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: xhttp [xhttp_mod.c:345]: new fake msg created (300 bytes):#012GET /Update HTTP/1.1#015#012Via: SIP/2.0/TCP 80.80.80.241:51898#015#012Accept: text/html, application/xhtml+xml, */*#015#012Accept-Language: he-IL#015#012User-Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; Trident/6.0)#015#012Accept-Encoding: gzip, deflate#015#012Host: 172.16.60.113:5060#015#012DNT: 1#015#012Connection: Keep-Alive#015#012#015#012 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:624]: SIP Request: May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:626]: method: GET May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:628]: uri: /Update May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:630]: version: HTTP/1.1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/parse_via.c:2561]: end of header reached, state=5 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:511]: parse_headers: Via found, flags=2 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:513]: parse_headers: this is the first via May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: NOTICE: script: HTTP HANDLER /Update May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: exec [exec_mod.c:208]: executing [kamctl fifo mt_list] May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [main.c:886]: SIGCHLD received: we do not worry about grand-children May 23 15:44
[SR-Users] topoch and xHTTP
Hello, I am testing the xHTTP module on kamailio-3.3 with topology hiding (topoch) and I get parsing error for each received HTTP message: /usr/local/sbin/kamailio[2937]: ERROR: core [parser/parse_from.c:60]: ERROR:parse_from_header: bad msg or missing FROM header /usr/local/sbin/kamailio[2937]: ERROR: topoh [topoh_mod.c:215]: cannot parse FROM header Is it configuration issue? Thanks, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] topoch and xHTTP
RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:624]: SIP Request: May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:626]: method: HTTP/1.1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:628]: uri: 200 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:630]: version: OK May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/parse_via.c:2561]: end of header reached, state=5 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:511]: parse_headers: Via found, flags=2 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:513]: parse_headers: this is the first via May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:202]: DEBUG: get_hdr_body : content_length=61 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [parser/msg_parser.c:104]: found end of header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: ERROR: core [parser/parse_from.c:60]: ERROR:parse_from_header: bad msg or missing FROM header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: ERROR: topoh [topoh_mod.c:215]: cannot parse FROM header May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_main.c:2313]: tcp_send: send from reader (29526 (33)), reusing fd May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_main.c:2549]: tcp_send: sending... May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_main.c:2583]: tcp_send: after real write: c= 0x7f8481de59a0 n=203 fd=11 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_main.c:2584]: tcp_send: buf=#012HTTP/1.1 200 OK#015#012Via: SIP/2.0/TCP 80.80.80.241:51898#015#012Content-Type: text/html#015#012Server: kamailio (3.3.1 (x86_64/linux))#015#012Content-Length: 61#015#012#015#012htmlbodyLastUpdated 0 result null;null;/body/html May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:3617]: handle_ser_child: read response= 7f8481de59a0, -1, fd -1 from 33 (29526) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [usr_avp.c:644]: DEBUG:destroy_avp_list: destroying list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [xavp.c:365]: destroying xavp list (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [receive.c:293]: receive_msg: cleaning up May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [io_wait.h:390]: DBG: io_watch_add(0x871120, 11, 2, 0x7f8481de59a0), fd_no=1 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [io_wait.h:617]: DBG: io_watch_del (0x871120, 11, -1, 0x10) fd_no=2 called May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_read.c:1281]: releasing con 0x7f8481de59a0, state -2, fd=11, id=4 May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29526]: DEBUG: core [tcp_read.c:1282]: extra_data (nil) May 23 15:44:57 RNDSRV /usr/local/sbin/kamailio[29536]: DEBUG: core [tcp_main.c:3378]: handle_tcp_child: reader response= 7f8481de59a0, -2 from 3 Thank you, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, May 23, 2013 3:10 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] topoch and xHTTP Hello, iirc, topoh callbacks are executed only for incoming sip traffic. Do you try to relay the http request? That doesn't work, kamailio works only as http server, not proxy. If it is the case of incoming request, can you run with debug=3 and send the output of such case here? Cheers, Daniel On 5/23/13 12:21 PM, Julia wrote: Hello, I am testing the xHTTP module on kamailio-3.3 with topology hiding (topoch) and I get parsing error for each received HTTP message: /usr/local/sbin/kamailio[2937]: ERROR: core [parser/parse_from.c:60]: ERROR:parse_from_header: bad msg or missing FROM header /usr/local/sbin/kamailio[2937]: ERROR: topoh [topoh_mod.c:215]: cannot parse FROM header Is it configuration issue? -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http
Re: [SR-Users] max number of pipes for pipelimit module?
It's great! Thank you, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Tuesday, May 07, 2013 10:19 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] max number of pipes for pipelimit module? Hello, On 5/6/13 7:30 PM, Julia wrote: Hello, Is there a limit on the max number of pipes for pipelimit module? no, there is no limit. You can define as many as you want in database table, provided that you have enough memory to store the associated structures in memory (which is hard to fit, unless you run kamailio with really low memory). Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013 * http://asipto.com/u/katu * ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok.
Thank you, The patch solves the problem with dlgtimeout BYE (also for chain of proxy servers), but causes a new one. Now, OPTIONs from dispatcher module sent with angle brackets, but 200 OK (received with same format) are ignored by kamailio. ERROR: dispatcher [dispatch.c:2373]: Setting the state failed (sip:) . BR, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, April 25, 2013 4:24 PM To: Uri Shacked Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Here is the link to the patch: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blobdiff;f=modul es/tm/t_msgbuilder.c;h=b5ff3094af2594e62a050ccc56768ad9237eb633;hp=aa0144c84 43760c9e81ee121ef907be812fa9da8;hb=4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b; hpb=744a8d317b894a1360e3441a9e69ac9190a1745b You have to add the lines starting with '+' in t_msgbuilder.c -- there are six. Not sure it really works replacing the entire file, it is safe to apply the patch. Cheers, Daniel On 4/25/13 3:17 PM, Uri Shacked wrote: I have no internet access from my kamailio servers. where can i download it and install? or just download the t_msgbuilder.c and reinstall 3.3.2 ? On Thu, Apr 25, 2013 at 3:55 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, I committed a patch to add angle brackets around From/To URI for local generated requests. Here is the link to commit: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4e4b1339 bfd3a832f5feeb1d2a2380c7455ec82b No time to test it, so give it a try. If you are using 4.0 (even 3.3) should work by just cherry-picking. Let me know if works fine. Depending on feedback will be part of 4.0.1 (out in few hours), or let to be backported for 4.0.2. Cheers, Daniel On 4/25/13 2:23 PM, Uri Shacked wrote: Hi, As i wrote, when the BYE is normal not generated form dlg_timeout. srv2 that forwards it, does it OK. The TO/From headers in my scenario are the same as the initial request in both servers (there are 2 legs for each call (incoming and outgoing), on each leg i use the same initial headers.Ii hope i was more clear now. Thanks, Uri On Thu, Apr 25, 2013 at 2:50 PM, Klaus Darilion klaus.mailingli...@pernau.at wrote: IMO the timeout-triggered BYE should have identical From/To headers as the initial request - otherwise it may cause issues with clients that are strict, or rely on identical headers (like in your setup). regards Klaus On 25.04.2013 13 tel:25.04.2013%2013 :30, Uri Shacked wrote: Hi, Following this issue, and the issue BYE dialog timeout bad syntax from Julia. I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to srv2 that forwards the BYE to the next sip server (some other server...). I can definitely see that the BYE that is being forward is malformed. The TO header info is not complete (the port section for example). When a normal bye is received from srv1 (not dlg_timeout) all works fine. One thing that i do in this scenario, on srv2 i use uac_replace() on the TO header. So, it is OK that the final destination is different (i do translations). I attached the BYE from both servers. Any ideas? Thanks, Uri You probably meant the To and From headers, I'm guessing. Yeah, as long as there is no display name component, URIs in headers like that don't have to go in s. The way Kamailio sends it is grammatically valid, per RFC 3261. The user agents are at fault for not understanding it correctly. Alex Balashov abalashov at evaristesys.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: /BYE headers? Which headers? Uri Shacked ushacked at gmail.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: Hi, I think there is a bug with the BYE that is sent to the caller and //callee //when dialog timeout happends. The BYE headers are sent with no or . //So, some sip singaling points decline the BYE. BR, //Uri // ___ //SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing //list //sr-users at lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users //http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- //Sent from my mobile, and thus lacking in the refinement one might //expect from a fully-fledged keyboard. Alex Balashov - Principal //Evariste Systems LLC //235 E Ponce de Leon Ave //Suite 106 //Decatur, GA 30030 //United States //Tel: +1-678-954-0670 tel:%2B1-678-954-0670 //Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ ___ //SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list //sr-users at lists.sip
Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok.
Now it works, Thank you! Julia. _ From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Monday, April 29, 2013 3:11 PM To: Julia; 'Kamailio (SER) - Users Mailing List' Cc: 'Uri Shacked' Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Hello, there are few follow up patches that you need to get, here are the commits id: 57ed79b9d45c29d37c405c3fa582c1d1011a2315 f22dcd559c739dd99275cd2444cf481d458d2fab ff890a4eee1888ed3e1e080a18bd72124ab99690 aefea5477dc7878d5e818628e04ddcb088fd2858 Cheers, Daniel On 4/29/13 11:31 AM, Julia wrote: Thank you, The patch solves the problem with dlgtimeout BYE (also for chain of proxy servers), but causes a new one. Now, OPTIONs from dispatcher module sent with angle brackets, but 200 OK (received with same format) are ignored by kamailio. ERROR: dispatcher [dispatch.c:2373]: Setting the state failed (sip:) . BR, Julia _ From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, April 25, 2013 4:24 PM To: Uri Shacked Cc: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] BUG? - Dialog module timeout BYE is not ok. Here is the link to the patch: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blobdiff;f=modul es/tm/t_msgbuilder.c;h=b5ff3094af2594e62a050ccc56768ad9237eb633;hp=aa0144c84 43760c9e81ee121ef907be812fa9da8;hb=4e4b1339bfd3a832f5feeb1d2a2380c7455ec82b; hpb=744a8d317b894a1360e3441a9e69ac9190a1745b You have to add the lines starting with '+' in t_msgbuilder.c -- there are six. Not sure it really works replacing the entire file, it is safe to apply the patch. Cheers, Daniel On 4/25/13 3:17 PM, Uri Shacked wrote: I have no internet access from my kamailio servers. where can i download it and install? or just download the t_msgbuilder.c and reinstall 3.3.2 ? On Thu, Apr 25, 2013 at 3:55 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, I committed a patch to add angle brackets around From/To URI for local generated requests. Here is the link to commit: - http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=4e4b1339 bfd3a832f5feeb1d2a2380c7455ec82b No time to test it, so give it a try. If you are using 4.0 (even 3.3) should work by just cherry-picking. Let me know if works fine. Depending on feedback will be part of 4.0.1 (out in few hours), or let to be backported for 4.0.2. Cheers, Daniel On 4/25/13 2:23 PM, Uri Shacked wrote: Hi, As i wrote, when the BYE is normal not generated form dlg_timeout. srv2 that forwards it, does it OK. The TO/From headers in my scenario are the same as the initial request in both servers (there are 2 legs for each call (incoming and outgoing), on each leg i use the same initial headers.Ii hope i was more clear now. Thanks, Uri On Thu, Apr 25, 2013 at 2:50 PM, Klaus Darilion klaus.mailingli...@pernau.at wrote: IMO the timeout-triggered BYE should have identical From/To headers as the initial request - otherwise it may cause issues with clients that are strict, or rely on identical headers (like in your setup). regards Klaus On 25.04.2013 13 tel:25.04.2013%2013 :30, Uri Shacked wrote: Hi, Following this issue, and the issue BYE dialog timeout bad syntax from Julia. I have 2 kamailio servers. srv1 creates a dlg_timeout BYE and sends it to srv2 that forwards the BYE to the next sip server (some other server...). I can definitely see that the BYE that is being forward is malformed. The TO header info is not complete (the port section for example). When a normal bye is received from srv1 (not dlg_timeout) all works fine. One thing that i do in this scenario, on srv2 i use uac_replace() on the TO header. So, it is OK that the final destination is different (i do translations). I attached the BYE from both servers. Any ideas? Thanks, Uri You probably meant the To and From headers, I'm guessing. Yeah, as long as there is no display name component, URIs in headers like that don't have to go in s. The way Kamailio sends it is grammatically valid, per RFC 3261. The user agents are at fault for not understanding it correctly. Alex Balashov abalashov at evaristesys.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: /BYE headers? Which headers? Uri Shacked ushacked at gmail.com http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users wrote: Hi, I think there is a bug with the BYE that is sent to the caller and //callee //when dialog timeout happends. The BYE headers are sent with no or . //So, some sip singaling points decline the BYE. BR, //Uri // ___ //SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing //list //sr-users at lists.sip-router.org http://lists.sip-router.org/cgi-bin
[SR-Users] BYE dialog timeout bad syntax
Hello, The BYE, generated by Kamailio in case of dialog timeout, is malformed: BYE sip:anonymous@192.168.225.2:50601 sip:anonymous@192.168.225.2:50601 SIP/2.0 Via: SIP/2.0/UDP 172.16.60.113;branch=z9hG4bK77b6.941684b6.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-JfymiMenCtp4urS5CXSnCHJnCXJZiHvRCHYJb6ggNPN9NVDL3 -TWhdW0UvOfN1KPTReRiHy1CHmcs6mZiHS* To: sip:anonymous;cpc=ordinary@192.168.225.2;tag=01e3a8c0-c1c2-t-1 sip:anonymous;cpc=ordinary@192.168.225.2;tag=01e3a8c0-c1c2-t-1 From: sip:1255010006@192.168.225.2:5060;user=phone;tag=813142547-1366730270587 sip:1255010006@192.168.225.2:5060;user=phone;tag=813142547-1366730270587 CSeq: 465332801 BYE Call-ID: mailto:1aebb42c-01e3a8c0-07c2@192.168.225.2 1aebb42c-01e3a8c0-07c2@192.168.225.2 Content-Length: 0 User-Agent: kamailio (3.3.2 (x86_64/linux)) Max-Forwards: 69 The bad syntax is located in the To header field. According to the RFC 3261 section 25.1, the grammar of the To header field is as follow: To= ( To / t ) HCOLON ( name-addr / addr-spec ) *( SEMI to-param ) name-addr = [ display-name ] LAQUOT addr-spec RAQUOT addr-spec = SIP-URI / SIPS-URI / absoluteURI to-param = tag-param / generic-param The RFC 3261 section 20.10 explains that: Even if the display-name is empty, the name-addr form MUST be used if the addr-spec contains a comma, semicolon, or question mark. There may or may not be LWS between the display-name and the . As the addr-spec sip:anonymous;cpc=ordinary@192.168.225.2 sip:anonymous;cpc=ordinary@192.168.225.2 contains a semicolon, it means that the name-addr form must be used. The To header field should be encoded as follow: To: sip:anonymous;cpc=ordinary@192.168.225.2 sip:anonymous;cpc=ordinary@192.168.225.2;tag=01e3a8c0-c1c2-t-1 BR, Julia ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] msg_apply_changes() in route[RELAY] gets error
Hello, When I used msg_apply_changes(); in route[RELAY] included in request_route, Received ERROR: textopsx [textopsx.c:116]: invalid usage - not in request route. Why? Thanks, Julia. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to rewrite tu in CANCEL message ?
Hello, We solved problems by disabling double rr in rr module. Now this works well! :) Thank all of you, Julia. _ From: Julia [mailto:juli...@gmail.com] Sent: Monday, February 04, 2013 3:17 PM To: 'mico...@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite tu in CANCEL message ? Hello Daniel, We tested in version 3.3.0 and got some problems: 1) Modified To header sent in CANCEL only when we add msg_apply_changes() after uac_replace_to()command in INVITE set out. 2) When we add msg_apply_changes(),INVITE is being sent out with additional Record-route header (without IP): S:E@FINVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:172.16.60.70;r2=on;lr;ftag=02e3a8c0-5ffc5d-t-2;vst=AHQAAAwLAQkICnAB BXIfCAQABwYWGAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK5653.9713646.0 Via: SIP/2.0/UDP 192.168.225.2:50602;branch=z9hG4bK005ffc5d511f5cf933dcd0456cb2ffe587 4d2a08 Max-Forwards: 68 From: 39936646 39936646 sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ffc5 d-t-2 To: sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone Call-ID: 1bf13574-02e3a8c0-00010c35@192.168.225.2 CSeq: 2 INVITE Contact: sip:39936646@192.168.225.2:50602 User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: 39936646 39936646 sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x000210043a000154010010043b00015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436 v=0 o=10.203.22.10 14111 2 IN IP4 10.203.22.10 s=SIP Call c=IN IP4 10.203.22.10 t=0 0 a=sendrecv m=audio 8368 RTP/AVP 8 a=rtpmap:8 PCMA/8000/1 a=ptime:20 3) If TOPOH module is used, mask IP address (10.1.1.10) is sent in the second Record-route (instead of local host IP). J5INVITE sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone SIP/2.0 Record-Route: sip:;r2=on;lr;ftag=02e3a8c0-5ff136-t-2;vst=AHQAAAwLAQkICnABBXIfCAQABwYW GAlHRktAB0VYWV5edXNlcj1waG9uZQ-- Record-Route: sip:10.1.1.10;line=sr-N6IAzBFwMJZfWJZ6MGZwMx1LMBu5oB1dNB1EpSthH.yLg.WrzSMAO .KEgBFlWJu4O.VXphW4Hjt0Pjt0mtt0Pjtw.FtaC4IxoqtGPIregqW0jjtGpuI9a4tdmtenpFtGM tggKu3ugRa3.EfBCBtw3jNspKYaOm4* Via: SIP/2.0/UDP 172.16.60.70;branch=z9hG4bK7bff.5c4d0c12.0 Via: SIP/2.0/UDP 10.1.1.10;branch=z9hG4bKsr-j4IPOlV7MGQKatycM.qLOBF6zGZLMBj7MBvuMx3AMB1jmxuqC 93X3heroEWvH9vsCFN43qdAMxyAMxyAMxyAWRgEM.M63EMAzR3u3lpq3RV4MxprWRjuzRaBg.cw3 RMAz.PLzSM* Max-Forwards: 68 From: 39936646 39936646 sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone;tag=02e3a8c0-5ff13 6-t-2 To: sip:039988002@172.16.60.6 mailto:sip%3A039988002@172.16.60.6 ;user=phone Call-ID: 3fe92128-02e3a8c0-00010c15@192.168.225.2 CSeq: 2 INVITE Contact: sip:10.1.1.10;line=sr-N6IAzBMsz.M6WBP6PxFsMJZfWBc7MBVuOBV-W.y6MxV* User-Agent: NetCentrex CCS Softswitch/7.11.2 Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, INFO, PRACK, UPDATE, NOTIFY Supported: 100rel P-Asserted-Identity: 39936646 39936646 sip:39936646;cpc=ordinary@192.168.225.2:5060;user=phone Privacy: none Content-Type: application/sdp Content-Length: 163 X-Ncx-Service-Info: h450-info=0x0002100434000154010010043500015503408000;ncx-info=0x407100330801 C016653136343A303030303030393732333939333636343601B0020C00010011333939333636 3436203339393336363436 v=0 o=10.203.22.10 14090 2 IN IP Thank you, Julia -Original Message- From: Julia [mailto:juli...@gmail.com] Sent: Thursday, January 31, 2013 2:03 PM To: 'mico...@gmail.com'; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: RE: [SR-Users] How to rewrite tu in CANCEL message ? Thank you, we will try to test it. -Original Message- From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Thursday, January 31, 2013 1:57 PM To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? I checked the sources and found that building CANCEL with From/To headers used in the INVITE sent out is done when using uac functions for changing their value. Some internal flags are set by those functions. So a patch should be done for remove_hf()/insert_hf() case or alternatively export a function to explicitely set these internal flags from config (do be used by the script writer when knowing the from/to headers where changed in some way). Without a patch, the uac module functions have to be used
Re: [SR-Users] How to rewrite tu in CANCEL message ?
OK, but a problem is in partially re-parsing of CANCEL. ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW. INVITE -- Kam INVIRE -- ru=a ru=c tu=a tu=c fu=b fu=d ---100--- 100 ---180---180 CANCEL -- CANCEL -- ru=aru=c tu=atu=a fu=bfu=b --481 Call/Transaction does not exist Thank you, -Original Message- From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE. /O 30 jan 2013 kl. 14:40 skrev Carsten Bock cars...@ng-voice.com: Hi, probably the best way is to simply use the uac_replace_to-method from the uac module: http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3) Kind regards, Carsten 2013/1/30 Julia juli...@gmail.com: Hello all, Is there any way to rewrite tu in CANCEL message in 3.2.1? We use remove_hf / insert_hf for INVITEs tu modification before t_relay. It works fine, but it doesnt work for CANCEL (INVITE re-parsing is disabled). Ths, ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:cars...@ng-voice.com Office +49 40 34927219 Fax +49 40 34927220 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to rewrite tu in CANCEL message ?
Thank you, we will try to test it. -Original Message- From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Thursday, January 31, 2013 1:57 PM To: Julia; 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -Users Mailing List' Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? I checked the sources and found that building CANCEL with From/To headers used in the INVITE sent out is done when using uac functions for changing their value. Some internal flags are set by those functions. So a patch should be done for remove_hf()/insert_hf() case or alternatively export a function to explicitely set these internal flags from config (do be used by the script writer when knowing the from/to headers where changed in some way). Without a patch, the uac module functions have to be used. Cheers, Daniel On 1/31/13 12:29 PM, Julia wrote: We get the same result with modparam(tm, reparse_invite, 1) and modparam(tm, reparse_invite, 0) -Original Message- From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Thursday, January 31, 2013 1:24 PM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? Hello, have you changed the value for tm parameter 'reparse_invite': http://kamailio.org/docs/modules/stable/modules/tm.html#reparse_invite Cheers, Daniel On 1/31/13 12:02 PM, Julia wrote: OK, but a problem is in partially re-parsing of CANCEL. ru = modified ru; tu = original tu; fu = original fu. In this case 481 received from GW. INVITE -- Kam INVIRE -- ru=aru=c tu=atu=c fu=bfu=d ---100--- 100 ---180---180 CANCEL -- CANCEL -- ru=aru=c tu=atu=a fu=bfu=b --481 Call/Transaction does not exist Thank you, -Original Message- From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Olle E. Johansson Sent: Thursday, January 31, 2013 10:52 AM To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - UsersMailing List Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? Unless you rewrote the To-URI in the INVITE, you really should not try to change a CANCEL. It needs to be almost a copy of the matching INVITE. /O 30 jan 2013 kl. 14:40 skrev Carsten Bock cars...@ng-voice.com: Hi, probably the best way is to simply use the uac_replace_to-method from the uac module: http://www.kamailio.org/docs/modules/devel/modules/uac.html#id2494560 (tested with 3.3) Kind regards, Carsten 2013/1/30 Julia juli...@gmail.com: Hello all, Is there any way to rewrite tu in CANCEL message in 3.2.1? We use remove_hf / insert_hf for INVITEs tu modification before t_relay. It works fine, but it doesnt work for CANCEL (INVITE re-parsing is disabled). Ths, ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:cars...@ng-voice.com Office +49 40 34927219 Fax +49 40 34927220 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, April 16-17, 2013, Berlin - http://conference.kamailio.com - ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] How to rewrite tu in CANCEL message ?
Hello all, Is there any way to rewrite tu in CANCEL message in 3.2.1? We use remove_hf / insert_hf for INVITE's tu modification before t_relay. It works fine, but it doesn't work for CANCEL (INVITE re-parsing is disabled). Ths, ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to rewrite tu in CANCEL message ?
Yes, we know it's wrong. But if we really need it, is there a way to do it? -Original Message- From: sr-users-boun...@lists.sip-router.org [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Alex Balashov Sent: Wednesday, January 30, 2013 4:36 PM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] How to rewrite tu in CANCEL message ? On 01/30/2013 09:31 AM, Julia wrote: We need some number manipulation for outgoing calls to PSTN GW. The same manipulations must be in ru and tu, because our PSTN GW adds redirection when tu ≠ ru. When we used INVITE re-parsing for CANCEL, modified tu is not included. I would say your PSTN GW is doing it wrong. No routing should ever be done on To. It is a purely cosmetic commentary on the intended logical destination of the call. Only the RURI should be used for that. -- 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/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
